Setting DCJMSCorreleationID in JMS RECEIVER using Seeburger AttribMapper

Hello
Has anyone managed to set the DCJMSCorreleationID dynamic attribute in a JMS RECEIVER using Seeburger AttribMapper module?
Here is how I configured the JMS_RECEIVER:
In the module tab, I added a new module:
Module Name     Module Type     Module Key
localejbs/Seeburger/AttribMapper     Local Enterprise Bean     map
And I added the following parameter:
Module Key     Parameter Name                                                       Parameter Value
map                     http://sap.com/xi/XI/System/JMS/DCJMSCorreleationID "TEST"
When I process a message, I can see in the adapter engine Audit log the following lines:
SEEBURGER/AttribMapper: Setting dynamic property http://sap.com/xi/XI/System/JMS - DCJMSCorreleationID = TEST
SEEBURGER/AttribMapper: Finished succesfully, 1 properties set or deleted
However looking at the Message Content/SOAP Document, I can see no dynamicConfiguration (it should be the case according to Seeburger documentation).
If I check the message properties on the JMS queue, I can see the correlation ID is not set to TEST.
Any idea?
Thanks in advance!
Greg

Are you using the AttribMapper in the Sender or in the Receiver Channel ? Please be aware that you will not be able to see the change of attribmapper in the message content in receiver channels (they are not updated/persisted there).

Similar Messages

Issue with JMS Receiver Comm. Channel using Seeburger AttribMapper

Hello,
I'm using a JMS_RECEIVER Comm. Channel on which the Seeburger AttribMapper is configured (I need to use the DCJMSCorreleationID dynamic attribute).
In the module tab, I added a new module:
Module Name Module Type Module Key
localejbs/Seeburger/AttribMapper Local Enterprise Bean map
And I added the following parameter:
Module Key Parameter Name Parameter Value
map http://sap.com/xi/XI/System/JMS/DCJMSCorreleationID "TEST"
When processing a message, I get the following error on the Communication Channel Monitoring:
Message processing failed. Cause: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of AttribMapper.
Does anyone has an idea on how to fix this problem?
Thanks for your help!
Benoit

HI,
Refer the discussion of
Setting DCJMSCorreleationID in JMS RECEIVER using Seeburger AttribMapper
Dynamic subject in AS2 receiver
Thanks
Swarup

Problem Encountered in JMS adapter using SEEBURGER module

