JMS Receiver channel : No Correlation ID

Hi,
JMS Receiver channel to WebSphere MQ,
I want to put a message on the queue with correlation ID left blank (= no correlation ID), because this causes problems on the receiving side.
Is there a way to achieve this?
I have tried several different settings, but the message appears always with correlation ID.
Kind Regards
Edmond Paulussen

I think you should use the notify response bean on the sender channel
Configuring the Sync/Async Bridge Using the JMS Adapter - Adding Modules to the Module Processor - SAP Library
Sync/Async communication in JMS adapter without BPM (SP19)

Similar Messages

Error in JMS receiver channel

Hi,
I have a JMS receiver channel which is connected to message queue of TIBCO which is working fine.
But if I use the same channel after a day it goes into error and after restart of the channel it again works fine.
Error: Message process failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Unable to write newJMS Message body for message: 343241-......... Connector Exception: ... session ended..
Thanks,
Aravind

Hello Aravind,
I have made similar experiences while accessing JMS queues.
Maybe the JMS queue was not available for a short time. So the receiver channel could not connect.
Best regards,
André

JMS Receiver channel EOIO

Hi,
In SAP help, for one of the parameters of JMS Receiver channel it is mentioned that:
Delivery Mode of Message Producer :
Specify the quality of service of the message producer. You have the following options:
u2022 Persist JMS Messages in the JMS Provider
u2022 Do Not Persist JMS Messages in the JMS Provider
Does this means EOIO/EO. I have proxy to JMS scenarios & like to send the data to JMS in EOIO.
We are using Transport Protocol " Access JMS Provider with JNDI"
With this I want to achieve, EOIO for Proxy to JMS. Pls let me know if Delivery Mode of Message Producer parameter would help & what should be the value.
Thanks.

Exactly Once messages are handled by default using status information in the J2EE server. All adapter error statuses and program terminations initialized externally are also handled in this mode. i.e.
= persist jms messages in the jms adapter.
Now if you specifically want to have dedicated queue; check manage queues under SXMB_ADM.
See if you can set dedicated queue to your interface so that the messages can be processed in the sequence they have received.
Also, once it is out of PI into target system (queue) the order will be maintained.
Cheers!

Heartbeat possibilty in JMS receiver channel?

Hi,
Does anyone know if it is possible to define a heartbeat interval in JMS receiver channels.
Is there maybe a possibility in the additional JMS paramters fields?
We need this to prevent connections being shut down by firewalls due to long inactivity. Once a JMS receiver channel is inactive due to this there is no automatic activation of the channel possible (I think).
The sending JMS channels pose no problem since XI AF seems to poll these every 5 seconds and thu sthe connection remains alive.
thanks
Tom

Hi Shai,
We are using XI 7.0 with SP 12 and we entered this parameter in advanced settings in JMS receiver adapter called "CONNECTION_TEST_POLL" as true and it does the polling to see if the adapter is active...
Hope this helps.
Regards,
TJ

Error with JMS receiver channel

Hi,
We have a scenario in which Order response will be sent from ECC to WebLogic (JMS system) through PI.
After the restart of JMS, we are facing issues with JMS receiver channel.
Some of the responses are delivered, and for few we have the error as described below.
Also, one of the cluster node of the JMS receiver channel has the below error.
Please anybody throw some light on this.
Error description:
" 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: Pending message discovered: dfff2e2b-80f5-94f1-a068-001cc4d99b3e.The channel is configured throw an recoverable, temporary error for this warning (default). Decide whether you want to bypass this message. If so, set the Pending Handling channel parameter to 'Bypass' and restart the message afterwards.. "
Thanks in advance.
Regards
Bhanu Tiruveedula.

Hello Bhanu,
we have been getting this error from long time with JMS channel but no solution except changing the configuration so that it can throw exception and move on.
we have also noticed that this happens for some time and then gets resolved automatically. so it seems to be some data which is not expectable by jms channel.
regards,
Ratna

