Sync / Async Bridge without BPM

[Former Member]

Hi All,

I was trying to implement the Sync / Async Bridge without the BPM. I am trying a HTTP to JMS Sync / Async Bridge. I have followed the following link and done exactly the same as shown in the document

http://help.sap.com/saphelp_nw04/helpdata/EN/45/20d2b4c20a0732e10000000a155369/content.htm

I have used a Java application which will poll the request queue and then place the message in the response queue with the same correlation ID frm the request queue.

After following the above link the response message was not appearing, the message were going to deilvering status and after some time i found that they were cancelled without errors

I searched in the forums for many solutions but what i found was this thread which stated that since the XI message ID is 32 bytes and Correlation ID is only 24 bytes its difficult for Modules to identify the response since the correlation is truncated.

I tried changing the configuration in the reciver JMS channel to XI Conversion ID instead of Message ID and this also doesnt give me fruitfull results. The message was not being placed in the request queue, it gave an error saying that the conversion id was null. Though in the thread it seems to have worked for him.

After this i planned to dynamically generate a Correlation ID (a dummy one) of 24bytes and i sent it to the request queue this time the message was retrived from the response queue only to find that the correlation ID this time has been converted to some other format

Corrletion ID sent to the request queue: ABCDEFGHIJKLMNOPQRSTUVWX

Corrlation ID coming in the response queue : 4142434445464748494a4b4c4d4e4f505152535455565758

Can anyone put some light on what i exactly need to do or tell me why the conversion ID worked for Daneil in the thread and it gave me an error saying that the Conversion id is null

Rgds

Aditya

[Former Member · Accepted solution]

Aditya,

Have you read OSS note 1086303? This contains some interesting information on this subject under question 4.

Kind regards,

Koen

[Former Member · Accepted solution]

Hi Koen,

Thanks this note solved the problem. I have awarded full points to you

cheers

Aditya

[prateek]

Make sure that while configuring the communication channels, for receiver under Correlation Settings you have selected "XI Message ID" as the JMSCorrelationID. At sender you should use JMS Correlation ID as the "XIConversationID".

Regards,

Prateek

[Former Member]

Hi Prateek,

This is what was tried in my first case. I did exactly what was given in that link.But since the Message id being 32 bytes and length of correlation id is 24 bytes id is getting truncated.

So its not working fine.

@ke i am having a look at the note will update you on this

Thanks for your response

Rgds

Aditya