Skip to Content
author's profile photo Former Member
Former Member

Scenario jms synchronous

Hi everyboy,

The scenario is: R3 -->XI (JMS) ---> MQ -


> XI (JMS) ---> R3

I have a scenario with jms synchronous. I created a correlation to take the correct message from MQSeries. But the correlations works wrong.

I think the instance process doesn't know if it is responsible for the message that MQ return. The correlations is the problem.

Anybody can say me how to correlate jms adapter correctly?

Have anybody got a good manual?

My e-mail is: mpnestar@hotmail.com

Thanks for advance.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Posted on Nov 28, 2007 at 09:03 PM

    Paloma,

    Do you have any primary key kind of association in the request and response messages being processed? Using these in the correlation definition in BPM would be the right way to go with.

    VJ

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 28, 2007 at 10:43 PM

    Have you looked at the Exchange Infrastructure "How To" guide for "How to Correlate JMS"?

    Refer to url Exchange Infrastructure How-to Guides for SAP NetWeaver 2004 [original link is broken]

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 29, 2007 at 09:35 AM

    Hi,

    Mike Hamer, thank you for the manual but is the same I used to create the correlation. Have you used the manual to create correlation with jms? Did it work you correctly?

    VJ, we use to associate the request and response message the conversation-id. We create the correlation with conversation-id in request message and use the correlation in response message.

    Any other suggest??

    Thank you very much.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 30, 2007 at 03:46 AM

    Paloma,

    I am using XI 3.0 with SP16 and revisited the document <b>How To...Correlate JMS Messages</b> to confirm

    3. The Step-By-Step Solution

    3.1 BPM Header-Based …

    Followed the Design steps 1 - 5

    Followed the Config steps

    6. FYI - the JMS-Compliant option is set to JMS-Compliant

    7. FYI - the JMS-Compliant option is set to WebSphereMQ (non-JMS)

    <b>Difference</b> - I have used the Correlation Setting Stored JMSCorrelationId of request

    I have provided a sample and some mapping logic for the application that processes the MQ queue

    <b>Request – note the MessageId and ConversationId</b>

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

    <!-- Response -->

    http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP=" http://sap.com/xi/XI/Message/30">

    <SOAP:Header>

    http://sap.com/xi/XI/Message/30" xmlns:SOAP=" http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu=" http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">

    <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>

    <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>

    <SAP:MessageId>A4869D70-A593-F94A-9716-4353769D5C0C</SAP:MessageId>

    <SAP:ConversationId>6195CFF0-9ECB-11DC-A178-000347055950</SAP:ConversationId>

    <SAP:TimeSent>2007-11-29T22:35:26Z</SAP:TimeSent>

    <SAP:Sender>

    a) XI puts the JMS request message on the MQ request queue

    b) An application reads the request from the MQ request queue and needs to save JMS message id from the MQMD field MsgId

    c) The application then does some action(s)

    d) The application then generates a response message. To correlate this response message back to XI, Adaptris will need to copy the JMS message id from the MQMD field MsgId (saved from the request message) into the MQMD field CorrelId of the response message and then write the message to the MQ response queue

    e) XI reads the JMS response message from the MQ response queue

    <b>Response – note the MessageId is different but the ConversationId is the same</b>

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

    <!-- Response -->

    http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP=" http://sap.com/xi/XI/Message/30">

    <SOAP:Header>

    http://sap.com/xi/XI/Message/30" xmlns:SOAP=" http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu=" http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">

    <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>

    <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>

    <SAP:MessageId>6C5E95C0-9ECB-11DC-A679-000347055950</SAP:MessageId>

    <SAP:ConversationId>6195CFF0-9ECB-11DC-A178-000347055950</SAP:ConversationId>

    <SAP:TimeSent>2007-11-29T22:35:44Z</SAP:TimeSent>

    <SAP:Sender>

    Regards,

    Mike

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.