JMS Adapter Websphere MQ problem

Guys,
I have a problem with websphere MQ using JMS adapter to send messages to XI.
When I send a message with 2 line items to MQ, XI JMS adapter is picking up only the first line item always and second line item just dissapears.
MQ --> XI --> System1
Any suggestions?

Hi,
see the below links
/people/alessandro.guarneri/blog/2006/01/04/jms-sender-adapter-handling-too-short-lines
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
content conversion
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
SAP help-
http://help.sap.com/saphelp_nw2004s/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
Regards
Chilla..

Similar Messages

PI 7.1 JMS Adapter Correlation ID problem

Hi,
I try to get rid of the Correlation ID generated by the JMS Adapter (receiver).
In the adapter configuration, processing tab, I choose Set Correlation ID To: NO VALUE.
But still, in the message's details I can see a Correlation ID like this:
62656263343530362D633765652D346435652D323166392D
Any idea how to force a NO VALUE or a specific value? (hardcoded)
Thanks,
Martin

Hi,
I try to get rid of the Correlation ID generated by the JMS Adapter (receiver).
In the adapter configuration, processing tab, I choose Set Correlation ID To: NO VALUE.
But still, in the message's details I can see a Correlation ID like this:
62656263343530362D633765652D346435652D323166392D
Any idea how to force a NO VALUE or a specific value? (hardcoded)
Thanks,
Martin

JMS Adapter Message Selector Problem...

Hi
I have set the following in the invoke before producing the message and dropping on the queue
<invoke name="Invoke_1" partnerLink="adapt"
portType="ns1:Produce_Message_ptt"
operation="Produce_Message"
inputVariable="Invoke_1_Produce_Message_InputVariable"
bpelx:inputHeaderVariable="Sender"/>
On the receive side I have the message selector configured for the adapter as follows:
<jca:operation
ActivationSpec="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec"
DestinationName="dattjndi"
UseMessageListener="false"
MessageSelector="Sender=AdaptationRequest"PayloadType="TextMessage"
OpaqueSchema="false" >
</jca:operation>
Where AdaptationRequest is the value for the Sender variable which will be used to filter the message. But this does not work. the messages are still not consumed. What could be the problem?
Thanks,
Anil

did you check the message selector section on
http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/Message.html
explains all the operators you can use and the correct syntax. Make a note of the case sensitivity.

Problem in JMS-Adapter with CharacterSet Websphere MQ

Hi,
we have the following scenario:
JMS -> PI -> File
We have a local Websphere MQ Queue Manager and the follwoing configuration in our sender adapter:
Transport-Protocol: WebSphere MQ (non JMS)
Message-Protocol: JMS 1.x
ConnectionFactory: com.ibm.mq.jms.MQQueueConnectionFactory
Java-class Queue: com.ibm.mq.jms.MQQueue
CCSID: 819
Transport: TCP/IP
JMS-conform: WebSphere MQ (non JMS)
In the local queue manager the messages (XML-Messages with header <?xml version="1.0" encoding="ISO-8859-1"?>) have characterSet 819 (ISO-8859-1). That's correct. You can open the files with XMLSpy and it works.
When we receive the messages by our JMS Sender Adapter all the character seems to be in UTF-8 and I don't know why. All the special characters are wrong cause the header of the XML-message shows ISO-8859-1 but all the signs are decoded in UTF-8.
In the other direction (JMS Receiver adapter, File -> PI - JMS) we have the same problem.
We create a ISO-8859-1 message in mapping (and it is really ISO-8859-1) and send it via JMS Receiver Adapter to the local message queue. But there the message arrives in UTF-8 encoding. I don't understand this.
Does anybody know what could be the cause for this?
Does the JMS adapter convert the messages from ISO-8859-1 into UTF-8?
Are there any parameters we have to set?
I hope anybody has an idea what's wrong.
Regards
Thorsten
Edited by: Thorsten Hautz on Oct 12, 2010 5:42 PM

Hi,
thanks a lot for your replies.
our driver settings are correct (as I can see).
I removed value 819 from CCSID, but we have the same effect.
The messages in the local queue manager are TextMessages in XML.
Does anybody know, if we need the standard modules (ConvertJMSMessageToBinary and ConvertBinaryToXMBMessage) in this case?
Is it possible to set the CCSID for the message payload anywhere in the configuration?
The CCSID in the Source tab doesn't have any influence to the encoding of the payload message, only to the header data.
Regards
Thorsten

