cancel
Showing results for 
Search instead for 
Did you mean: 

Inserting custom header fields inside MQRFH2 (JMS Receiver adapter)

Former Member
0 Kudos

Hello,

I have a scenario where PI sends the data to IBM Webspehere MQ version 6.0 using JMS adapter. The requirement of the outbound JMS message is that, we have to add 3 property fields to MQRFH2 header section at <usr> and value of the

properties needs to be fetched from the Message body( business data like VendorID..basically routing information to the supplier)

I started with writing a graphical mapping in and used DynamicConfiguration classes to add message properties in the header. But the result of this mapping is, it adds the custom property fields inside SOAP header of the message but not on JMS header MQRFH2 section.

Any valuable inputs are welcome.

Thanks in advance!

Amulya

Accepted Solutions (1)

Accepted Solutions (1)

rajasekhar_reddy14
Active Contributor
0 Kudos

Hi Amulya,

Here is the solution,

1. In Adapter Specific Message Attributes under the "Advanced" tab, use the table to enter your property names into the table (up to 10)

2. Click on the "Module" tab of the communication channel.

3. In the processing sequence, add a new module called "AF_Modules/DynamicConfigurationBean" type "Local Enterprise Bean" module key "RFHHEADER"

4. You can now enter name value pairs in the module configuration table.. for instance, if you want to assign a value of "TEST" to a property called "Environment" (created in step 1, and first entry in table), then the config would be as follows:

Module Key Parameter Name Parameter Value

=========== ============= =========================

RFHHEADER key.0 insert http://sap.com/xi/XI/System/JMS DCJMSMessageProperty0

RFHHEADER value.0 TEST

repeat using key.1/value.1 etc..

Regards,

Raj

Former Member
0 Kudos

Hi ,

This is veeru. I am doing proxy to jms using websphere mq series. i don't now in header data of the jms adapter . I configure the Jms communication channel but few things i am facing problem . how define in header parameters in module tab please help me this things. my header parameter is BH_heradename,BH_version,BH_debug,etc ..

Best Regards,

Veera.

Former Member
0 Kudos

Hi Raj,

My requirement is to send the PI message id in JMS header properties.I have added dynamic configuration bean in module tab.What else i need to add?

Regards,

Karthiga

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi,

I have a scenario similar to this. But can anyone tell me hvor to get data from the message body to the header fields I have created in the ASMA Properties?

Former Member
0 Kudos

I found one small information missing in the answer (at least when using MQ Series).

In the communication channel, under Parameters --> Target --> Target Client, change the value "WebSphereMQ (non-JMS)" to "JMS-Compliant".

I only managed to get the MQRFH2 header, when the above mentioned setting was changed.

Former Member
0 Kudos

Hi ,

This is veeru. I am doing proxy to jms using websphere mq series. i don't now in header data of the jms adapter . I configure the Jms communication channel but few things i am facing problem . how define in header parameters in module tab please help me this things. my header parameter is BH_heradename,BH_version,BH_debug,etc ..

Best Regards,

Veera.

Shabarish_Nair
Active Contributor
0 Kudos

you can achive it using the Specify Additional JMS Message Properties -> http://help.sap.com/saphelp_nw2004s/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm and filling the values using dyn. conf.

Else you can also use the dynamicconfigurationbean http://help.sap.com/saphelp_nw04/helpdata/EN/45/da2239feb22e98e10000000a155369/content.htm

rajasekhar_reddy14
Active Contributor
0 Kudos

Hi AMuly,

If you want to add MQRFH2 Header,You need to add RFH2 bean in JMS Receiver Communication channel,

after that add 3 property fileds in ASMA Properties.

using Dynamic configuration it wont work.

Regards,

Raj

Former Member
0 Kudos

This message was moderated.

rajasekhar_reddy14
Active Contributor
0 Kudos

This message was moderated.