Specifying additional JMS message attributes in Sender Adapter

Hi,
Iam using sender JMS adapter and I have to use the option " Specify Additional JMS Message Properties" for adding addtionalJMS properties in XI message header.
Once I cselect the option in the below table Iam not able to add new lines to add addtional JMS Message Properties..But In receiver adapter I was able to add the new lines.
Is this option graded in SAP PI 7.3 or relatd to any authorization issue..?
Is anyone faced this issue before.. Please help me out
Thank you

Hi everybody
I'm starting a project where I have to take adptadores JMS and I'm in the same situation kirian, I am need to configure a JMS adapter with version of SAP PI 7.3 and I wonder if anyone can help me or give me manuals leagues where information comes related.
Someone can help me with this information
Regards

Similar Messages

Specifying Additional Files in an FTP Sender Adapter

Hi,
Has anyone worked out how to specify additional files in a File/FTP Sender Adapter using the FTP transport protocol? This functionality comes 'standard' in the File/FTP Sender Adapter using NFS transport protocol so that additional files can been included as attachments, however, it doesn't seem to be available when trying to use the FTP protocol.
Thanks in advance.
Regards,
Reuben.

Yes this is available in only NFS mode check sap help
http://help.sap.com/saphelp_nw04/helpdata/en/3c/b4a6490a08cd41a8c91759c3d2f401/frameset.htm
Thanks!

Additional JMS Destination Attributes

How can I associate additional attributes to an Administered Object in
          JNDI? Specifically, I want to add a JMS Destination (Queue) to the
          JNDI context. I want the Queue to also have 2 additional attributes
          for my application to process. The additional attributes I need to
          associate with the Administered Queue Object are: Reply-To-Queue and a
          boolean value (log message or don't log message).
          I went into the JNDI namespace (iPlanet Directory Server in this
          case), and manually added additional attributes in the
          javaReferenceAddress. The JMS API did not choke on this, but I can't
          figure out a way to expose this either.


I found that if I in the JMS receiver queue tick Specify Additional JMS Message Properties (Maximum of 10) and provide the name JMSReplyTo and the value Sting I can collect the ReplyTo queue name via a parameter in the operation mapping and the value of that parameter I can set to the Dynamic Configuration variable DCJMSMessageProperty0 in a UDF like this:
String x = container.getInputParameters().getString("replyToQueueName");
DynamicConfiguration conf1 = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION) ;
DynamicConfigurationKey key1 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/JMS", "DCJMSMessageProperty0") ;
conf1.put(key1, x);
return "";

Additional JMS Message Properties

Hi Guru's,
I am looking for a solution to dynamicly set the filename for JMS receiver adapter. What I have found so far is that this should be done with the Additional JMS Message Properties...
Based on a field from the source structure I want to determine the filename which will be send via the JMS adapter. Is there any documentation available on how to achieve this?
Best regards,
Guido Koopmann

I have written an UDF to determine the filename dynamicly:
//write your code here
String str = "SAPDATA-" + a + "ES" + ".xml";
DynamicConfiguration conf = (DynamicConfiguration)
container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey FileName = DynamicConfigurationKey.create("http:/"+"/sap.com/xi/XI/System/File","FileName");
conf.put(FileName, str);
return "";

Setting Adapter-Specific Message Attributes in an Adapter Module

Hi!
I want to set Adapter-Specific Message Attributes in an Adapter Module. Is it possible to configure the Variable Transport Binding in this way?
Best regards,
Daniel

I'd like to know it as well.
I've checked out the XI AF API but didn't find much.
One thing that I've observed is that since Module API can treat any Message Class (not only XI Messages), I guess it won't have any specific methods for XI messages (hence, no dynamic configuration). But you could try to get the message object and then treat it as an XI Message (you would be doing the steps that the Java Mapping API do before it calls a Java Mapping class) to get the Map objects (which include the parameters).
Good luck on it, and let us know if you have any progress!
Regards,
Henrique.

Setting additional JMS message properties

Hi ALL,
I have a requirement where I need to create an adapter module to set additional message property for JMS.
The property name has to be Key_String specifically.
I am not sure whether to specify this name in the code written for the module or in the channel configuration.
Please help.
Thanks n regards
Pushpinder Kaur