JMS receiver channel Error !!

Hi All,
We are facing problem in all JMS receiver communication channels, all rcevr channels are failing with following error,
Error while processing message '498499a3-e65c-0086-e100-80000a05260c';
detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Pending message discovered: 498499a3-e65c-0086-e100-80000a05260c.
The channel is configured throw an recoverable, temporary error for this warning (default). Decide whether you want to bypass this message. If so, set the Pending Handling channel parameter to 'Bypass' and restart the message afterwards. at
com.sap.aii.adapter.jms.core.channel.filter.OutboundDuplicateCheckFilter.filter(OutboundDuplicateCheckFilter.java:153) ...
does anybody know whats the exact error??
is it due to Adpater engine message buffere is full ?
regards
biplab

Biplap,
1) Did you restarted the Java Engine ? If so deactive & active the JMS Adapter,
2)Check any EOIO message got struck in Adapter Engine ( RWB-Communication channel- JMS Adapter )
3) Sxmb_moni - Look for the below message status - 498499a3-e65c-0086-e100-80000a05260c
Cheers
Agasthuri Doss

Re-using JMS Receiver Channel

Hi,
I have scenarios with SAP -> PI -> 2 Different External Parties.
External Parties use JMS.
There are some flows which are common for both the parties, like sending Acknowledgement from SAP to JMS.
Now can I just configure one common Receiver Communication Channel and Send message (Acknowledgement) to any of the two Parties? So I will have two Receiver Agreements using the same Receiver JMS channel.
Like by using some concept can I populate JMS channel parameters like IP Address or Server Name , JMS Queue
Thank you,
Pankaj.

Hi,
You need as many receiver channels as you have JMS queues. When you have 60 JMS queues, then you need 60
channels.
I have only 6 queues; one each for one Party.
When you send all messages to same JMS queues and receiver can identify the message type anyhow, then you need
only one channel for this queue.
Ok.
But even when you have only one JMS queue, you might need seperate channels anyway, for example when you use
FCC for each interface individually.
So basically if the setting is different then I need to have that number of channels. the way messages are sent is the same in all the cases. Even when we are using Dynamic Configuration it is the same for all the messages to be send to the External Party.
Thank you,
Pankaj.

Error in JMS receiver channel - XI - Weblogic

Hi Experts
We are also having the situation that we are sending messages from XI to Weblogic server with the help of JMS Adapter. The Queue is available in Weblogic server.
Our configuration of JMS receiver Adapter is
JNDI Lookup Name of Queue Connection Factory----
ConnectionFactory
JNDI Lookup Name of JMS Queue----
queue/IntegrationQueue
Name of JNDi Initial Context Factory: -
weblogic.jndi.WLInitialContextFactory
JNDI Server Address:----
weblogic server ip
JNDI Logon User: -
user
JNDI Password: -
password
We are getting the error in the adaptor like " com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA:"
Could you please tell me if there are any other JAR files for this as i have already deployer weblogic.jar. If yes, Can you please give me some more details on that.
Thank you very much for your time and help.
Manjunath
Edited by: Manjunath Achar on May 23, 2010 4:12 PM

Hi Manju
There could be some problem while deploying the libraries. please check you have deployed the JAR Files correctly.
You need to include the Weblogic Thick client driver 'weblogic.jar' - with all classes under the package 'javax.jms' removed in your aii_af_jmsproviderlib.sda (releases 3.0/7.0) or com.sap.aii.adapter.lib.sda (releases 7.1).
The below links might be helpful for you,
http://wiki.sdn.sap.com/wiki/display/XI/FAQ+J2EEJMS+Adapter
Note 1090516 - XI JMS Adapter and BEA Weblogic JMS: FAQ
Regards
Ramg

Sync/Async communication with JMS Receiver

