| Author |
Message
|
| amit1310 |
 Posted: Sat Jan 22, 2011 8:51 am Post subject: The required "targetService" property was not pres |
 |
|
Newbie
Joined: 22 Jan 2011
Posts: 9
|
Hi All,
Need help for the following.
We have the following setup Websphere --> Datapower --> MQ.
MQ sends across a raw SWIFT MQ message to Datapower, Datapower converts this into a SOAP JMS message and puts it on one of the queues from which an MDB read this.
The problem is that even the first log line in the MDB is not getting printed in the Application log files.
When we tried putting the same SOAP JMS message with the help of one of our Stubs, everything works fine.
The following error is printed in the system log files
'The required "targetService" property was not present in the inbound JMS request message.'
Can some one help us in this?? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sat Jan 22, 2011 3:25 pm Post subject: Re: The required "targetService" property was not |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| amit1310 wrote: |
Hi All,
Need help for the following.
We have the following setup Websphere --> Datapower --> MQ.
MQ sends across a raw SWIFT MQ message to Datapower, Datapower converts this into a SOAP JMS message and puts it on one of the queues from which an MDB read this.
The problem is that even the first log line in the MDB is not getting printed in the Application log files.
When we tried putting the same SOAP JMS message with the help of one of our Stubs, everything works fine.
The following error is printed in the system log files
'The required "targetService" property was not present in the inbound JMS request message.'
Can some one help us in this?? |
My guess is that this is something to do with the processing in your MDB.
Are you building a JMS (RFH2) header? Have you set all the expected properties?
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Jan 22, 2011 5:09 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Hrm.
I'm guessing that DataPower isn't properly building the message before it forwards it to the MDB.
 |
|
| Back to top |
|
|
| amit1310 |
| Posted: Sun Jan 23, 2011 5:44 am Post subject: "targetService" property was not present in the in |
|
|
Newbie
Joined: 22 Jan 2011
Posts: 9
|
Thanks for your feedback.
The message which is posted into the queue by our stub is the same as message which is posted by datapower. What else could we compare.
Now, other than the error message in the system log files "targetService" property was not present in the inbound JMS request message.' we have no other clue.
Is there some way of finding out that root cause of the issue. Are there any basic checks that we could do or questions that we could ask the MQ or the Datapower teams ? |
|
| Back to top |
|
|
| amit1310 |
| Posted: Sun Jan 23, 2011 5:59 am Post subject: Actual Message |
|
|
Newbie
Joined: 22 Jan 2011
Posts: 9
|
Just for Reference, this is the message that is being sent to Datapower
Message sent
SAFFY NO 037658242 QUEUE LIQUIDITY-FS{1:F01NEDSZAJ0XXXX5075861186}{2:O9411200100429SBZAZAJ0AXXX82285930641004291300N}{3:{108:37658242}
}{4:^M
:20:SM80594134145048^M
:21:LIQUIDTY476^M
:25:200830449^M
:28:00337/01^M
:62F:C110106ZAR13028,00^M
-}{5:{MAC:37658242}{CHK:C8D52B9FA681}}
StrucId =[MD ]
Version =[1]
Report =[0]
MsgType =[8]
Expiry =[-1]
Feedback =[0]
Encoding =[273]
CodedCharSetId =[0]
Format =[MQSTR ]
Priority =[-1]
Persistence =[2]
MsgId =[0-65, 1-77, 2-81, 3-32, 4-90, 5-65, 6-78, 7-67, 8-48, 9-48, 10-48, 11-46, 12-84, 13-87, 14-69, 15-69, 16-76, 17-160, 18-42,
19-178, 20-33, 21-33, 22-9, 23-11, ]
CorrelId =[037658242 ]
BackoutCount =[0]
ReplyToQ =[ ]
ReplyToQMgr =[ ]
UserIdentifier =[swqa ]
AccountingToken =[ ^C227 ]
ApplIdentityData=[ ]
PutApplType =[6]
PutApplName =[swmqout ]
PutDate =[20110120 ]
PutTime =[10073043 ]
ApplOriginData =[ ]
GroupId =[ ]
MsgSeqNumber =[1]
Offset =[0]
MsgFlags =[0]
OriginalLength =[-1] |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Jan 23, 2011 7:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The way I interpret the error message is that the MQ message on the queue does not have enough information in it about what SOAP/JMS call is being made for the MDB to determine which Target Service and which Operation on that Target Service to call.
That is, if you were making a SOAP/HTTP call here, you would be missing the service part of the HTTP url - not the http:<hostname:port>/ part, but the rest of it - the http:/<hostname:port>/<target service> part.
So when the SOAP/JMS listener on the WAS instance receives the message, it doesn't know which MDB or SOAP Service to call.
So if nothing else, I would compare the messages from your stubs with the ones from Datapower, at the MQ level. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jan 23, 2011 10:00 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mqjeff wrote: |
The way I interpret the error message is that the MQ message on the queue does not have enough information in it about what SOAP/JMS call is being made for the MDB to determine which Target Service and which Operation on that Target Service to call.
That is, if you were making a SOAP/HTTP call here, you would be missing the service part of the HTTP url - not the http:<hostname:port>/ part, but the rest of it - the http:/<hostname:port>/<target service> part.
So when the SOAP/JMS listener on the WAS instance receives the message, it doesn't know which MDB or SOAP Service to call.
So if nothing else, I would compare the messages from your stubs with the ones from Datapower, at the MQ level. |
 I would also make sure I compare the message properties (V7 or V6 in RFH2). If for some reason the information is stored in the message properties and not in the message content itself...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| amit1310 |