You can use adapter specific message attributes for this.
See online help, scroll down to "Advanced Tab Page"
http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm
Hope that helps
Stefan

Attachment of original message in file sender adapter content conversion

Hi,
does anybody know how I can configure a file sender communication channel (with content conversion) so that the original file is added to the XI SOAP message as attachment? Maybe this is just a parameter in "Advanced" tab. (The content conversion itself is not an issue.)
The result should be the "Main Document" (XML-message) and the "original document" as two attachments in the SOAP payload.
The reason for this is that the original file should be archived with the XML message as it was before the XML content conversion of the file sender adapter took place.
Thanks,
Philipp

original file is added to the XI SOAP message as attachment?
The "Advanced" tab -> additional files added in file adapter should act as the attachment to soap receiver adapter if u select the "Keep Attachments" option in soap receiver communication channel.
What do u want to do in FCC is a bit unclear?
Regards,
Prateek

Using adapter specific message attributes in SOAP adapter configuration

Hi,
Can you please let me know how to use adapter specific message attributes in receiver and sender SOAP adapter configuration. If possible , with example.

See here:
Adapter-Specific Message Attributes in the Message Header
http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/frameset.htm
Sender Soap Adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
Receiver Soap Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/frameset.htm

Overwrite Adapter-Specific Message Attributes in MAIL adapter.

Hi guru.
I'm trying to use the SENDER MAIL Adapter.
My scenario is the following:
a remote system send an email with an XML file like attachment. The PI System read the mailbox and tries to map the payload.
When I try without the "Adapter-Specific Message Attributes" the flow work well, but I need to know the email of the sender.
When I try to enable the Adapter-Specific Message Attributes the system finds an error in the SOAP envelop, in the "SHeaderX-CR-HASHEDPUZZLE" Node.
This is a part of the ENVELOP.
<sap:DynamicConfiguration SOAP:mustUnderstand="1">
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTO">email</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SUser">testxi</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-ORIGINATING-IP">[XX.XXX.XX.XXX]</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SGreeting">
Lotus Notes POP3 server version X2.0 ready on xxx.</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderSUBJECT">GROUDWORK_REMOTE</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-MSG-REF">
server-10.XXXX.com!1224858537!24401109!1
</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderMESSAGE-ID"> 00a801c935e4$d4b4e3d0$7e1eab70$
</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-VIRUS-SCANNED">amavisd-new at xxx.com</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-ENV-SENDER">EMAIL</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-STARSCAN-VERSION">5.5.12.14.2; banners=-,-,xxx.it</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-SPAMWHITELISTED">domain whitelist</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-VIRUSCHECKED">Checked</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-MIMETRACK">
Itemize by SMTP Server on IXXX(Release 6.5.5|November30, 2005) at 10/24/2008 16:28:57,Serialize by POP3 Server on IXXX(Release 6.5.5FP2|October23, 2006) at 24/10/2008 16:38:51,Serialize complete at 24/10/2008 16:38:51
</sap:Record>
*THE ERROR IS IN THE FOLLOWING NODE*
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-CR-HASHEDPUZZLE">
7hY= AFac ANQ+ Ad/R ArpP BnYc C6X8 EpvL FLPB GGaw GaCt HKM+ I0Nu JIhk JdJ4 KIZZ;1;dABlAHMAdAB4AGkAQABwAHIAbwB0AG8AdABpAHAAbwAuAGkAdAA=;
Sosha1_v1;7;{CCB182EF-E812-44B6-9C48-85873A18C72};bQBhAG4AdQBlAGwALgBjAGgAaQBhAHIAZQBsAGwAaQBAAGkAbgBmAHIAYQBjAG8AbQAuAGkAdAA=;
Fri, 24 Oct 2008 14:28:46 GMT;RgBXADoAIABDAE8ATQBFAFIAXwBSAEUATQBPAFQARQA=
</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-CR-PUZZLEID">{CCB182EF-E812-44B6-9C48-B85873A18C72}</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderTHREAD-INDEX">
Ack1vUKnx+miPqT4T22mKaVcKhgAvwAAEmwwAAGwdQAABvplAAAAK6sgAAARhjAAAGHCAAAAKwPAAABcPNA=
</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderRECEIVED">
from XXX.com ([xx.xxx.xxx.xx])         by mail3.XXX.com (Lotus Domino Release 6.5.5)         with SMTP id 2008102416285733-32229          for EMAIL ;         Fri, 24 Oct 2008 16:28:57 +0200
</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderDATE">Fri, 24 Oct 2008 16:28:48 +0200</sap:Record>
     <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SServerLocation">pop://popserver</sap:Record>