While testing the receiver JMS adapter for XML to EDI conversion using Seeburger module, I am facing errors.
1. The error encountered is :
Error while processing message '4720bc32-2dfc-03d8-0000-00000a2050d3'; detailed error description: java.lang.NullPointerException at com.sap.aii.adapter.jms.core.connector.SendContextImpl.send(SendContextImpl.java:43) ...
SEEBURGER BICXIADAPTER --- Conversion of synchronous request from module chain ended with errors ---Error: [Error:ID=2061;LEVEL=1] XMLDocReader moveNext(): Cannot move to next trigger : Error in line 1: XML file should begin with white spaces or <. (Found char :U(Hex :85). DESCRIPTION: XMLDocReader Exception: Not able to move to next trigger [not specified] - trigger may not right set.
2. The targer PAYMUL xml is as follows :
( At receiver channel, the above should be converted to EDI-Paymul using the Seeburger Module)
PAYMUL XML
<?xml version="1.0" encoding="UTF-8" ?>
- <LIST>
- <S_UNA>
<D_DELIMITER>:+.? '</D_DELIMITER>
</S_UNA>
- <S_UNB>
- <C_S001>
<D_0001>UNOA</D_0001>
<D_0002>2</D_0002>
</C_S001>
- <C_S002>
<D_0004>SAPDM</D_0004>
<D_0007>ZZ</D_0007>
</C_S002>
- <C_S003>
<D_0010>000000000000</D_0010>
<D_0007>55</D_0007>
</C_S003>
- <C_S004>
<D_0017>070201</D_0017>
<D_0019>1150</D_0019>
</C_S004>
<D_0020>01945678912345</D_0020>
- <S_UNH>
<D_0062>1</D_0062>
- <C_S009>
<D_0065>PAYMUL</D_0065>
<D_0052>D</D_0052>
<D_0054>96A</D_0054>
<D_0051>UN</D_0051>
<D_0057>FUN01G</D_0057>
</C_S009>
- <S_BGM>
- <C_C002>
<D_1001>452</D_1001>
</C_C002>
<D_1004>01945678912345</D_1004>
<D_1225>9</D_1225>
</S_BGM>
- <S_DTM>
- <C_C507>
<D_2005>137</D_2005>
<D_2380>20070201</D_2380>
<D_2379>102</D_2379>
</C_C507>
</S_DTM>
- <G_SSG4>
- <S_LIN>
<D_1082>1</D_1082>
- <S_DTM>
- <C_C507>
<D_2005>203</D_2005>
<D_2380>20070201</D_2380>
<D_2379>102</D_2379>
</C_C507>
</S_DTM>
- <S_RFF>
- <C_C506>
<D_1153>ACK</D_1153>
<D_1154>01945678912345</D_1154>
</C_C506>
</S_RFF>
- <S_RFF>
- <C_C506>
<D_1153>AEK</D_1153>
<D_1154>01945678912345</D_1154>
</C_C506>
</S_RFF>
- <S_BUS>
<D_3279>IR</D_3279>
- <C_C551>
<D_4383>UGI</D_4383>
</C_C551>
</S_BUS>
- <G_SSG5>
- <S_MOA>
- <C_C516>
<D_5025>9</D_5025>
<D_5004>5000</D_5004>
<D_6345>EUR</D_6345>
</C_C516>
</S_MOA>
</G_SSG5>
- <G_SSG6>
- <S_FII>
<D_3035>OR</D_3035>
- <C_C078>
<D_3194>ES921998500000000012</D_3194>
<D_6345>EUR</D_6345>
</C_C078>
- <C_C088>
<D_3433>ABNAES17000</D_3433>
<D_1131>25</D_1131>
<D_3055>5</D_3055>
</C_C088>
<D_3207>ES</D_3207>
</S_FII>
</G_SSG6>
- <G_SSG7>
- <S_NAD>
<D_3035>OY</D_3035>
- <C_C080>
<D_3036>XYZ CORPORATION LTD</D_3036>
</C_C080>
- <C_C059>
<D_3042>XX</D_3042>
</C_C059>
<D_3164>XX</D_3164>
<D_3207>ES</D_3207>
</S_NAD>
</G_SSG7>
- <G_SSG11>
- <S_SEQ>
- <C_C286>
<D_1050>1</D_1050>
</C_C286>
- <S_MOA>
- <C_C516>
<D_5025>9</D_5025>
<D_5004>5000</D_5004>
<D_6345>EUR</D_6345>
</C_C516>
</S_MOA>
- <S_DTM>
- <C_C507>
<D_2005>227</D_2005>
<D_2380>2007-02-01</D_2380>
<D_2379>102</D_2379>
</C_C507>
</S_DTM>
- <S_RFF>
- <C_C506>
<D_1153>AIK</D_1153>
<D_1154>01901234567890</D_1154>
</C_C506>
</S_RFF>
- <S_RFF>
- <C_C506>
<D_1153>CR</D_1153>
<D_1154>01901234567890</D_1154>
</C_C506>
</S_RFF>
- <S_FCA>
<D_4471>13</D_4471>
</S_FCA>
- <G_SSG12>
- <S_FII>
<D_3035>BF</D_3035>
- <C_C078>
<D_3194>AT921998500000000011</D_3194>
<D_6345>EUR</D_6345>
</C_C078>
- <C_C088>
<D_3433>ABNAAT14000</D_3433>
<D_1131>25</D_1131>
<D_3055>5</D_3055>
</C_C088>
<D_3207>ES</D_3207>
</S_FII>
</G_SSG12>
- <G_SSG13>
- <S_NAD>
<D_3035>BE</D_3035>
- <C_C080>
<D_3036>ABC CORPORATION 1</D_3036>
</C_C080>
- <C_C059>
<D_3042>XX</D_3042>
</C_C059>
<D_3164>XX</D_3164>
<D_3207>ES</D_3207>
</S_NAD>
</G_SSG13>
- <G_SSG16>
- <S_PRC>
- <C_C242>
<D_7187>11</D_7187>
</C_C242>
- <S_FTX>
<D_4451>PMD</D_4451>
- <C_C108>
<D_4440>SENDERPN1</D_4440>
</C_C108>
</S_FTX>
</S_PRC>
</G_SSG16>
</S_SEQ>
</G_SSG11>
</S_LIN>
</G_SSG4>
- <S_CNT>
- <C_C270>
<D_6069>2</D_6069>
<D_6066>1</D_6066>
</C_C270>
</S_CNT>
- <S_UNT>
<D_0074>1</D_0074>
<D_0062>1</D_0062>
</S_UNT>
</S_UNH>
- <S_UNZ>
<D_0036>1</D_0036>
<D_0020>01945678912345</D_0020>
</S_UNZ>
</S_UNB>
</LIST>
3. The module parameters for Seeburger inputs :
( In receiver communication channel)
Processing Sequence
localejbs/CallBicXIRaBean Local Ent Bean x2e_bic_paymul
SAP XI JMS Adapter/ConvertMessageToBinary Local Ent Bean convert_XI2Bin
SAP XI JMS Adapter/SendBinarytoXIJMSService Local Ent Bean
 exit
Module Key
x2e_bic_paymul destSourceMsg MainDocument
x2e_bic_paymul destTargetMsg MainDocument
x2e_bic_paymul logAttID ConverterLog
x2e_bic_paymul mappingName See_X2E_PAYMUL_UN_D96A
x2e_bic_paymul newLine true
x2e_bic_paymul saveSourceMsg XMLEDI

Hi,
Check Below links,
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
Regards,
Phani

Configuration of JMS receiver Using Jboss JMS provider

Hi all..
I am configuring JMS adapter as receiver.
I am using JMS provider JBOSS .
I hav done configuration as
Transport protocol :Acess JMS provider with JNDI
JNDI lookUp Name of q connection factory: org.jboss.naming.LinkRefPairService
Name of JNDI initial Context factory :org.jnp.interfaces.NamingContextFactory
in sxmb_moni I am getting blak&white flag
IN Run time work bench In adapter monitoring I am getting
Receiver channel. Details: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory.
Can anybody plz tell me why this haapend?

Did you deploy the JMS client jars to the J2EE Engine?
Cannot instantiate class: org.jnp.interfaces.NamingContextFactory sounds like the Framework can't find the class.
Take a look here:
Re: Using JBOSS JMS provider with XI
Greetz
Sebastian
Message was edited by: Sebastian Simon

JMS/AQ: Setting properties for JMS message using PL/SQL

I have created a procedure in PL/SQL that uses JMS messages, and now I need to include a property so that the subscriber can use a message selector to filter out unwanted messages. Is this possible using PL/SQL?
A previous post said: "... But you can have properties in the message payload itself and also define selectors on the message content ...". But I looked at Sun's tutorial and there it said: "A message selector cannot select messages on the basis of the content of the message body."
I have 300 different screens and messages apply only to one screen at a time. When the user is looking at screen 'A' I want him to only recieve messages that apply to screen 'A'. I thought I would do this with message selector, but is there any other way?
Here is my code(borrowed from an earlier post)
PROCEDURE ENQUEUE_JMS_MESSAGE AS
BEGIN
DECLARE
Enqueue_options DBMS_AQ.enqueue_options_t;
Message_properties DBMS_AQ.message_properties_t;
Message_handle RAW(16);
User_prop_array SYS.AQ$_JMS_USERPROPARRAY;
Agent SYS.AQ$_AGENT;
Header SYS.AQ$_JMS_HEADER;
Message SYS.AQ$_JMS_TEXT_MESSAGE;
Message_text VARCHAR2(100);
BEGIN
Agent := SYS.AQ$_AGENT('',NULL,0);
User_prop_array := SYS.AQ$_JMS_USERPROPARRAY();
Header := SYS.AQ$_JMS_HEADER( Agent, '', 'aq1', '', '', '', User_prop_array);
Message_text := 'Message 1 from PL/SQL';
Message := SYS.AQ$_JMS_TEXT_MESSAGE(Header, LENGTH(Message_text), Message_text, NULL);
DBMS_AQ.ENQUEUE(queue_name => 'tstopic',
Enqueue_options => enqueue_options,
Message_properties => message_properties,
Payload => message,
Msgid => message_handle);
END;
END;
-Christer

Thanks for the answer. I managed to set the Correlation id and retrieve it using getJMSCorrelationID(). But I did not manage to use the MessageSelector on it. I have used the Topicbrowser which is not part of the JMS standard? I tried to enqueue the messages using Java too and tried to use the topicbrowser on both JMSCorrelationID and user defined properties withou success. Is there some special requirements of the TopicBrowser?
Enumeration messages;
oracle.jms.TopicBrowser browser =tsess.createBrowser(topic, "TS", "JMSCorrelationID = 'TST'");
int count = 0;
messages = browser.getEnumeration();
if(messages.hasMoreElements())
System.out.println("message"); //never executed
dtxtmsg = (TextMessage)(tsub1.receiveNoWait()) ; //returns a message
String corrID = dtxtmsg.getJMSCorrelationID(); //returns: TST
Thanks for your help so far...it would really save my day if you have some ideas on this too!
-Christer

Set JMSType in JMS Receiver

Hello.
I have to send a JMS Message to MQ Series and can not set the JMSType (is a JMS Header property). Any know about this ? Thanks.

Hey
This needs to be set in UDF in message mapping and use the technical name DCJMSType.check the below two links
http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
set it the way attributes are assigned in the below blog
Dynamic Configuration of Some Communication Channel Parameters using Message Mapping
Thanx
Aamir

How to set values in JMS Adapter using Adanced specific Message Attributes

Hi Frnds,
in my scenarios i have to add extra header information MQ Message,
using Adanced specific Message Attributes i defined 7 parameters(Transaction,Environment,shema......) all are type Interger.But i have to set values ( Transaction type,Enviroment,shema....).
Where i can set values ??
help me on this...
Regards,
Raja Sekhar

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

Can't set phone up to receive wifi

I am unable to set my 4s to receive/ use wifi.
I've tried resetting, turning it off,and still the wifi remains off

http://support.apple.com/kb/TS1559

JMS Receiver - set DCJMSMessageProperty value dynamically from message

Hi,
I have a JMS Receiver where I want to set a DCJMSMessageProperty value to a value from the message contents
For example:
Scenario 1:
Message content field <EANCode>123456</EANCode>
DCJMSMessageProperty6 should be set to 123456 in this instance
Scenario 2:
Message content field <EANCode>99999</EANCode>
DCJMSMessageProperty6 should be set to 99999 in this instance
I know how to set this property to a fixed value using the module DynamicConfigurationBean but do not know how to make this value to use message content.

Hi,
As stated earlier, I need to set DCJMSMessageProperty on the communication channel to a value held in the content not a fixed value.
I will use a UDF to do this now as there are only certain dynamic values you can use using the DynamicConfigurationBean such as message ID, interface name etc. I want to use something in the content so a UDF should be able to do this.
Cheers
Colin.

This is regarding CBMA in SAP PI 7.3.1. I have set up the alert mail using default java mail client.I do receive the alerts via mail. But my requirement is to direct all the mails to Business workplace inbox in ECC.

This is regarding CBMA in single stack SAP PI 7.3.1. I have set up the alert mail using default java mail client.I do receive the alerts via mail. But my requirement is to direct all the alert mails to Business workplace inbox in ECC.
So I need to set up PI to redirect mails to ECC Business workplace user inbox (sbwp). From here rules are set up & routed per distribution list.
Please guide me how I can achieve this requirement.

Hi,
yes, it is a little bit different. This is the issue.....
But I am not sure if your links will help:
1) /people/william.li/blog/2008/02/13/sap-pi-71-mapping-enhancements-series-using-graphical-variable
is about a different solution. I do not need to count the number of lines of the source message.
And the second variable is about concat line by line from unbound node to unbound node.
My issue is:
Souce:
Message line (0...unbound) ! ! ! ! ! ! ! !
.    ResultLine   (1..1)
Mapping:
=>   ResultLine1
       ResultLine2
       ResultLine........          => into UDF to an element (1..1) in one mapping operation.
