on 11-27-2014 7:37 PM
Hi All,
I have configured sender jms channel to extract RFH2 parameters from jms message to PI. But I am not getting the parameter value to PI and following are the communication channel monitoring entries in RWB..
Channel successfully processed the message 84b16230-d771-470b-1a51-a1fd07a6758c
The JMS property fileName that corresponds to the dynamic header DCJMSMessageProperty0 is missing from the JMS message
ID:414d5120514d44415452414430312020c0026854b2b9f320. Hence it cannot be added as a dynamic header to the XI message 84b16230-d771-470b-1a51-a1fd07a6758c
XI Message ID corresponding to JMS message with ID ID:414d5120514d44415452414430312020c0026854b2b9f320 will be created as a new
GUID with value 84b16230-d771-470b-1a51-a1fd07a6758c
How to solve out this issue and it seems I have done proper configuraitons in PI communication channel. Where the issue was? Any help would be great appreciated..
Thanking you all.
Best Regards,
Ashok.
Hi Ashok,
The problem seems to be in the DCJMSMessageProperty0 configuration in your sender JMS channel. Could you share how have you set this parameter?
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vila,
Thanks for your quick response. I have selected set adapter specific message attributes check box, then Specify additional jms message properties(max of 10) and given the fileName on parameter, advanced tab.
On Module tab, I have configured properties like this...
3 AF_Modules/DynamicConfigurationBean Local Enterprise Bean RFHHEADER
RFHHEADER key.0 read http://sap.com/xi/XI/System/JMS DCJMSMessageProperty0
RFHHEADER value.0 fileName
I have tested with different options. I have removed Module tab configurations and tested. Still error is same JMS propety fileName that corresponds to DCJMSMessageproperty0 is miising from JMD message ID:........ Hence it cannot be added to the dynamic headers tothe XI message..
Please suggest.
Thanks,
Ashok.
Hi Ashok,
1.
check if this helps
2.
Please also make sure you use "JMS compliant mode" if have an MQ scenario.
3.
However, see 's answer here that you probably wouldn't need the adapter module mentioned in Former Member's blog....http://scn.sap.com/message/8041641#8041641
Personally, I think you are pretty far. Looks to me that everything is set up mostly correct but the message doesn't contain the properties. Maybe if 2. doesn't help, you want to deep dive using XPI Inspector to see the bare bone message coming from JMS
HTH
Cheers
Jens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.