Hi all,
I am working on one Sync/Async model without BPM. Sender is RFC which is expecting some response, but we know receiver jms doesnt support response message directly. For this i used modules provided by SAP.
While developing interface i used below objects.
One Outbound Synchronous interface--> for Sender RFC channel
Inbound Synchronous Interface----->for Receiver JMS Channel
outbound asynchronous interface--->for Sender JMS channel
one request mapping and one response mapping
Operational mapping between outbound Synchronous to inbound synchronous.
ID Objects:
2 sender agreements: one with sender jms channel
one with sender rfc channel
1 receiver agreement: with jms receiver channel
1 receiver determination
1 interface determination
In receiver jms and sender jms channels i used modules as specified in the document http://help.sap.com/saphelp_nw04/helpdata/EN/45/20d2b4c20a0732e10000000a155369/content.htm
But my interface is not working end to end successfully.
Please confirm below points
1)do i need to have other external application put response message to response queue or will the MQ automatically generates the response message and put into response queue
2)In receiver jms channel is it ok if i will put response queue(Q2) name in the field JMS ReplyTo Queue Name or do i need to put in the form queue://<ReplyToQMgr>/<ReplyToQ>
3). what is the format of data type for asynchronous outbound interface which i used for sender agreement of jms sender channel.
4). Do i need to do any other special settings at MQ settings in MQ server.
Note: i am using PI7.1 and i selected the option JMS-compliant for target client in jms channels.
Thanks,
Madhu
Edited by: Madhusudana Reddy on Nov 4, 2009 9:38 AM

1)do i need to have other external application put response message to response queue or will the MQ automatically generates the response message and put into response queue
The following information is available in SAP note-
Message correlation implies correlating a response message with a request message. With respect to the JMS adapter, this means that you sent have sent a message through a JMS receiver channel to some JMS queue (say queueA) , some external application processes this message and puts the response onto another JMS queue(say queueB) which is then picked up by a JMS sender channel. You need to relate this response message with the original request message.
In the simple case, for all JMS compliant providers this can be done in a straightforward manner:
a) In the JMS receiver channel configuration, set the JMSCorrelationID to the XIMessageID. (or some other XI header which is applicable)
b) Ensure that your external application does not change the value of the JMSCorrelation
c) In the JMS sender channel configuration, set the XIConversationID to the JMSCorrelationID
d) The XIConversationID header of the response XI message now contains the XIMessageID of the request XI message.
For some providers such as Websphere MQ in legacy/native mode this is not so straightforward.
Do i need to do any other special settings at MQ settings in MQ server.
If your using Websphere MQ, refer que#4 in sap note :1086303
Edited by: nagarjuna _s on Nov 4, 2009 11:02 AM

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

Viewing the flat file in JMS Receiver???

How can i see the Flat file generated after content conversion by JMS Receiver channel in a in a ECC->PI->JMS scenario.
I have a JMS Receiver channel connecting to WMS system , how can i see the flat file produced just after the JMS adapter's content conversion. its like
ECC ---> PI----->JMS----> (intermediate client MQ file cannot be viwed here it forwards the file to WMS MQ)------>(MQ)WMS
i need to see the flat file produced just after the JMS channel content conversion..is there some logging option there should be. Please help

Hello,
I don't think there is any standard way to achieve ur req.
But what u can do is, write a custom AM module to either write a file on PI file system (for ur monitoring) or display the text file in ur audit logs.
Send File to Two Different Locations using Adapter Module
Thanks
Amit Srivastava

JMS Receiver Adapter to MQ - additional message property error

Hi,
I'm trying to add addional message properties to a Receiver JMS message for MQ Server queue. Creating the message in the MQ queue only works when I don't try to
add additional message properties. As soon as I try to add additional message properties the XI-Monitor says it's OK but there is no message in the queue.
Our system constellation is a bit odd cause we implemented the JMS/MQ classes of release 5.3 in XI/J2EE.
Our actual used MQ Server is on release 5.1 due to compatibilty reasons of other productive software.
Is there a need to use a MQ server of release 5.3 ?
Has anybody a step by step description for implementing a JMS receiver Adapter for MQ with with additional message property (f.ex. mesType = salesOrder) in the MQ header?
Thanx a lot in advance
Hans