So that all "ResultLine"s are included.
The result is explained in the given link for Mail attachment with UDF.
So I am not sure how to use this thread for my issue.
In the comments of that blog Christoph Gerber writes that the new variable feature can only handle single values.
So it is not suitable for my purposes as I have a list of values here that needs to be moved into the target message field.
2) http://wiki.sdn.sap.com/wiki/display/Java/UsingEditJavaSectioninMessageMapping
shows where to find the button "Java section" which is not available here in 7.1
3) /people/sap.user72/blog/2005/10/01/xi-new-features-in-sp14
too is about the nice little button for Java Section that is no longer existing on PI 7.1 screen for mappings.
So my issue is: How to replace the Java section function with global variables in PI 7.1?
Best regards
Dirk

JMS Receiver Adapter, using JMS Properties

Hello,
with XI SP14 i should be able to set JMS Properties using Adapter Specific Message Attributes DCJMSStringProperty1 and DCJMSStringProperty2. I set the Elements DCJMSStringProperty(1,2) during java mapping and everything works fine. i can see the "DynamicConfiguration" in the Message monitoring appearing with the correct values.
In the configuration of the adapter specific attributes i give the message properties names and hope the adapter will pass the the values to the jms (IBM MQ implementation) but in jms no properties appear.
has anybody a hint for me, has anybody faces similar issues.
best regards,
roland