Problem with Send using JMS Adapter with Websphere MQ

Hi,
We have two scenarios using JMS Adapter with MQ:
1. File->PI->MQ
This works fine and drop the file in MQ correctly.
2. MQ->PI->File
This gives an error reading from the queue: (see highlighted in the log below). It correctly connects to the queue name. But it fails with the message "Could not begin a AF transaction".
Our PI version is 7.0 SP 13
Websphere MQ Version 6.0.
Any idea what could be wrong?
Cluster Node Administration Information Availability Times
Cluster Node Details for Channel CC_JMS_MQ_Sender
Short Log
In the Last 4 Hours Server 0 15_92786
_Sucessfully connected to destination 'queue:///MMPP.PLM.FGH41? CCSID=37&targetClient=1'_
Line 1 / 1
Processing Details for Cluster Node Server 0 15_92786
Type
Time Stamp
Message ID
Explanation
9/2/08 2:27:28 PM 2e6206f0-7925-11dd-bc02-0003bae50b4d Error while processing message '2e6206f0-7925-11dd-bc02-0003bae50b4d'; _detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Could not begin a AF transaction: TxManagerException: Unable to open transaction: com.sap.engine.services.ts.exceptions.BaseSystemException at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:103) ..._
9/2/08 2:27:28 PM 2e6206f0-7925-11dd-bc02-0003bae50b4d XI message ID corresponding to JMS message with ID 'ID:414d512071736431202020202020202047d9462024028b02' will be created as a new GUID with value '2e6206f0-7925-11dd-bc02-0003bae50b4d'
Amith Dharmasiri

Checked the drivers installed in :
/usr/sap/<SID>/DVEBMGS<SYSNO>
/j2ee/cluster/server0/bin/ext/com.sap
.aii.af.jmsproviderlib
They are available and properly added to aii_af_jmsproviderlib.sda.
The drivers are:
CL3Export.jar
CL3Nonexport.jar
com.ibm.mq.jar
com.ibm.mqjms.jar
connector.jar
dhbcore.jar
rmm.jar
These were installed per OSS note 747601.
Any other suggestions, why retrieving from MQ doesn't work?

Problem with JMS Adapter after upgrade to 7.1

Hi All,
After an upgrade the JMS adapter connecting IBM Websphere MQ gives the following error:
Error connecting due to missing class: com.ibm.mq.jms.MQQueueConnectionFactory. Ensure that all resources required are present in the JMS provider library: aii_af_jmsproviderlib.sda
Since we are now on PI 7.1, the directory the JMS adapter should be looking for the libraries should be com.sap.aii.adapter.lib.sda. Has anyone else come across this problem after an upgrade? Should we remove the old aii_af_jmsproviderlib.sda?
Edited by: Luqman on Oct 31, 2008 5:39 PM

does following JAR files in place in aii_af_jmsproviderlib.sda.
●      com.ibm.mq.jar
●      com.ibm.mqbind.jar
●      com.ibm.mqjms.jar
●      connector.jar (use the JAR file from the J2EE client directory)
can u check n confirm.
i hopw u have followed the proper deployement process.
chirag

Error in JMS Adapter while communicating with WebSphere MQ 7.5

Guys,
I am trying to integrate JMS Adapter with WebSphere MQ.
JMS Adapter : 14.0.2.0
WebSphere MQ : 7.5
I am getting error like below. Please help me out. Thanks
17/04/14 16:25:49 java.lang.NoSuchMethodError: com.ibm.msg.client.jms.JmsSession.createQueue(Ljava/lang/String;)Ljavax/jms/Queue;
at com.ibm.mq.jms.MQSession.createQueue(MQSession.java:708)
at com.acta.adapter.jms.MQConfigHandler.getQueue(MQConfigHandler.java:74)
at com.acta.adapter.jms.JMSAdapter.getQueue(JMSAdapter.java:547)
at com.acta.adapter.jms.JMSGetOperation.start(JMSGetOperation.java:398)
at com.acta.adapter.sdk.OperationWrapper.runOperation(OperationWrapper.java:171)
at com.acta.adapter.sdk.OperationWrapper.run(OperationWrapper.java:94)
at java.lang.Thread.run(Thread.java:662)
I have added following jars in class path of the adapter.

Problem solved after removing j2ee.jar file from classpath !

Anyone successfully deployed BPEL + JMS Adapter (for MQ) to WebSphere?