Hi,
You also might want to look at sap note 856346...for this ..
2.6) I am connecting to a JMS provider using JNDI mode. How do I add pass an extra name,value property pair while setting up the JNDI initial context?
Answer: Assuming that your property value is a string, please add the following name, value pair in "JMS Additional properties" table of your channel configuration:
JNDI.InitialContext.property.X=java.lang.String propertyName, java.lang.String propertyValue
where X is a number, the LHS part needs to be put in the name column and the RHS part in the value column of the table respectively.
This note covers frequently asked questions that arise during the installation, configuration or administration of the XI JMS Adapter from the Adapter Framework (AF).
Other terms
JMS - Java Message Service
AF - Adapter Framework
AE - Adapter Engine
SP - Service Pack
Reason and Prerequisites
This note clarifies the frequently asked questions on the XI/PI JMS adapter for released 3.0, 7.0 and 7.1 in the form of an FAQ. References to external information is provided at the end.
Solution
1. Documentation
1.1) Where do I find the JMS adapter documentation?
Answer: In the SAP online help. Go to http://help.sap.com and select SAP Netweaver-> SAP Netweaver 7.1 or SAP NetWeaver 7.0 (2004s) or SAP Netweaver 2004. This opens up SAP Library topic page for that release.
For releases 3.0 and 7.0:
Select SAP Netweaver Library -> SAP Netweaver by Key capability-> Process Integration by Key Capability -> SAP Netweaver Exchange Infrastructure -> Runtime -> Connectivity -> Adapters -> JMS Adapter.
For releases 7.1:
Select SAP Netweaver Process Integration 7.1 -> SAP Netweaver Process Integration Library -> Function Oriented View > Advanced Adapter Engine.
In the topic page click on the JMS Adapter link.
Alternatively, you may simply enter the search string "JMS adapter" and navigate to the documentation page directly from the relevant search results. This is much faster.
1.2) Which JMS providers are supported?
Answer: The JMS Adapter supports JMS 1.02b and 1.1. JMS providers that also claim to be compatible with JMS 1.02b or 1.1 can be accessed using the JMS Adapter.
Furthermore, SAP makes no assertions as to whether a particular JMS provider is tested or can be recommended, because SAP has not set up a certification or testing process.
2. Functions and architecture
2.1) Does the JMS Adapter support JMS topics (publish&subscribe)?
Answer: No. Currently the JMS Adapter works with JMS queues because 100% Exactly Once (In Order) service quality can only be guaranteed with JMS queues. However, this capability might be planned for introduction at a future release. (no planned time estimate)
2.2) I have JMS message properties that are of significant. How do I get this data into XI? How do I get this data out of XI?
Answer:
A feature generically referred to as XI adapter-specific message properties was introduced in the adapter framework. This allowed additional adapter information to be attached to a XI message which can be used the routing, mapping and BPE. The message properties of different adapters are differentiated by namespaces.
If you are on XI 3.0 support pack 18 onwards, the JMS adapter allows you to copy JMS message properties into these XI adapter specific message properties (at the sender JMS channel), and to copy the values of XI adapter specific message properties back into JMS message properties (at the receiver JMS channel).
The JMS adapter currently supports upto 10 JMS message properties to be copied into the XI message properties with the name DCJMSMessageProperty0 to DCJMSMessageProperty9. The configuration details of how to achieve this are explained in the sub-topic pages of the JMS adapter documentation. (See sub topics: "Configuring the Sender JMS adapter", "Configuring the Receiver JMS adapter")
JMS Message properties can have values belonging to types: boolean, byte, short, int, long, float, double, and String (defined in the specification). These are all normalized to strings when converted to the their respective XI message properties at the sender JMS channel.
However, in the receiver JMS channel configuration, you can enter specific JMS message property types, such that these normalized XI message properties may be coerced back into their original types (or any compatible JMS message property type) when translating a XI message into a JMS message.
Transfer of custom JMS Message properties from/to XI adapters-specific message attributes is only supported for JMS compliant messages, i.e. this feature will not work for Websphere MQ in legacy mode.
Deprecated Information on this feature
Between support pack 14 to support pack 18, the JMS adapter allowed the allowed you append only up to two JMS string properties to the XI message in the sender channel, which could then be analyzed in XI routing, mapping and BPE. In the JMS receiver channel, the XI adapter-specific message attributes could be read, and up to two JMS string properties could be set. The names of the (now deprecated) XI message properties were DCJMSStringProperty1 and DCJMSStringProperty2.
Regards
Ravi Raman