Hi Prasad
You can use a simple user defined function. The question is, to which destination element should the function be connected to? I tried to connect to the root element of the destination structure (as dummy) and it worked.
I prefer JAVA Mapping it's more transparent and reusable.
Btw. My original problem remains still unsolved. Our IBM MQ still cannt see the JMS Properties.I contacted SAP for this matter, I will provide you with the solution when there is any.
Greetings
Roland
Message was edited by: Roland Stellmach

How to modify Fileadapter filename with val from JMS msg using xsl?

In my case I need to name the file based on information received in a JMS message.
I would like to receive an xml document from a JMS queue, the document will contain content as well as the name of a file to be saved off. I found references to something similar in the BPEL and ESB documentation for the file adapter by using "ehdr:setOutboundHeader(" as a means to set the outbound header value but I cannot find the mechanics of how to accomplish getting that set with a value that is selected from an incoming message in XSL code.
The examples shown indicate the creation of a pass through mechanism that would take a message from a request header and pass it along to the outbound header which is great but I need a snippet of code to get me through setting the outbound header with an element value that is sourced from the inbound message.
I also found an incomplete reference in a "Oracle SOA Suite Enterprise Server Bus" powerpoint presentation that indicates JMS custom properties support for "Property[@name="Country"]/@value" but no details were provided to assist further.
I would greatly appreciate any information you can provide.
Thank You,
John

