Processing Multiple SWIFT messages with A4SWIFT 3.0
Danappagoudar@discussions.microsoft.com Lingaraj Danappagoudar
Note: I am using MicrosoftAccelerator 2007
My incoming file is like this [MT101]$[MT103]$[MT210]$[MT101]
I need to do debatching and do the processing using orchestration.
Fragmentation = True
Inbound Debatching = True
Message Trailer Schema = flat file schema(with single element)
SWIFT Header Schema =
Microsoft.Solutions.FinancialServices.SWIFT.Runtim eSchemas.HeaderSchema,
Microsoft.Solutions.FinancialServices.SWIFT.Runtim eSchemas, Version=2.0.0.0
I set these properties in Disassembler stage and dropped the incoming file
in input folder. I am getting the input file as it is in OUTPUT folder with
UNPARSEDMESSAGE.
It seems to be i am going wrong with flat file. Debatching is not etall
happening.
Plzz help me out this...its really very very urgent as i am getting blast
from client.
Regards,
Lingaraj Danappagoudar
Jay Kinker
I hope you have already read answer to this query in another thread in this
forum itself... I cannot answer to your problem from the information you
have provided. There can be many reasons why you are not able to parse SWIFT
messages
Anyways, I will try to answer you...
I have not yet worked with MSAccelerator 2007 but I don't think it will be
different then what previous versions had.
This should be straight forward, with or withou Orchestration.
BTW Processing multiple messages has nothing to do with Orchestration.
Let us go in stages:
You have not mentioned if you are able to process even 1 file at a time. Try
with only 1 file (with only 1 message) in input folder.
- Use A4SWIFT DASM in receive pipeline
- use Passthrough pipeline as send pipeline
If you complete entire flow correctly - You must get an XML file against 1
input SWIFT message (flat file). Try with only 1 message type per file.
Once you are able to do this... processing multiple SWIFT messages of
multiple types from one file should not be a problem.
NOTE - It is very important that you use SWIFT message of correct SWIFT
standard/version.
For example: Use SWIFT 2008 complaint SWIFT messages if you have applied
SWIFT 2008 Netpack over A4SWIFT.
BizTalk may not be able to parse SWIFT messages if there is any version
conflict between your input SWIFT message and BizTalk Accelerator Netpack.
Regards,
Jay Kinker__
http://geekswithblogs.net/jaykinker
------------------------------------------------------------------------------
Lingaraj Danappagoudar
I am able to process with single file with single message type. I don't have
any issues with this, as i have been working on the same since last 5 months
and done with e-mail alerting...n so on.
I got this new requirement recently and could not able to solve this.
I am using "Microsoft BizTalk Accelerator for SWIFT 2007 Message Pack".
Steps followed:
-Flat file with single element(Schema-flat file extension, Default child
order-postfix, deflt child order type-character, default child delimiter-$),
in Root i have used these default values and for element did not change
anything.
-dissebler stage..the properties i mentioned
-Receive location...used the receive pipeline and in send port...passthru.
Note: As i found trailer.xsd schema in the 2007 service pack...but am unable
to open it.
If possible please send out me the Flat file...which we are refering in
trailer schema.
Regards,
Lingaraj
Jay Kinker
If you are able to process one message at a time means, you have proper
version of flat file, schema and pipelines.
Only part which is remaining is splitting multiple files, rest remains same.
Your trailer also looks good from the description you have provided.
You now have to do following property changes for A4SWIFT Disassembler:
Set “Fragmentation” to TRUE
Set “Inbound Debatching” to TRUE
I don't see any reason why you are not able to do it.
- Undeploy receive pipeline
- Do property changes and redeploy
Below is the Trailer schema I was using in my demo application:
<?xml version="1.0" encoding="utf-16" ?>
- <xs:schema xmlns:b="http://schemas.microsoft.com/BizTalk/2003"
xmlns="http://Schemas.FFTrailerSchema"
targetNamespace="http://Schemas.FFTrailerSchema"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
- <xs:annotation>
- <xs:appinfo>
<b:schemaInfo standard="Flat File" root_reference="MsgTrailer"
default_pad_char="" pad_char_type="char" count_positions_by_byte="false"
parser_optimization="speed" lookahead_depth="3" suppress_empty_nodes="false"
generate_empty_nodes="true" allow_early_termination="false"
early_terminate_optional_fields="false"
allow_message_breakup_of_infix_root="false" compile_parse_tables="false"
default_child_order="postfix" child_delimiter_type="hex"
default_child_delimiter="0x0D 0x0A" />
<schemaEditorExtension:schemaInfo namespaceAlias="b"
extensionClass="Microsoft.BizTalk.FlatFileExtension.FlatFileExtension"
standardName="Flat File"
xmlns:schemaEditorExtension="http://schemas.microsoft.com/BizTalk/2003/SchemaEditorExtensions" />
</xs:appinfo>
</xs:annotation>
- <xs:element name="MsgTrailer">
- <xs:annotation>
- <xs:appinfo>
<b:recordInfo structure="delimited"
preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false"
sequence_number="1" child_order="default" child_delimiter_type="default" />
</xs:appinfo>
</xs:annotation>
- <xs:complexType>
- <xs:sequence>
- <xs:annotation>
- <xs:appinfo>
<b:groupInfo sequence_number="0" />
</xs:appinfo>
</xs:annotation>
- <xs:element name="Field" type="xs:string">
- <xs:annotation>
- <xs:appinfo>
<b:fieldInfo sequence_number="1" justification="left" />
</xs:appinfo>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Below is sample for MT103 seperated by $
{1:F01BOFAUSNYJXXX4321000123}{2:I103BANKDEFFAXXXN2020}{3:{103:CAD}}{4:
:20:00071
:23B:SPRI
:32A:001118USD3,34
asdf
asdf
:50F:/34x
TESTUSVT
:59:/34x
4X35x
:71A:OUR
-}{5:{MAC:23456789}{PAC:23456789}{CHK:123456789012}{SYS:1231313}{TNG:}{PDE:12345}{DLM:}}${1:F01BOFAUSNYJXXX4321000123}{2:I103BANKDEFFAXXXN2020}{3:{103:CAD}}{4:
:20:00071
:23B:SPRI
:32A:001118USD3,34
asdf
asdf
:50F:/34x
TESTUSVT
:59:/34x
4X35x
:71A:OUR
-}{5:{MAC:23456789}{PAC:23456789}{CHK:123456789012}{SYS:1231313}{TNG:}{PDE:12345}{DLM:}}
Hope this helps...
Please let the forum know about your solution when you resolve this issue
Cheers,
Lingaraj Danappagoudar
I have noticed that you have used child delimiter type as Hexagon..and
delimiter 0x0D 0X0A in your flat file.
Jay Kinker
In your case, you must use:
Delimter type = Character
Delimiter = $
Regards,
Jay
----------------------------------------------------------------------
Lingaraj Danappagoudar
<?xml version="1.0" encoding="utf-16"?>
<xs:schema xmlns:b="http://schemas.microsoft.com/BizTalk/2003"
xmlns="http://Shell.BizTalk.GF.FTO.Quantum.PaymentsAndATR.Schemas.DebatchSchema"
targetNamespace="http://Shell.BizTalk.GF.FTO.Quantum.PaymentsAndATR.Schemas.DebatchSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:annotation>
<xs:appinfo>
<b:schemaInfo default_pad_char=" " pad_char_type="char"
count_positions_by_byte="false" parser_optimization="speed"
lookahead_depth="3" suppress_empty_nodes="false" generate_empty_nodes="true"
allow_early_termination="false" early_terminate_optional_fields="false"
allow_message_breakup_of_infix_root="false" compile_parse_tables="false"
standard="Flat File" root_reference="DebatchSchema"
default_child_order="postfix" child_delimiter_type="char"
default_child_delimiter="$" />
<schemaEditorExtension:schemaInfo namespaceAlias="b"
extensionClass="Microsoft.BizTalk.FlatFileExtension.FlatFileExtension"
standardName="Flat File"
xmlns:schemaEditorExtension="http://schemas.microsoft.com/BizTalk/2003/SchemaEditorExtensions" />
</xs:appinfo>
</xs:annotation>
<xs:element name="DebatchSchema">
<xs:annotation>
<xs:appinfo>
<b:recordInfo structure="delimited"
preserve_delimiter_for_empty_data="true" suppress_trailing_delimiters="false"
sequence_number="1" child_order="default" child_delimiter_type="default" />
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:annotation>
<xs:appinfo>
<b:groupInfo sequence_number="0" />
</xs:appinfo>
</xs:annotation>
<xs:element name="Debatch" type="xs:string">
<xs:annotation>
<xs:appinfo>
<b:fieldInfo justification="left" sequence_number="1" />
</xs:appinfo>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Regards,
Lingaraj Danappagoudar
So, Flat file should look like this.
Schema(default_child_order="postfix" child_delimiter_type="hex"
,default_child_delimiter="0x0D 0x0A" )
-Root(Child order=postfix, delimiter type=character, delimiter=$)
-field element(leave as it is)
Isn't it?
Jay Kinker
Regards,
Jay
-----------------------------------------------
Lingaraj Danappagoudar
Please let me know your contact number...if you don't mind. I have to
resolve this issue by any means..lot of pressure from clients.
Regards,
Lingaraj
91-9731142000
Lingaraj Danappagoudar
FYI..
Jay Kinker
Regards,
Jay
Lingaraj Danappagoudar
So, the Flat file should look like this.
Schema(default_child_order="postfix" child_delimiter_type="hex"
,default_child_delimiter="0x0D 0x0A" )
-Root(Child order=postfix, delimiter type=character, delimiter=$)
-field element(leave as it is)
Isn't it?
Regards,
Jay Kinker
Open it in Visual studio and change below properties of "Schema Properties"
to:
Default Child Delimiter = $
Default Child Delimiter Type = Character
Everything else remains same.
Cheers,
Jay
-------------------------------------------------
Lingaraj Danappagoudar
Below given is my incoming file with multiple message types.
{1:F01BOFAUSNYJXXX4321000123}{2:I103BANKDEFFAXXXN2020}{3:{103:CAD}}{4:
:20:AT1537786-1
:23B:SSTD
:32A:071109EUR920000,
:33B:EUR920000,
:53B:/11030728
:56A:CHASDEFX
:57A:CHASGB2L
:71A:OUR
-}{S:{LAU:CF92FBD8}}${1:F01BOFAUSNYJXXX4321000123}{2:I103BANKDEFFAXXXN2020}{3:{103:CAD}}{4:
:20:AT1537786-1
:23B:SSTD
:32A:071109EUR920000,
:33B:EUR920000,
:53B:/11030728
:56A:CHASDEFX
:57A:CHASGB2L
:71A:OUR
-}{S:{LAU:CF92FBD8}}${1:F01BOFAUSNYJXXX4321000123}{2:I103BANKDEFFAXXXN2020}{3:{103:CAD}}{4:
:20:AT1537786-1
:23B:SSTD
:32A:071109EUR920000,
:33B:EUR920000,
:53B:/11030728
:56A:CHASDEFX
:57A:CHASGB2L
:71A:OUR
-}{S:{LAU:CF92FBD8}}
Lingaraj Danappagoudar
Wat is the message you have used in Receive Shape?
I used inXmlDoc(of type xml.xmldocument).
Lingaraj Danappagoudar
My incoming file with multiple messages looks like this.
End of Message Terminator : “-}”
LAU Key: {S:{LAU:7CE50019}}
The LAU key appears as follows after the End of Message Terminator
-}{S:{LAU:7CE50019}}
{1:F01GB20XXXX0000000000}{2:I210CHASGB20XXXXN}{4:
:20:SE233-1471
:25:/123123123
:30:080613
:21:SE233-1471
:32B:BRL2,02
:52A:CHASGB20
:56A:CHASGB20
-}{S:{LAU:7D300784}}${1:F01LGB20XXXX0000000000}{2:I210CHASGB20XXXXN}{4:
:20:SE233-1471
:25:/123123123
:30:080613
:21:SE233-1471
:32B:BRL2,02
:52A:CHASGB20
:56A:CHASGB20
-}{S:{LAU:7D300784}}
I am getting 1 Parse error in Event viewer. So, i want the flat file which
resolve this issue.
Lingaraj Danappagoudar
Now...i got the result what i expected. I am able to debatch now.
Thanks for your support and guidance.
Margaret
I am starting up a business and need new customers. Any help that you could
give me, I would really appreciate it. Im not spaming anyone, so please let
me know if there are anyone you know who lives in the london area and would
be interested in the purchase of medical uniforms.
Im trying to get as many customers as i can. i need help tho. Please pass
this email on to whom ever you know who would be interested. I would really
appreciate it.
Here is a little about it:
We are a business that makes Medical Uniforms which are made for Nurse's,
Doctors, and any Medical team that there is out there like PSW's.
You can find more out about it at: www.a...@hotmail.com/blog
We have flexible plans to accommodate growth. All size's, styles and colors
that you can think of
We are located in London, Ontario
Thank you for your time.
Margaret
"Lingaraj Danappagoudar" <Lingaraj Danapp...@discussions.microsoft.com>
wrote in message news:43FE1359-AC52-4499...@microsoft.com...
Lingaraj Danappagoudar
The issue related to debatching has been resolved. I had refered the trailer
schema in header schema instead of refering at trailer schema properties.
And, made small mistake in flat file trailer schema.
One thing, my incomimng file contains CR at the end of file. How to remove
that...if present. if not..proceed further.
regards,
RAJ