Anyone successfully deployed BPEL Process Manager + JMS Adapter (for MQ) to WebSphere (i.e not OAS/OC4J)?
If you have - I would love to see a valid example of the ra.xml and oc4j-ra.xml files in your jca/JmsAdapter.rar file - to see how you configured access for the JMS Adapter to your remote MQ queues.
Thank you
Dennis

Hi Garima,
Please check the following:
1. Add dhbcore.jar also to aii_af_jmsproviderlib.sda and deploy it.
2. Check the existence of your JMS drivers.
3. Check the following link and Install the drivers as the way it is mentioned in the guide 'How To Install And Configure External Drivers For JDBC & JMS'
https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
There are 4 files which needs to be added. http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/frameset.htm
Any of the above solutions should help you solve the problem.
Regards,
Abhy

XI JMS Adapter encoding and codepage (MDMP) problem

Hi
I have a scenario where i convert an IDoc into a target structure and post it onto a Websphere MQ queue using JMS adapter. The SAP system which sends the idoc is a non/unicode system and i can receive data which can either danish, polish etc. Within XI the mapping works fine and the data is transferred to the MQ series queue. But when the third party system tries to get the message from the queue it says it downloads the message and is unable to convert the downloaded message due to invalid content (special danish, polish characters). Also the CCSID and encoding expected is 1252 and 546 respectively, but whenever i send message to the queue the CCSID is 1252 but encoding is 273.
Any idea as to why the above is happening, and how can it be corrected.
Also if anybody had faced any issues with respect to code page problems and resolved it with JMS as either sender or receiver, please share the same with me as well.
I am repeating that my SAP system is non-unicode (MDMP) system.
thanks
Sameer
Message was edited by:
Sameer Shadab

Sameer,
I guess u can ask the third party to set CodedCharSet in GetMessageOptions. Actually my MQ knowledge is around 4 yrs old but I remember we had similar problem when we were pushing messages on remote queue of MQ on AS-400. I hope they resolved by setting this value.
Regards
Rajeev

How to install Oracle AS JMS Adapter on Websphere (or any J2EE server)

Hi,
We have a requirement in which the client wants to connect to the OC4J JMS running in SOA Suite (Oracle Application Server 10.1.3.4).
They are using Websphere. We are exploring ways by which they can connect from Websphere application to Oracle AS OC4J JMS.
One option is - deploy the Oracle AS JMS adapter in Websphere and then use it to connect to the OC4J JMS.
Please let us know if this is the right approach. Also, if so, kindly point to the documentation regarding how to install the JMS adapter on 3rd party J2EE servers such as websphere.
Rgds,
Amit

While searching the knowledge base I found the following note, which seems to suggest that Oracle Adapters are not deployble on other J2EE application servers:
Support For Jca Adapter In Other Application Servers Like Jboss [ID 1114738.1]
==============================================
From the statements in documentation it may be implied that jca adapter should be deployable on any application server that is compliant with j2ee/jca. Please note that this cannot be implied at this time and jca adapter cannot be deployed on other application servers than OAS in BRM 731 due to some technical constraints. So currently we can support only OAS and not JBoss or another application server , in BRM 731. The documentation will be updated accordingly to reflect this.

Problem with special character like u00E5,u00E4 u00F6 in Sender JMS Adapter

Hi,
Problem:
Sender JMS Adapter has transformation error when the file includes western european characters such as å,ä ö. And because of this reason the data is not picked up by adapter.
The scenrio is JMS --- > XI ---> Proxy.
If the file does not include the western European characters then it is working fine, but when the file include the western european characters such as å, ä, ö so got the error.
Our Efforts:
We have tried ISO8859-1 in JMS Module Tab as shown below.
1. Transfer.ContentType text/xml;charset=ISO-8859-1
AND with this also
2. Transfer.ContentType application/coctet-stream;charset=ISO-8859-1
None of them working.
Error In CC:
In Sender CC monitoring we are getting the below error.
Error while processing message 'aa157082-b064-4421-0fc3-c286d2732093'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Error converting Message: sun.io.MalformedInputException: TransformException: Error converting Message: 'sun.io.MalformedInputException' at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java(Compiled Code)) ...
Any suggestion in this regard will be a great help.
Regards,
Sarvesh