Ok I was able to get fileadapter filenames modified.
First you cannot do this after a dbadapter query as that functionality seems to be broken. The best way to solve it for me was to simplify the problem, I started with placing the setoutbound header data after reading a simple file and ignoring the files content altogether. I do the set inside a match of the xslt using a constant value, again for simplicity. For the test just put in 'ateststring.txt' in the setoutbound header call, no need to select data from the document at this point; we will get to that. Now get that to work.
Once you have that working take a value from the incoming document and select it into a variable named myvariable then replace the 'ateststring.txt' with $myvariable. So basically its a three step process for the final solution. Select the data of interest from the document into a variable. add a select statement to make the method call just after that. Make the method call inside the select statement and prepend the variable name with the $ symbol.
So far I have only tested this file to file and file to ftp, I suspect that jmsadapter to file will work fine too. So the trick for me was to understand that if an incoming document is the result of a query that just wont do. My requirement was to take an input JMS request, use that to drive a query, take the data from the query and write it to a filename as defined in the JMS request. No matter what I did to set the frustrating fileadapter/ftpadapter filename in the header I was unable to do so. I used constant strings etc in every part of the document ( before select, inside select, outside select etc ). It wasnt until I went file to file that I was able to get this to work at all. And then not in the xslt header etc, it MUST be in an area of the document that resulted in a select match, which after review makes sense.
To work around the query to file issue, I place the results of the data query into a temporary filename%SEQ%.tmp, along with the query results I add the real filename inside the document. I have a file listener that listens for the filename using wildcards filename*.tmp, it takes the file reads it in, pulls the permanent filename from the incoming document, and sets that filename in the header using the steps worked out above by selecting the filename into myvariable.
You cannot ( to my knowlege ) store variables in ESB so I found I had to put them inside the documents to move the data around. When I am all done with the work through the routing service I strip out the variable data fields that I needed to carry along with the data.
I hope this saves someone else a bit of frustration!
John

JMS Receiver Adapter Catching MQ Exceptions