| Posted: Sat Jan 29, 2011 1:31 am Post subject: "targetService" property was not present |
|
|
Newbie
Joined: 22 Jan 2011
Posts: 9
|
Nothing has worked until now. we have used all the hints/suggestions given by this forum.
The messages are directed to the system error queue. On viewing the message, this is what we see
<?xml version="1.0" encoding="UTF-8"?>.<soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">. <soapenv:Body>. <StatementCallbackBal>. <NS1:StatementCallbackBalRq xmlns:NS1="http://contracts.it.nednet.co.za/services/customer-services/2010-06-11/SwiftCallback">. <NS1:BasicHeader>. <NS1:logicalTerminalIdentifier>. <NS1:bankCode>NEDS</NS1:bankCode>. <NS1:countryCode>ZA</NS1:countryCode>. <NS1:locationCode>J0</NS1:locationCode>. <NS1:logicalTerminalCode>X</NS1:logicalTerminalCode>. <NS1:branchCode>XXX</NS1:branchCode>. </NS1:logicalTerminalIdentifier>. <NS1:sessionNumber>5075</NS1:sessionNumber>. <NS1:sequenceNumber>861186</NS1:sequenceNumber>. </NS1:BasicHeader>. <NS1:ApplicationHeaderResponse>. <NS1:messageType>941</NS1:messageType>. <NS1:inputTime>1200</NS1:inputTime>. <NS1:messageInputReference>. <NS1:deliveryDate>20100429</NS1:deliveryDate>. <NS1:logicalTerminalIdentifier>. <NS1:bankCode>SBZA</NS1:bankCode>. <NS1:countryCode>ZA</NS1:countryCode>. <NS1:locationCode>J0</NS1:locationCode>. <NS1:logicalTerminalCode>A</NS1:logicalTerminalCode>. <NS1:branchCode>XXX</NS1:branchCode>. </NS1:logicalTerminalIdentifier>. <NS1:sessionNumber>6597</NS1:sessionNumber>. <NS1:sequenceNumber>593064</NS1:sequenceNumber>. </NS1:messageInputReference>. <NS1:outputDate>100429</NS1:outputDate>. <NS1:outputTime>1300</NS1:outputTime>. <NS1:messagePriority>N</NS1:messagePriority>. </NS1:ApplicationHeaderResponse>. <NS1:identification>SM80594134145048</NS1:identification>. <NS1:relatedIdentification>LIQUIDTY786</NS1:relatedIdentification>. <NS1:account>200830449</NS1:account>. <NS1:Statements>. <NS1:documentNumber>337</NS1:documentNumber>. <NS1:documentSequenceNumber>1</NS1:documentSequenceNumber>. </NS1:Statements>. <NS1:finalClosingBookedBalance>. <NS1:transactionIndicator>C</NS1:transactionIndicator>. <NS1:finalClosingBookedBalanceDate>110106</NS1:finalClosingBookedBalanceDate>. <NS1:theCurrencyCode>ZAR</NS1:theCurrencyCode>. <NS1:theCurrencyAmount>13028.00</NS1:theCurrencyAmount>. </NS1:finalClosingBookedBalance>. </NS1:StatementCallbackBalRq>. </StatementCallbackBal>. </soapenv:Body>.</soapenv:Envelope> |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Jan 29, 2011 4:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Okay, so now you know what the failing message from data power looks like.
What does the successful message from your stubs look like. |
|
| Back to top |
|
|
| amit1310 |
| Posted: Sat Jan 29, 2011 6:16 am Post subject: Successful Message from Stub |
|
|
Newbie
Joined: 22 Jan 2011
Posts: 9
|
Hi ,
Thanks for your reply.
Stub message is exactly the same as the one shown in Datapower with 3 differences
1) <?xml version="1.0" encoding="UTF-8"?> is missing from the stub message
2) Stub has <soapenv:Header ></soapenv:Header>
3) Message from Datapower has . after every tag. Ex:. <NS1:bankCode>NEDS</NS1:bankCode>. <NS1:countryCode>ZA</NS1:countryCode>.
Here is the complete message from the Stub
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header />
<soapenv:Body>
<StatementCallbackBal>
<p445:StatementCallbackBalRq xmlns:p445="http://contracts.it.nednet.co.za/services/customer-services/2010-06-11/SwiftCallback">
<p445:BasicHeader>
<p445:logicalTerminalIdentifier>
<p445:bankCode>NEDS</p445:bankCode>
<p445:countryCode>ZA</p445:countryCode>
<p445:locationCode>J0</p445:locationCode>
<p445:logicalTerminalCode>A</p445:logicalTerminalCode>
<p445:branchCode>XXX</p445:branchCode>
</p445:logicalTerminalIdentifier>
<p445:sessionNumber>5075</p445:sessionNumber>
<p445:sequenceNumber>861186</p445:sequenceNumber>
</p445:BasicHeader>
<p445:ApplicationHeaderResponse>
<p445:messageType>941</p445:messageType>
<p445:inputTime>1200</p445:inputTime>
<p445:messageInputReference>
<p445:deliveryDate>110119</p445:deliveryDate>
<p445:logicalTerminalIdentifier>
<p445:bankCode>SBZA</p445:bankCode>
<p445:countryCode>ZA</p445:countryCode>
<p445:locationCode>J0</p445:locationCode>
<p445:logicalTerminalCode>A</p445:logicalTerminalCode>
<p445:branchCode>XXX</p445:branchCode>
</p445:logicalTerminalIdentifier>
<p445:sessionNumber>5075</p445:sessionNumber>
<p445:sequenceNumber>861186</p445:sequenceNumber>
</p445:messageInputReference>
<p445:outputDate>110119</p445:outputDate>
<p445:outputTime>1200</p445:outputTime>
<p445:messagePriority>N</p445:messagePriority>
</p445:ApplicationHeaderResponse>
<p445:identification>SM80594134145048</p445:identification>
<p445:relatedIdentification>LIQUIDTY476</p445:relatedIdentification>
<p445:account>401942279</p445:account>
<p445:Statements>
<p445:documentNumber>337</p445:documentNumber>
<p445:documentSequenceNumber>1</p445:documentSequenceNumber>
</p445:Statements>
<p445:OpeningBalance>
<p445:transactionIndicator>C</p445:transactionIndicator>
<p445:openingBalanceDate>20110119</p445:openingBalanceDate>
<p445:theCurrencyCode>ZAR</p445:theCurrencyCode>
<p445:theCurrencyAmount>93358</p445:theCurrencyAmount>
</p445:OpeningBalance>
<p445:finalClosingBookedBalance>
<p445:transactionIndicator>C</p445:transactionIndicator>
<p445:finalClosingBookedBalanceDate>20110119</p445:finalClosingBookedBalanceDate>
<p445:theCurrencyCode>ZAR</p445:theCurrencyCode>
<p445:theCurrencyAmount>93358</p445:theCurrencyAmount>
</p445:finalClosingBookedBalance>
<p445:finalClosingAvailableBalance>
<p445:transactionIndicator>C</p445:transactionIndicator>
<p445:finalClosingAvailableBalanceDate>20110119</p445:finalClosingAvailableBalanceDate>
<p445:theCurrencyCode>ZAR</p445:theCurrencyCode>
<p445:theCurrencyAmount>93358</p445:theCurrencyAmount>
</p445:finalClosingAvailableBalance>
<p445:forwardAvailableBalance>
<p445:transactionIndicator>C</p445:transactionIndicator>
<p445:forwardAvailableBalanceDate>20110119</p445:forwardAvailableBalanceDate>
<p445:theCurrencyCode>ZAR</p445:theCurrencyCode>
<p445:theCurrencyAmount>93358</p445:theCurrencyAmount>
</p445:forwardAvailableBalance>
</p445:StatementCallbackBalRq>
</StatementCallbackBal>
</soapenv:Body>
</soapenv:Envelope> |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Jan 29, 2011 7:02 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The empty Soap:Header may be important. Try making sure that the datapower message adds it.
Please also look at the REST of the MQ message, aside from just the data portion.
In HTTP, for example, the operation to call is sent in an HTTP Header, not in the HTTP document itself.
The "." is likely the carriage return/line feed that is showing up in the stub, but not being recognized by whatever you are using to display these messages. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jan 29, 2011 8:36 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mqjeff wrote: |
| Please also look at the REST of the MQ message, aside from just the data portion |
You have yet to show us a comparison of the message properties or of the RFH2 if present in any of the messages...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| amit1310 |
| Posted: Sun Jan 30, 2011 2:16 am Post subject: Complete JMS Message |
|
|
Newbie
Joined: 22 Jan 2011
Posts: 9
|
Here is the complete JMS Message, Could you please have a look ?
<Transport_Folders>
<Message_MetaData>
<PayloadType>jms_text</PayloadType>
<MessagePersistence>1</MessagePersistence>
</Message_MetaData>
<Header_Values>
<JMSDestination> </JMSDestination>
<JMSDeliveryMode dt="i4">1</JMSDeliveryMode>
<JMSExpiration dt="r8">0</JMSExpiration>
<JMSPriority dt="i4">4</JMSPriority>
<JMSTimestamp dt="r8">1296337358360</JMSTimestamp>
<JMSMessageID> </JMSMessageID>
<JMSCorrelationID>414d5120513220202020202020202020e042414d20006b02</JMSC
orrelationID>
<JMSReplyTo> </JMSReplyTo>
<JMSType>mcd://XMLNSC/AVF1S48002001/StatementCallbackBalRq?format=XML1</
JMSType>
<JMSRedelivered dt="boolean">FALSE</JMSRedelivered>
</Header_Values>
<Application_Properties>
<contentType>text/xml; charset=utf-8</contentType>
<targetService>SwiftCallbackSoapPort</targetService>
<transportVersion>1</transportVersion>
</Application_Properties>
</Transport_Folders>
<soapenv:Envelope
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<StatementCallbackBal>
<NS1:StatementCallbackBalRq
xmlns:NS1="http://contracts.it.nednet.co.za/services/customer-services/2
010-06-11/SwiftCallback">
<NS1:BasicHeader>
<NS1:logicalTerminalIdentifier>
<NS1:bankCode>NEDS</NS1:bankCode>
<NS1:countryCode>ZA</NS1:countryCode>
<NS1:locationCode>J0</NS1:locationCode>
<NS1:logicalTerminalCode>X</NS1:logicalTerminalCode>
<NS1:branchCode>XXX</NS1:branchCode>
</NS1:logicalTerminalIdentifier>
<NS1:sessionNumber>5075</NS1:sessionNumber>
<NS1:sequenceNumber>861186</NS1:sequenceNumber>
</NS1:BasicHeader>
<NS1:ApplicationHeaderResponse>
<NS1:messageType>941</NS1:messageType>
<NS1:inputTime>1200</NS1:inputTime>
<NS1:messageInputReference>
<NS1:deliveryDate>20100429</NS1:deliveryDate>
<NS1:logicalTerminalIdentifier>
<NS1:bankCode>SBZA</NS1:bankCode>
<NS1:countryCode>ZA</NS1:countryCode>
<NS1:locationCode>J0</NS1:locationCode>
<NS1:logicalTerminalCode>A</NS1:logicalTerminalCode>
<NS1:branchCode>XXX</NS1:branchCode>
</NS1:logicalTerminalIdentifier>
<NS1:sessionNumber>8228</NS1:sessionNumber>
<NS1:sequenceNumber>593064</NS1:sequenceNumber>
</NS1:messageInputReference>
<NS1:outputDate>100429</NS1:outputDate>
<NS1:outputTime>1300</NS1:outputTime>
<NS1:messagePriority>N</NS1:messagePriority>
</NS1:ApplicationHeaderResponse>
<NS1:identification>SM80594134145048</NS1:identification>
<NS1:relatedIdentification>LIQUIDTY476</NS1:relatedIdentification>
<NS1:account>401942279</NS1:account>
<NS1:Statements>
<NS1:documentNumber>337</NS1:documentNumber>
<NS1:documentSequenceNumber>1</NS1:documentSequenceNumber>
</NS1:Statements>
<NS1:finalClosingBookedBalance>
<NS1:transactionIndicator>C</NS1:transactionIndicator>
<NS1:finalClosingBookedBalanceDate>110106</NS1:finalClosingBookedBalance
Date>
<NS1:theCurrencyCode>ZAR</NS1:theCurrencyCode>
<NS1:theCurrencyAmount>13028.00</NS1:theCurrencyAmount>
</NS1:finalClosingBookedBalance>
</NS1:StatementCallbackBalRq>
</StatementCallbackBal>
</soapenv:Body>
</soapenv:Envelope> |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Jan 30, 2011 4:56 am Post subject: Re: Complete JMS Message |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| amit1310 wrote: |
| <targetService>SwiftCallbackSoapPort</targetService> |
|
|
| Back to top |
|
|
|
|