</sap:DynamicConfiguration>
My question is:
Can I overwrite in the adapter the <sap:Record namespace="http://sap.com/xi/XI/System/Mail" name="SHeaderX-CR-HASHEDPUZZLE"> ?
<post_modified>
Edited by: Juan Reyes on Nov 3, 2008 7:22 PM

Hi
Check the details of the Email in Mail box are all the Adapter specific parameters are coming. If not then this will not read Adapter Specific parameters. Some Legacy system dont generate all parameters But you can add your using variable header.
Thanks
Gaurav

Error while posting messages to SOAP sender adapter SP 13

Hi Friends,
I have configured a SOAP sender adapter in XI 3.0 and is using the URL
http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to post the messages. When I open the URL in the browser I am getting the error.
Message Servlet is in Status ERROR
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_VAL_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal not instantiated
ModuleProcessorRemote not instantiated
But when I test the URL http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_WEBSERVICE:CC_WEBSERVICE_SOAP to check the communication channel I am getting the right response as below.
<?xml version="1.0" ?>
<http://host:port/XISOAPAdapter/HelperServlet?action=FindChannel&channel=:BS_EBTR_WEBSERVICE:CC_EBTR_WEBSERVICE_SOAP> <s:ChannelInfo xmlns:s="http://sap.com/xi/WebService/xi30">
<channelID>e7ac884596ea3d088cbfd8b434f942f2</channelID>
<name>CC_WEBSERVICE_SOAP</name>
<type xmlns:st="http://sap.com/xi/XI/System">st:SOAP</type>
<direction>INBOUND</direction>
<party />
<service>BS_WEBSERVICE</service>
</s:ChannelInfo
I used the http capture to debug, In the 1st case though I am getting "Message Servlet in status error" I am seeing a 200 OK code in the http capture tool. When the message is posted from .net client proxy we are getting a 500 internal server error.
Am not sure what causes the error ? I saw two notes in SDN related to SOAP - J2EE SP13. We are in SP13. Is this the issue ? Wanted to know your opinion before applying the notes.
Thanks & Regards,
Mathew

ABAP & Java stack was on different SP levels.

Adapter specific message attributes for SOAP adapter

Hi all,
I have gone through the SAP Help Documents for configuring SOAP Communication Channel. I am unable to understand how to implement ASMA for Soap adapter.
Please provide some links to help me understand the same
Many Thanks,
Neha

Hi Neha,
pls do chk the below links for SOAP adapter message attributes
http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/content.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst38.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/webservices/webservices16.htm
Regards
Sampath

How to set Priority of JMS message in the Receiver adapter

Hi,
How can I set the priority of message going to MQ in the receiver JMS adapter. I tried to set a value in the <b>JMS message Priroty</b> field. But it is not working.
In the receiving queue manager the default priority of the queue which receives data is set to 0.
Can anyone suggest how to get this done.
Thanks in Advance
Abinash

Hi Ravi,
If I am not wrong You are referring to article <b>Queues for Prioritized Message</b>. But this is about how to Prioritize message inside XI.
What I am intresetd in is to set a message priority (for example "2")for the message going to MQ. That is when the message reached the detination queue the priority of this message should be 2 in the queue.
Thanks
Abinash

Problem in receiving messages via RFC Sender Adapter

Hi,
I have problems in receiving messages from SAP backens systems. Sometimes we are getting all messages sometimes not. Strange.
We are transfering report-results via asynchronous RFC calls. To avoid big message sizes we split them up in max. 1000 rows blocks.
Each RFC call on backend side is completed with COMMIT WORK!
We increased the number of connections in the RFC sender adapter. Then it was better, but the problem still exists! Not so often, but sometimes !?!?!
I hope everybody can help me. Thanks a lot!
best regards,
Hannes

