|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
SWIFT Transformation in WMQI 2.1 |
« View previous topic :: View next topic » |
Author |
Message
|
Debadutta |
Posted: Mon Jul 12, 2004 10:01 pm Post subject: SWIFT Transformation in WMQI 2.1 |
|
|
 Newbie
Joined: 06 Dec 2002 Posts: 4
|
Hi,
I am trying to test out SWIFT transformation in WMQI 2.1 environment by using the IBM Provided SWIFT Message set.
I am hard coding the values for SWIFT elements in the message flow. The trace of the message flow shows the hardcoded values being assigned to the SWIFT elements, but the output shows only {A:}.
User Trace
-------------
2004-07-13 10:59:31.014999 2640 UserTrace BIP2537I: Node 'Test_MT536.Compute1': Executing statement 'SET OutputRoot.MRM.A.SW23G.SUB_FUNCTION = 'ABCD';' at (23, 1).
2004-07-13 10:59:31.014999 2640 UserTrace BIP2566I: Node 'Test_MT536.Compute1': Assigning value ''ABCD'' to field / variable 'OutputRoot.MRM.A.SW23G.SUB_FUNCTION'.
2004-07-13 10:59:31.014999 2640 UserTrace BIP2537I: Node 'Test_MT536.Compute1': Executing statement 'SET OutputRoot.MRM.A.SW98A.QUALIFIER = 'ABCD';' at (24, 1).
2004-07-13 10:59:31.014999 2640 UserTrace BIP2566I: Node 'Test_MT536.Compute1': Assigning value ''ABCD'' to field / variable 'OutputRoot.MRM.A.SW98A.QUALIFIER'.
2004-07-13 10:59:31.014999 2640 UserTrace BIP2537I: Node 'Test_MT536.Compute1': Executing statement 'SET OutputRoot.MRM.A.SW98A.DATE = '10102004';' at (25, 1).
2004-07-13 10:59:31.014999 2640 UserTrace BIP2566I: Node 'Test_MT536.Compute1': Assigning value ''10102004'' to field / variable 'OutputRoot.MRM.A.SW98A.DATE'.
2004-07-13 10:59:31.014999 2640 UserTrace BIP4124I: Message propagated to 'out' terminal of compute node 'Test_MT536.Compute1'.
2004-07-13 10:59:31.014999 2640 UserTrace BIP2538I: Node 'Test_MT536.Trace2': Evaluating expression 'Root' at (1, 3).
2004-07-13 10:59:31.014999 2640 UserTrace BIP4060I: Data '(
(0x1000000)Properties = (
(0x3000000)MessageSet = 'ITSMS70098001'
(0x3000000)MessageType = 'MT536'
(0x3000000)MessageFormat = 'SWIFT'
(0x3000000)Encoding = 546
(0x3000000)CodedCharSetId = 437
(0x3000000)Transactional = TRUE
(0x3000000)Persistence = FALSE
(0x3000000)CreationTime = GMTTIMESTAMP '2004-07-13 05:29:30.960'
(0x3000000)ExpirationTime = -1
(0x3000000)Priority = 0
(0x3000000)ReplyIdentifier = X'000000000000000000000000000000000000000000000000'
(0x3000000)ReplyProtocol = 'MQ'
(0x3000000)Topic = NULL
)
(0x1000000)MQMD = (
(0x3000000)SourceQueue = 'Q_IN'
(0x3000000)Transactional = TRUE
(0x3000000)Encoding = 546
(0x3000000)CodedCharSetId = 437
(0x3000000)Format = 'MQSTR '
(0x3000000)Version = 2
(0x3000000)Report = 0
(0x3000000)MsgType = 8
(0x3000000)Expiry = -1
(0x3000000)Feedback = 0
(0x3000000)Priority = 0
(0x3000000)Persistence = 0
(0x3000000)MsgId = X'414d5120514d31202020202020202020522cf240200028bc'
(0x3000000)CorrelId = X'000000000000000000000000000000000000000000000000'
(0x3000000)BackoutCount = 0
(0x3000000)ReplyToQ = ' '
(0x3000000)ReplyToQMgr = 'QM1 '
(0x3000000)UserIdentifier = 'hemendr '
(0x3000000)AccountingToken = X'160105150000008a5a4160f89fb474828ba628eb03000000000000000000000b'
(0x3000000)ApplIdentityData = ' '
(0x3000000)PutApplType = 11
(0x3000000)PutApplName = 'C:\WINNT\system32\mmc.exe '
(0x3000000)PutDate = DATE '2004-07-13'
(0x3000000)PutTime = GMTTIME '05:29:30.960'
(0x3000000)ApplOriginData = ' '
(0x3000000)GroupId = X'000000000000000000000000000000000000000000000000'
(0x3000000)MsgSeqNumber = 1
(0x3000000)Offset = 0
(0x3000000)MsgFlags = 0
(0x3000000)OriginalLength = -1
)
(0x1000021)MRM = (
(0x1000000)A = (
(0x3000000)SW16R = 'ABCD'
(0x1000000)SW28E = (
(0x3000000)NUMBER = 123
(0x3000000)INDICATOR = 'abcd'
)
(0x1000000)SW13A = (
(0x3000000)QUALIFIER = 'ABCD'
(0x3000000)NUMBER_ID = 'ABCD'
)
(0x1000000)SW20C = (
(0x3000000)QUALIFIER = 'ABCD'
(0x3000000)REFERENCE = 'ABCD'
)
(0x1000000)SW23G = (
(0x3000000)FUNCTION = 'ABCD'
(0x3000000)SUB_FUNCTION = 'ABCD'
)
(0x1000000)SW98A = (
(0x3000000)QUALIFIER = 'ABCD'
(0x3000000)DATE = '10102004'
)
)
)
)
' from trace node 'Test_MT536.Trace2'.
The trace node 'Test_MT536.Trace2' has output the specified trace data.
This is an information message provided by the message flow designer. The user response will be determined by the local environment.
2004-07-13 10:59:31.014999 2640 UserTrace BIP4067I: Message propagated to output terminal for trace node 'Test_MT536.Trace2'.
The trace node 'Test_MT536.Trace2' has received a message and is propagating it to any nodes connected to its output terminal.
No user action required.
2004-07-13 10:59:31.014999 2640 UserTrace BIP2638I: The MQ output node 'Test_MT536.MQOutput1' attempted to write a message to the specified queue 'Q_OUT' connected to queue manager 'QM1'. The MQCC was 0 and the MQRC was 0.
2004-07-13 10:59:31.014999 2640 UserTrace BIP2622I: Message successfully output by MQ output node 'Test_MT536.MQOutput1' to queue 'Q_OUT' on queue manager 'QM1'.
2004-07-13 10:59:37.859001 2288 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2004-07-13 10:59:37.859001 2288 UserTrace BIP6060I: Parser type 'Properties' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2004-07-13 10:59:37.859001 2288 UserTrace BIP6061I: Parser type 'MQMD' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value 'MQHMD' from previous parser.
2004-07-13 10:59:37.859001 2288 UserTrace BIP6061I: Parser type 'XML' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '230' bytes beginning at offset '364'. Parser type selected based on value 'XML' from previous parser.
Wondering if I am missing out anything here. Any help regarding this is highly appreciated.
Regards,
Debadutta |
|
Back to top |
|
 |
wooda |
Posted: Wed Jul 21, 2004 5:36 am Post subject: |
|
|
 Master
Joined: 21 Nov 2003 Posts: 265 Location: UK
|
What version of the IBM SWIFT message set are you using ?
Your problem might be that you are only setting a some of the fields in the outgoing swift message.
As I understand it the IBM SWIFT message set models the message as an outer message (SwiftEnvelope) which contains the common header strucutre an an embedded message (eg. MT536) to contain the body.
You don't appear to be setting any fields in the envelope and your outer message is MT536 not SwiftEnvelope so this may be the problem.
Although I'd have expected an error.
Try turning on validation in the flow so you can validate the outgoing message as this may give you more useful information.
regards,
Alex |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|