Error in JMS communicatin channel while deleivering to WMQ server

How to check whether a node in Adapter engine is having messaging service active?
I am having one of the JMS receiver node having error :
"Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Connector for ConnectionProfile of channel: JMS_Americas_EDI_Receiveron node: 101565650 having object id: #MSGid# encountered error: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException in sending to destination queue:///NASB.UPXI.EDI.INBOUND.AQ, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 0 JMSCorrelationID:3258af50-24e0-11dd-bc98-3c2ac1cacf6e JMSDestination: null JMSReplyTo: null JMSRedelivered: false ReceiverId: ### SenderId:### ISA00 00 124165122352 *08 080 5180935U00401 Another 478 character(s) omitted: javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException"
The second Line for same mssg id provides follwing info:
""JMS error occurred while processing message 'MSGIDe'; error mesage: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException null; error code: MQJMS1016"
Can anyone suggest what can be a fix over this. We have tried restyrting j2ee also but the still persists.
Expect points for sure.
Regards,
Nipun

Hey All,
Following is the solution for the above mentioned JMS receiver channel problem whilst connecting to MQ Series Server.
I assume you are connecting to a MQ series server with version less then 7.xx, or MQ Server 5.xx,
Cause of Problem: The problem appears when you try to send a message through JMS Receiver Adapter channel to a such MQ server and at that particular moment, the server do not accepts the message i.e. the connection with MQ Server drops out; resulting in a Java null pointer error, as the MQ fails to assign the pointer back to the same message, { again until its transferred to MQ.} therefore MQ JMS 2003, MQJMS2007 and MQJMS1016 error appears.
Possible configuration at XI/PI:
1. Add a Advanced additional JMS parameter Connection_Test_Poll = True
2. For XI settings from the drop down of field "Handling of Pending XI messages" select "Bypass Pending Warning and Send Message to JMS(Duplicates possible)" . This will probably cause duplicates at MQ series Server side, make sure you are ready to encounter it there!!
3. If the error still appears, choose In the Error Handling settings, Reconnection if Exception text Starts with provide the error number which the message is currently experiencing. eg. MQJMS1016 or MQJMS2007 or MQJMS2003. Restart the communication channel and restart such message..
After applying the above settings if you still experience errors MQJMS2007, 2003 and MQJMS1016, when connecting and processing messages to MQ server, Then you should try upgrading the MQ Series server! You cannot do much in the XI/PI system else you will create duplicates in the MQ system.
Please Note this error has more to do with the compatibility issue of MQ Series server with PI's JMS adapter.
Do let me know if you have any more queries on this.
Regards,
NIPUN

JMS Type in JMS Receiver

Experts
I need to send JMS Type to the JMS Receiver.
The following UDF was used.
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey keyHeader1 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/JMS","DCJMSType");
String a="341";
conf.put(keyHeader1,a);
return "";
Selected ASMA in the Receiver channel. Anything else needs to be done ?
Thanks and regards,
J Augastine