hi,
when you don't receive messages what do you see in SM58
on the r3?
any errors over there?
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Adapter-Specific Message Attributes in MAIL adapter

Hi,
I need to access a ASMA in the mail adapter (SHeaderSUBJECT) but I am not sure the mail client is sending it.
Therefore how can I ensure/make the mail client send this information ?
The e-mail is coming from a Lotus Domino system if this helps in any way.
Cheers
Colin.

Hi,
I have tried using "Mail Package" and the received message looks like this:
*Mail Message*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <xim:Mail xmlns:xim="http://sap.com/xi/XI/Mail/30" encoding="base64">
<Subject>NewFileName.XLS</Subject>
<From>Lawrence.Attrilldomgen.com</From>
<To>axon.maildomgen.com</To>
<Content_Type>multipart/related; boundary="=_related 005864BF802574F2_="</Content_Type>
<Date>2008-10-30T16:02:12Z</Date>
<Message_ID><OFD7EE19C8.01B0E188-ON802574F2.0053C9AA-802574F2.005864C0domgenr5.com></Message_ID>
<X_Mailer>Lotus Notes Release 7.0.2 September 26, 2006</X_Mailer>
<Content>DQotLT1fcmVsYXRlZCAwMDU4NjRCRjgwMjU3NEYyXz0NCkNvbnRlbnQtVHlwZTogbXVsdGlwYXJ0 L2FsdGVybmF0aXZlOyBib3VuZGFyeT0iPV9hbHRlcm5hdGl2ZSAwMDU4NjRCRjgwMjU3NEYyXz0i DQoNCg0KLS09X2FsdGVybmF0aXZlIDAwNTg2NEJGODAyNTc0RjJfPQ0KQ29udGVudC1UeXBlOiB0 ZXh0L3BsYWluOyBjaGFyc2V0PSJVUy1BU0NJSSINCg0KTGF3cmVuY2UgQXR0cmlsbA0KMzc3OSAv IDAyMDggODc5IDg3NzkNCkRvbWVzdGljICYgR2VuZXJhbCBHcm91cCBMaW1pdGVkDQoNCi0tPV9h bHRlcm5hdGl2ZSAwMDU4NjRCRjgwMjU3NEYyXz0NCkNvbnRlbnQtVHlwZTogdGV4dC9odG1sOyBj aGFyc2V0PSJVUy1BU0NJSSINCg0KDQo8YnIDQo8YnIPGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMt c2VyaWYiPjxicj4NCjwvZm9udD48Zm9udCBzaXplPTIgZmFjZT0iVmVyZGFuYSITGF3cmVuY2Ug QXR0cmlsbDxicj4NCjM3NzkgLyAwMjA4IDg3OSA4Nzc5PGJyPg0KRG9tZXN0aWMgJmFtcDsgR2Vu ZXJhbCBHcm91cCBMaW1pdGVkPC9mb250Pg0KPHAPGltZyBzcmM9Y2lkOl8xXzA5MEIxQjc4MDkw QjE3OTAwMDU4NjRCRjgwMjU3NEYyPg0KLS09X2FsdGVybmF0aXZlIDAwNTg2NEJGODAyNTc0RjJf PS0tDQotLT1fcmVsYXRlZCAwMDU4NjRCRjgwMjU3NEYyXz0NCkNvbnRlbnQtVHlwZTogaW1hZ2Uv Z2lmDQpDb250ZW50LUlEOiA8XzFfMDkwQjFCNzgwOTBCMTc5MDAwNTg2NEJGODAyNTc0RjI+DQpD b250ZW50LVRyYW5zZmVyLUVuY29kaW5nOiBiYXNlNjQNCg0KUjBsR09EbGhXUUF0QU5VQUFCY0RC U0FHQ1JZREVRTUJBd2tCRGdrRUZ3UUVCZ2NIQ0FVSUhsWnRybk9IdmFXejFibkUzL3Y4L3ZyNw0K L1FnS0N3SUtBUWNIQS9qemViYWlIdkxRQXVqTUZ2L01BTysvQU4rekFNK21BTCtaQUorQUFJOXpB SUJtQUdCTkFGQkFBRUF6QUNBYQ0KQUJBTkFIQlpBREFtQUF3QkFmLy8vKy92NzkvZjM4N096cisv djZpb3FKK2ZuNCtQajRDQWdIQndjR0ZoWVdCZ1lGQlFVRUJBUURBdw0KTUNBZ0lCQVFFQUVCQVFB QUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQ3dBQUFBQVdRQXRBQUFHLzBDY2NFZ3NHby9J cEhMSg0KYkRxZjBLaDBXVE5aazdZYXpvUmJjYmxJc05BN0xTOXRKcTNMRlNhS2srKzBlWDZNcFlR Mm10MFV3N2xNS1NZb015WmVYemg3TVRZeQ0KZ1dKV0pqT0JNMTF2ZEZBdWQwTXBOVFlwZG14Z2gx czFtNTB2S1RKYmJqZ3BOcDJzYkpaU2pFTXZqNUNRcXFxaGhJOS9Rbkc2WDVPeQ0KVW53emhLMDJM MXVUWEdqQ3JLNnBxTHJBckRqUWxjVk9hSUdJZ1RUTmxGWFJlNm1NZ0t1UktjN2M3L0R4OHZQMDlm Ynd0L242Ky96OQ0KdHhZQUF3b2NTTENnd1lNVy9DbGM2QStodzRjUUdVcWNhQUtpeFlzQ1RUaEl3 TEZqZ2dZZVExb0I2VEVmeVk3NU1LcU1hS0tCZzVjdw0KRzdpVStYS216Sll3SFRSb3lkT2xUdita TzYyc0hIclFTa2lPSjQ4aVBSclVCTk4vQWtIZ3lQQnd4QWlpR1duKzNKcVQ2MDZ0T20vNQ0KdEFr MW9CQ3FDRE1Jd1JwdzVNbWdNbEcyN0xoelk4bWtIL1VOUER1UUE0Z1BHeXhnOENDa2c0VU5oZzkz d0NCNEJBZ1BHb3E2cmRtVA0KNWxleVFIKzJISHN6cFVDK0FVY1EyYUNCaUFXcFZLVXlEa0VFTGNG YmRHRXI3YXcwNU9WSGU2ZCtGbUZCTFlqZU9INmYxcTI2TkE0TA0KSFhBa2ZyMTU1a2ljWTJzMjdh cXpabGk5bjNVRE5BNXdyVytBcUlkandGQ1lzZVM1U0IvaHZmdldvOTBFejNGbmQ4M2RndmZnNElu ag0KWUx5QnlBV0RsV21tbm5VeFhTYmRUMXJ4cEdCdTlLMWwzM0hmRFpmYWZnQmR3SUVRSGdESVUy dzMwUlgvVjNwT0xVVlhiQXBXTkY5QQ0KRjZ4RkhnbkFDUmVlYXNrWlZ0cHZHYmdHMElEWFRRWVha Z2lPMVZ4bjhwbFZ4SEJER0tiV1dvUVJnWUZ4eVNtSGdWWG0zYmplUjdXTg0KNk5HSDZLSEVnQUlM bUNpa2FSbDhnSU1JVndIVUpFQWtDQUVDQ0l3MWljTlZGM1RRd1g5dFFWZWdUMTF4RmxOem0zVzFB SmRlc29XVg0KVVV4VkdaWnRJZTVrMjVaZENpcG9uOVpsVnVCMWVQWjRFNTZYQ3VYb29CUjEycytt bkhvcWFsbWdxblRQcWFnNmNVT3F4YkN3RGF1dw0KcHZGcUU2dkM2Z1FNMzdEeWhRbXVtbkNDQzZU MHNTc2JNZkNSaUsxUGlIRkhKTHNBdzBnTE1xVEJEQzdNbEpKQ3JjZ3VZY3Nkb1RTNw0KeFIrWUtO SUlJYzQ4Z20yMlNjZ3dNd2tMeTNKcmpRa3R3SXVHREdpUUs4MHk2RExoNmgwMHFLTUtEQ2JBc0Vz TDRFQnlnZ25pN0NGTw0Kdmd3MzdQRERFTDhUQkFBNw0KLS09X3JlbGF0ZWQgMDA1ODY0QkY4MDI1 NzRGMl89LS0=</Content>
</xim:Mail>
However, I also have an attached CSV file which I need to pass - I am using the PayloadSwapBean for this.
Therefore, the question I now have is this:
How do I use the <Subject> field from the original received message ? It is lost once I call the PayloadSwapBean so I am stumped on how to get it ?
Any ideas ??
Kind regards
Colin.