> I think you have to figure out first, which codepage you really have, not just try. Maybe you ask someone or you check with a hex editor.
Hi Stefan,
Finally we solved the problem.
As you said above to figure the the codepage, we asked to our MQ team for the same and found that they are using ISO-8859-1. In XI we were also trying with multiple conbinations (ISO-8859-1, UTF-8 and many more), but didn't get any success.
Finally MQ team changed their encoding to UTF-8 and in XI we used ISO-8859-1 and we get the success in picking the data with spl char. Even though in XI the spl char comes in destorted order but at the receiver end they are in proper shape.
Thanks a lot for your help.
Regards,
Sarvesh

Problem in configuring JMS adapter

Hello,
My purpose is to send xml data from MQSeries to BW using XI. MQSereies is installed in XI server. For thah I am trying to configure JMS adpter for MQSeries in XI. I have successfully deployed the necessary external drivers using SDM. I have configured the sender channel with the following parameters.
Adapter type: JMS
Transport Protocol :WEBsphereMQ(non-JMS)
Message protocol :JMS1.x
Queue connection factory java class:com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class: com.ibm.mq.jms.MQQueue
IP address: IP address of XI system.
Port: 1414
Queue manager name : MQ-manager-name_XI-system-name
Channel Name : reciever-channel-name_XI-system-name
JMS queue: postcard
Charecter set ID:
Transport/networkprotocol: TCP/IP
JMS-Compliant : WebsphereMQ(non-JMS)
But when I check it in adapter monitor JMS is shown as red.
When I go to Visual Administrator
"cluster->server->services->monitoring->runtime->monitor tree->services->Connector Service" is white instead of green.
Can any one tell what could be the problem.
Regards,
Amith

Hi Vijaya,
In VA there is only option to stop or start JMS XI adapter.
I dont know where to activate JMS adapter in VA. It is already started in VA.
Regards,
Amith

JMS adapter fails to open IBM WebSphere MQ Manager V6 Remote Queue

Hello,
We are trying to connect to a Remote Queue with the SAP PI 7.0 SP9 JMS adapter to IBM WebSphere MQ V6 on Linux SLES9 x86_64.
We did deployed the JMS-adapter with the V6 native libaries on SAP PI.
In the Communication Channel we use the Adapter Type = JMS, Sender, Transport Protocol = WebSphereMQ(non-JMS).
The MQ Queue Manager is on the same server as SAP PI so we use localhost, Server Port, Queue Manager Name, Channel Name and JMS Queue Name
The <sid>adm user is a member of the mqm group.
When I check the RWB I see this fault message:
Error during channel initialization; exception trace: javax.jms.JMSException: <b>MQJMS2008: failed to open MQ Queue</b> at ...
and also
com.ibm.mq.MQException: <b>MQJE001: Completion Code 2, Reason 2045</b>
When we lookup the reason 2045 we get this explaination on MQ:
MQRC_OPTION_NOT_VALID_FOR_TYPE
We also have a type = Receiver Communication Channel on the same MQ Queue Manager that one is working fine.
Please advise!
Best regards,
Mike Laanen

Mike,
check whether the Queues are created and activated if it done. then check whether you have authorization for those queues.
Regards
Sreeram.G.Reddy

JMS Adapter: Sending data with WebSphere MQ Client to XI

Hi,
I want to send data from the WebSphere MQ Client to the XI. Is this possible and what do I have to do except configuring the JMS queues in Visual admin?
Thanks in advance
Dominic

hi
xi jms adapter will read/write data frm queue.
but u want to access the jms queues in XI WAS frm ur MQ client
..will hv to access it directly frm ur client
chk this
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/604e2b64-e689-2910-64b3-ffd650f83756
rgds
arun

Problem testing JMS adapter

I have create and configure JMS resource but still i am getting this exception
Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'sendMessage' failed due to: ERRJMS_ERR_CR_QUEUE_PROD. ERRJMS_ERR_CR_QUEUE_PROD. Unable to create Queue producer due to JMSException. Please examine the log file to determine the problem. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
Fault
BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'sendMessage' failed due to: ERRJMS_ERR_CR_QUEUE_PROD. ERRJMS_ERR_CR_QUEUE_PROD. Unable to create Queue producer due to JMSException. Please examine the log file to determine the problem. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
Kindly help

This is how I configured
Configure the JMS Queue Resource (Jndi name=>>> jms/demoMsgQueue)
Configured the JMS Connection Factory Resource
configured the demoCF JMS connection factory
Created a JMS Adapter Connection Pool
Associate the Connection Pool with the Connection Factory
Redeployed the JMS Adapter with the New Resources
How I can do bouning app server?

JMS Adapter Websphere MQ problem

Similar Messages

Maybe you are looking for