Hi Experts,
We are running into an issue with our JMS receiver adapter failing PI. We are trying to send transactions via the adapter to a MQ Series' queue but it is failing after no transactions have been sent after a period of 3 hours or more. The only way we can flush the queue is to change the setting on the adapter to Bypass, restart the adapter and then resend the message. Once we do this, everything runs fine throughout the day. It seems to be the amount of time between transactions be processed on the queue.   For instance, last night the last transaction processed successfully was at 7:36pm EST. Then around 11:40pm EST we tried sending another and this is when we caught an exception from MQ once again. We have tried everthing that we know of u2013 we thought it might have been a background job running on PI that causes the issue but last night proved that it wasnu2019t the issue since it occurred before midnight. I feel that the issue is between our JMS connection and your MQ. Below is the message log of the transaction:
What course of action should we take next in diagnosing the issue?
Audit Log for Message: 1c728f10-2044-0441-0a04-604e2cf00000
Time Stamp     Status     Description
2009-05-21 22:40:48     Success     Message successfully received by messaging system. Profile: XI URL: http://bus0157:52000/MessagingSystem/receive/AFW/XI Credential (User): PIPISUSER
2009-05-21 22:40:48     Success     Using connection JMS_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2009-05-21 22:40:48     Success     Message successfully put into the queue.
2009-05-21 22:40:48     Success     The message was successfully retrieved from the receive queue.
2009-05-21 22:40:48     Success     The message status set to DLNG.
2009-05-21 22:40:48     Success     Delivering to channel: JMS_IDOC_SPK_RCV
2009-05-21 22:40:48     Success     MP: Entering module processor
2009-05-21 22:40:48     Success     MP: Processing local module localejbs/SAP XI JMS Adapter/ConvertMessageToBinary
2009-05-21 22:40:48     Success     MP: Processing local module localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService
2009-05-21 22:46:48     Error     MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP
Time Stamp     Status     Description
2009-05-21 22:46:48     Error     Exception caught by adapter framework: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP?targetClient=1 JMSReplyTo:      null JMSRe
2009-05-21 22:46:48     Error     Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_IDOC_SPK_RCVon node: 203518650 having object id: 61da4c76acec3b989e9adbc641058f03 encountered error: MQJMS2007: failed to send message to MQ queue in sending to destination queue:///BDR.TO.SPKREDP?targetClient=1, the message message: JMS Message class: jms_text JMSType:         null JMSDeliveryMode: 2 JMSExpiration:   0 JMSPriority:     4 JMSMessageID:    null JMSTimestamp:    1242963648113 JMSCorrelationID:1c728f10-2044-0441-0a04-604e2cf00000 JMSDestination: queue:///BDR.TO.SPKREDP.

Ok, would you mind taking a look at my forum question titled "Multiple Message Types into one Websphere Message Queue", it may be an easy one for you since you are already doing this!
Best regards,
Aaron
[Multiple Message Types into one Websphere Message Queue|Multiple Message Types into one Websphere Message Queue]

Convert UTF-8 to ISO-8859-1 in JMS receiver

Hi Freinds,
We are sending an XML message to the MQ via JMS receiver channel and I need to change the character set from UTF-8 to the ISO-8859-1 while sending it to the MQ queues. Will this be possile?
Please suggest how can I acheive this.
Regards,
Kumar.

Hi Kumar,
Try changing the encoding using XSLT mapping and you can call this mapping as shown in this blog:
/people/michal.krawczyk2/blog/2005/11/01/xi-xml-node-into-a-string-with-graphical-mapping
or try this wiki page:
http://wiki.sdn.sap.com/wiki/display/XI/SOAPMessagesin+XI
Regards
Suraj

JMS receiver adapter configuration error

Hi All,
I am facing an issue with JMS receiver adapter. My Configuration parameters for receiver adapter are as follows.
1.Transport protocol:WebspherMQ (MQSeries) JMS provied
2.Message porotocol:JMS 1.x
3.Adapter Enigen: Integration Server
4.QueueConnecation Factory Java Class:com.ibm.mq.jms.MQQueueConnectionFactory
5.Queue Java Class:com.ibm.mq.jms.MQQueue
6.IP Address or server name:<Host Name>
7.Server port:1414
8.Queue Mannager Name:TestQM
9.channal name:Recv_Channel
10.JMS queue:SAP_PI
11.Transport/netwrok protocol:TCP/IP
12.JMS compliant:WebSpherMQ(non jms)
13.Delivery mode of message Producer:Persist JMS Messages in the JMS provider
14.Mapping of message:Message Payload=JMS Payload
In adapter monitor, the adapter status shows below error.
Receiver channel. Details: (No detail information set.)
I have already installed the external drivers for JMS adapter. Can someone help me if I am missing some parameter in the above configuration.
Thanks in advance
Regards,
Ashish

Hi,
I am getting the below error in Audit Log.
Error - Exception caught by adapter framework: The JMSSender returned no JMSTextMessage to use. Must abort send process.
Error - Delivery of the message to the application using connection AFW failed, due to: The JMSSender returned no JMSTextMessage to use. Must abort send process..
Can someone please help me in resolving this issue...
Thanks in advance.
Regards,
Ashish

Setting DCJMSCorreleationID in JMS RECEIVER using Seeburger AttribMapper

Similar Messages

Maybe you are looking for