BizTalk Server Orchestration - SWIFT accelerator / orchestration question

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > July 2005 > SWIFT accelerator / orchestration question





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author SWIFT accelerator / orchestration question
pj

2005-07-01, 5:54 pm

I'm using BT 2004 with SWIFT accelerator.
In simple terms I want to assemble the SWIFT flatfile to XML - easy by
folloiwing the tutorial - and output the XML to a folder.
I then have an orchestration that picks it up and maps it to a common XML
layout.
OK so far - for one message type (MT540 say).

Now I want to do the same for another SWIFT message of the same "family" (
MT541) - i.e. it fits the common XML layout that I want to produce at the
end.

It seems I should be able to direct the generated SWIFTXML to different
receieve ports, one for each message type which are then bound to 2 different
recieve ports in my orchestration.

My orchestration has 2 recieve ports, one for each message type & then each
has a receive shape within a listen shape to process whatever arrives - each
branch will process a different message type according to it's own map to my
common output which is then sent to a send port by a common send shape.

My first message type works fine - but the second consistently shows the
follwing error in the event viewer:

"Microsoft.BizTalk.DefaultPipelines.XMLReceive" Source: "XML disassembler"
Receive Location: "C:\STP\XMLFiles\GBPSWIFT(To)\MT541\*.xml" Reason: The
disassembler cannot retrieve the document specification by using this type:
"http://schemas.microsoft.com/BizTalk/Solutions/FinancialServices/SWIFT/Category5/MT541#SWIFT_CATEGORY5_MT541_Interchange".
Either the schema is not deployed correctly, or more than one schema is
deployed for the same message type.

I've checked all the things that are obvious to me -
Ports appear to be bound correctly to the correct receive location
In the orchestration each of the receive port requests points to a
different message type.

Can someone suggest what else to check - or better still a simpler way to
process this.

Thanks in advance.
Scott Colestock

2005-07-11, 5:51 pm

Have you confirmed that the second schema is deployed correctly? You can
use the biztalk assembly viewer for this, or look in the bt_DocumentSpec
table in Sql Server (BizTalkMgmtDb).


(Also - in case you haven't already thought of this - you won't need the
file folder as an intermediary in the long term - the orchestration can
subscribe directly to the documents you are receiving.)

Scott Colestock
www.traceofthought.net



"pj" <jersey@ci.com> wrote in message
news:D53EC185-926A-4665-B147-81A87B7FDF7C@microsoft.com...
> I'm using BT 2004 with SWIFT accelerator.
> In simple terms I want to assemble the SWIFT flatfile to XML - easy by
> folloiwing the tutorial - and output the XML to a folder.
> I then have an orchestration that picks it up and maps it to a common XML
> layout.
> OK so far - for one message type (MT540 say).
>
> Now I want to do the same for another SWIFT message of the same "family" (
> MT541) - i.e. it fits the common XML layout that I want to produce at the
> end.
>
> It seems I should be able to direct the generated SWIFTXML to different
> receieve ports, one for each message type which are then bound to 2
> different
> recieve ports in my orchestration.
>
> My orchestration has 2 recieve ports, one for each message type & then
> each
> has a receive shape within a listen shape to process whatever arrives -
> each
> branch will process a different message type according to it's own map to
> my
> common output which is then sent to a send port by a common send shape.
>
> My first message type works fine - but the second consistently shows the
> follwing error in the event viewer:
>
> "Microsoft.BizTalk.DefaultPipelines.XMLReceive" Source: "XML disassembler"
> Receive Location: "C:\STP\XMLFiles\GBPSWIFT(To)\MT541\*.xml" Reason: The
> disassembler cannot retrieve the document specification by using this
> type:
> "http://schemas.microsoft.com/BizTalk/Solutions/FinancialServices/SWIFT/Category5/MT541#SWIFT_CATEGORY5_MT541_Interchange".
> Either the schema is not deployed correctly, or more than one schema is
> deployed for the same message type.
>
> I've checked all the things that are obvious to me -
> Ports appear to be bound correctly to the correct receive location
> In the orchestration each of the receive port requests points to a
> different message type.
>
> Can someone suggest what else to check - or better still a simpler way to
> process this.
>
> Thanks in advance.



pj

2005-07-13, 7:54 am

I have undeployed the schema, removed it from my solution, re-depolyed the
solution, re-added the schema & re-deployed and still get the same message. I
also tried to install the biztalk assembly viewer following the instructions
in the documentation, but then I get "The specified module cannot be found" -
I'm sure I've navigated to the correct path & can see the BTSAsmExt.dll.
I tried to look in the bt_DocumentSpec table, but I have no idea what I'm
looking for & it's a big table!

So I'm no better off.

Thanks for the tip - I as I'm new to this I thought it best to take it one
step at a time - before sending something in and hoping to see it at the
other end...

"Scott Colestock" wrote:

> Have you confirmed that the second schema is deployed correctly? You can
> use the biztalk assembly viewer for this, or look in the bt_DocumentSpec
> table in Sql Server (BizTalkMgmtDb).
>
>
> (Also - in case you haven't already thought of this - you won't need the
> file folder as an intermediary in the long term - the orchestration can
> subscribe directly to the documents you are receiving.)
>
> Scott Colestock
> www.traceofthought.net
>
>
>
> "pj" <jersey@ci.com> wrote in message
> news:D53EC185-926A-4665-B147-81A87B7FDF7C@microsoft.com...
>
>
>

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com