JMS adapter: Adapter specific message attributes

Hi,
I have a synchronous SOAP to JMS (MQ series) scenario where Im using sync/async bridge (without BPM).
I need to correlate the message being put on JMS queue (JMS receiver adapter) and the response (JMS sender adapter).
The standard receiver JMS adapter only allows the JMS correlation ID to be set to one of three different values (excluding NULL). 2 of these (reference and conversation ID) will be empty in my scenario, leaving me with only the XI message ID. This ID however exceeds the length of ie. the JMS correlation ID and thus isnt suitable for correlating anything using the field JMS Correlation ID.
NB: it is of no use to try and set the conversation ID at mapping time (using container object) since the changed value only is available during mapping execution.
Surely one way of setting the conversation ID would be to use an adapter module in SOAP sender, but this is not an option. Also the sender system will not provide one either.
Now the problem isnt setting the JMS correlation ID dynamically at runtime (this is achieved without trouble using the dynamic configuration API with the key DCJMSCorreleationID). The problem is to actually have XI correlate the request with the response.
Since the JMS collelation ID is smaller than the XI message ID and the conversation and reference ID isnt available, what I figure is that I need to find a MQ message property to use and then use the Set MSProperty to part instead this property surely needs to be large enough to contain the XI message ID.
So what I did was I looked in http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.amqwak.doc/js50938.htm
where a list of fields in the message descriptor is available figuring I can just use one of these. Looking through the list I notice the field MDRQ (Name of reply queue, 48-byte character string) should be able to hold the XI message ID. So I add MDQR in the Specify additional JMS message properties and set the Java Type to String and also enter this field in the Correlation Setting of the receiver JMS adapter.
Runtime:
When looking in MDT I see:
New JMS message will be correlated with the XI message. Correlation rule: XI_MESSAGEID, correlated property: JMS property MDRM, correlation value: 36158680-5a0c-11dc-8c14-000f203cd3c8
I looks like a success! No data is however set in the field when looking at messages being put on MQ.
If I increase the trace level of the JMS adapter I can see (in defaultTrace) the following:
Cannot read the switch setting for property name DCJMSStringProperty0, switch name dynConfigDCJMSStringProperty0. It is switched off.
What does this error mean?
I have of course clicked Use adapter Specific Message-Attributes and also the Specify additional. In other words everything look ok in configuration.
Since Ive also put a check mark in Fail if adapter specific message attributes is missing I can see that I successfully put a value (using dynamic conf. at mapping time) in the field... but still something isnt right the value of the property never reached MQ.
Now Ive tried with a couple of fields in the message descriptor from the previous URL. XI complains all the time.
Anybody got some ideas?
Best Regards,
Daniel

Hi Vijay,
Thanks for your replay,as per your input i creted dynamic configuration method,
i taget structure luks like this
   <Data>
       <Mesage>
             <gl_update>
                  <header>
                        <ean1>
                        <ean2>
                  </header>
              <gl_update>
       <Message>
i written UDF and mapped to header element gl_update,
but i am getting below error message in MONI
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_ ffjms_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:MT_jms_ _a</SAP:P3>
<SAP:P4>sync_out/Data/Message/ GLUpdate. Values missi~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_ ffjms_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:MT_jms_ asyncout/Data/Message/ GLUpdate. Values missi~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
i want to know i mapped to UDF to GL_Update is is correct, to which element i have to map.
i think there is no prob with UDF,its executing ,giving warning messages
help me on this,
Regaards
Raj

Specifying additional JMS message attributes in Sender Adapter

Similar Messages

Maybe you are looking for