Abhishek
Modified the UDF.
Also
In the JMS Receiver channel did the following
- Checked the box for 'Use Adapter Specific Message Attributes'
- Checked the box for 'Fail if Adapter Specific Message Attributes missing'
- Checked the box for 'Specify Additional JMS Message Properties'
- Defined property in the table and set the Java type
DCJMSMessageProperty0 String
Under the Module tab,
- Added the module AF_Modules/DynamicConfigurationBean in position 1 with module key HEADER
- Added module configuration as follows:
Module key HEADER
Parameter name key.0
Parameter value write http://sap.com/xi/XI/System/JMS DCJMSMessageProperty0
Module key HEADER
Parameter name value.0
Parameter value JMS DCJMSMessageProperty0
What change needs to be done ???

Sync/Async - JMS receiver comm. channel not processing

I have a Sync/Async scenario (without bpm) in PI 7.11:
RFC -> PI -> JMS
whereby the JMS receiver comm. channel does not fully process the message.
More specifically, the RFC sender comm. channel gets a message in and passes the message to the JMS channel, but that JMS channel within the RWB comm. channel log only shows the entry:
- Message processing started
The odd twist to this is that when we bring the PI server down, then back up again, (or wait a period of time, still trying to determine this period) the FIRST message attempt does successfully get processed, i.e. the first message on that JMS receiver comm. channel RWB log shows as:
- Channel successfully processed the message: 08499236-387c-11e0-b002-000025bab2c2
- Stored the correlation ID 08499236-387c-11e0-b002-000025bab2c2 of the request JMS message: ID:c3e2d840d4d8d4f24040404040404040c754dc12d8b54ec6 correponding to the XI message: 08499236-387c-11e0-b002-000025bab2c2
- Message processing started
(but then because of an issue on the target system, no response comes back, so then we'll additionally get the log entry:
- Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: no message received
Any suggestions appreciated on what I can check here to try and figure this out. Possibly because the first message eventually errors out, it is stopping the other subsequent msgs from getting processed...
When I check the audit logs of a 'success' msg vs. a not-successful msg, the success msg has an entry (and subsequent entries) of:
14.02.2011 12:50:19 Information Transform: transforming the payload ...
14.02.2011 12:50:19 Information Transform: successfully transformed
14.02.2011 12:50:19 Information ROB: entering RequestOnewayBean
14.02.2011 12:50:19 Information ROB: forwarding the request message
14.02.2011 12:50:19 Information ROB: leaving RequestOnewayBean
14.02.2011 12:50:19 Information JMS Message was forwarded to the JMS provider succesfully."
14.02.2011 12:50:19 Information XMB Message as Binary was forwarded to the SAP XI JMS service succesfully.
14.02.2011 12:50:19 Information WRB: entering WaitResponseBean
14.02.2011 12:50:19 Information WRB: retrieving the message for 08499236-387c-11e0-b002-000025bab2c2 ...
wheras the non-success msg shows only:
14.02.2011 12:55:30 Information Transform: transforming the payload ...
14.02.2011 12:55:30 Information Transform: successfully transformed
14.02.2011 12:55:30 Information ROB: entering RequestOnewayBean
14.02.2011 12:55:30 Information ROB: forwarding the request message
14.02.2011 12:55:30 Information ROB: leaving RequestOnewayBean
So, we can see that the message is not "forwarded to the JMS provider..." in the non-success case.
And also the sxi_monitor shows these messages with a status of "Log version".
Keith

Hi Siddhesh - yes that was a while back and am trying to remember the resolution. I have implemented sync/async bridges (as well as async/sync bridges) successfully, so I don't mind checking your settings, particularly I am interested in the settings within the Module tab of the JMS receiver. I can then compare to mine if you'd like. Also if you can let me know what underlying queuing system in that target system (e.g. MQSeries?) that would be great.
Regards,
Keith

JMS Receiver channel : No Correlation ID

Similar Messages

Maybe you are looking for