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?

Similar Messages

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

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 testing EMail adapter

Hi All, I have deployed EMail adapter succesfully. I am trying to test that. Could
anybody tell How to test this ? what i want to know what is the XML input to test
the email adapter application. ? Thanks in advance.

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?

Esb parallel processing problems with jms adapter and bpel

Hi,
I have esb project which dequeues from a jms adapter and then the esb router calls a bpel process. This bpel process takes about 10 seconds. The first step this bpel does is to return true ( to the client) to the esb router so the ESB thinks he is ready. This does not work.
Now if I use in the esb router asyn routing rule to the bpel ws then the esb dequeus all the messages from the queue. All the esb entries are green. But the esb starts one for one the bpel process and then updates the esb entry with a new start time ( very strange) .
If I use a sync routing rule then it dequeues and call the bpel process one for one.
How I can parallel proces the jms messages ,because I have 2 quad cores cpu's . Async routing rules looks like the solution.
How can the esb detects the bpel is still running even with the first action in bpel is to return true. I expected when the esb retrieves true from the bpel ws it ends the current esb entry and goes on with the next. So the total esb time takes a few seconds and not so long as the last the bpel proces finishes.
And why is he updating the starting time.
Thanks Edwin
Message was edited by:
biemond

I have esb project which dequeues from a jms adapter
and then the esb router calls a bpel process. This
bpel process takes about 10 seconds. The first step
this bpel does is to return true ( to the client) to
the esb router so the ESB thinks he is ready. This
does not work. I am not sure if it can ever work, if you reply and then still proceed with your BPEL process.
Here is something I would like to suggest:
Can you try ESB -- (sync) --> BPEL, where BPEL process itself is Async. In that case, esb will consume all the messages very fast and BPEL will get that message and put in Delivery Queue and reply back to ESB. Now BPEL will process them simultaniously based Receiver/Worker threads defined in your env.
HTH,
Chintan

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

Testing JMS

Is there any way to test JMS adapter..
What do I have to install & configure.??

Hi,
You can test the JMS adapter by using Websphere MQ (WMQ) or Sonic MQ. To test the scenario you need to install jar files into XI box provided by these vendors. If you donu2019t have these MQ series softwareu2019s available at your end then use Transport Protocol as u201CAccess JMS with JNDIu201D. In this case you need not install drivers / jar files but you need to create a queue in Visual Admin or you can use existing queue also. Once the queue is created, configure the JMS adapter and monitor in RWB and SXMB_MONI. You can use file to JMS and JMS to file scenario for testing purpose.
Reward points if it is helpful.
Regards,
Sridhar.

Jms adapter configuration and testing

Hi,
Please inform the JMS adapter configuration and testing.
Thanks
Naidu

Hi,
tried to reach JMS adapter but was not sure about what to inform it with
Ok, just being silly there... About your problem:
Overview - not complete and a little dated but notetheless good starting point
Exploring JMS and SAP-XI JMS Adaper
JMS FAQ Note - valuable official statements for various questions. Many linked notes which may also be of interrest
http://service.sap.com/sap/support/notes/856346
Driver deployment note
http://service.sap.com/sap/support/notes/1138877
Some other valuable links provided by Chirag Gohil
Re: jms senarios
HTH for starters
Cheers
Jens

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

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 Testing

Hi Team
I am using the JMS adapter as a sender and the idoc as receiver. i want to test the End to End scenario. i am using the Transport Protocol as " Access JMS Provider with JNDI".
I have been provide by a program which helps to write the xml message into the queue.
My doubt is how to run this program and where to run this java program??
this is the first time i am developing scenario by using the JMS adapter
Awaiting for your replies
thanx

Hi,
Are you trying to test the scenario JMS -> PI ?
If you are trying to add a message to the queue, you can use MQ client software to do this - this allows you to connect to a remote queue manager and add messages to any queue on the queue manager.
Cheers
Colin.

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..

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

JMS Adapter test

Hi to all,
I have a JMS -> XI -> RFC scenario. Actually, I haven't my sender Business System, thus I want to use something to test my JMS Adapter. There is any tool that I can use to test my JMS adapter/channel or to simulate a MQSeries sender?
Thanks to all!

You can put a test message directly in your communication channel:
RWB -> Component Monitoring -> Integration Engine -> Test Message
or
You can create your own queue on the j2ee server:
See blogs of William Lee - How to use SAP's WebAS J2EE's JMS Queue in Exchange Infrastructure
or
If your queue is in place, you can use a tool like rfhutil, but then you also need a mq client on your workstation. (all free so why not)

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 testing JMS adapter

Similar Messages

Maybe you are looking for