Quantcast
Channel: SCN : Unanswered Discussions - Process Integration (PI) & SOA Middleware
Viewing all articles
Browse latest Browse all 6719

JMS TO PROXY scenario

$
0
0

Hi @all,

 

i've implemented an async scenario:

JMs to PROXY

PROXY to JMS(way back, response)

 

Backend is ECC 6.0 and Middleware is PI 7.1.

 

Business Case: Run a request with a number, get an answer back with an entry. The number is an individual criteria which is not included in the answer. So I decided to write the number in JMSCorrelationID, therefore I've written an UDF in Message Mapping.

I've checked the JMS Correlation ID in additional properties and also added this into the list of additional properties:

key.0 -> read xxxx DCJMSCorreleationID

value.0 -> DCJMSCorrelationID.

 

First question: is there something what I should account for in JMS receiver channel?

 

At the way back I've implemented another UDF for writing the JMSCorrelationID back to payload in message mapping.

But I'm not sure that works. The coding looks like:

 

try

{

 

DynamicConfiguration conf = (DynamicConfiguration)

container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);

DynamicConfigurationKey KEY_JMSCorrID = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/JMS","DCJMSCorrelationID");

 

String a = conf.get(KEY_JMSCorrID);

 

}

catch(Exception e){}

return a; //a is an input field for the payload back to SAP backend.

 

Second question: is there something what I should accound for JMS sender channel? Do I need to add the DCJMSCorreleationID to the list of additional properties (JMS Correlation is checked)?

 

Thanks in Advance,

 

vijender


Viewing all articles
Browse latest Browse all 6719

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>