Error initializing Sender JMS Adapter

Hi,
Has anyone integrated MQSeries 5.3 with XI 3.0? I have placed all the necessary jar files under tech_adapter and in class path.My adapter status is red and the log says that
    ". ...andler moduleHandler, Parameter para) [Thread[Thread-11,5,main]] Error: java.lang.NoSuchMethodException
            at java.lang.Class.getConstructor0(Native Method)
            at java.lang.Class.getConstructor(Unknown Source)
            at com.sap.aii.messaging.adapter.ModuleJMS2Transport.init(ModuleJMS2Transport.java:351)
            at com.sap.aii.messaging.adapter.ModuleHandlerImpl.run(ModuleHandlerImpl.java:576)
            at java.lang.Thread.run(Unknown Source)"
please let me know if i am missing something.
Regards
Sathya

Hi Amol,
       Our SLD Accessor service is working properly.i have deployed all the necessary jar files.I am not very confident in my class path settings.So i am sending my class path,
       D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\classes12.zip;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\com.ibm.mqjms.jar;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\com.ibm.mq.jar;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\connector.jar;D:\usr\sap\MTX\DVEBMGS00\j2ee\cluster\server0\bin\ext\com.sap.aii.af.jmsproviderlib\com.ibm.mqbind.jar;D:\usr\sap\BWXI\SYS\global\tech_adapter\server.jar;com.sap.aii.messaging.adapter.AdapterImpl;D:\usr\sap\BWXI\SYS\global\tech_adapter\ejb.jar;
please look into that.
I am sending the log trace for Adapter Configuration so that you can make something out of it.
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: >>>>>
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Starting adapter engine version 3.0.0318 ($Id: //tc/aii/30_REL/src/_messaging/java/com/sap/aii/messaging/adapter/AdapterImpl.java#7 $, $DateTime: 2004/08/03 11:19:35 $ ) ...
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: sync.time: 200411110440
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: jdk.version: 1.3.1
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: make.rel: 30_REL
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: build.date: 2004-11-11 04:58
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: latest.change: 300224
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: make.server: PWDFM060
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: >>>>>
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: main adapter properties file found: 'D:\usr\sap\BWXI\SYS\global\tech_adapter\adapter_base.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: main adapter properties file found: 'D:\usr\sap\BWXI\SYS\global\tech_adapter\adapter.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: initializing and starting with given Parameters ...
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: - Token File token.keystoragenot found
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Reading property file 'adapter_base.properties' for adapter modules configuration...
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: adapterID set to Adapter1
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   AdapterMonitor      - expects property file 'BaseConfiguration/AdapterMonitor.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module AdapterMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module AdapterMonitor
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-0,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleAdapterMonitor' created, version 2.0.1010
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module AdapterMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module AdapterMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   InfoLogger      - expects property file 'BaseConfiguration/InfoLogger.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module InfoLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module InfoLogger
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-1,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleInfoLogger' created, version 2.0.0918
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module InfoLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module InfoLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   IDLogger      - expects property file 'BaseConfiguration/IDLogger.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module IDLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module IDLogger
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-2,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleIDLogger' created, version 1.0.0523
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModuleIDLogger [Thread[Thread-2,5,main]] Info: Initializing new IDLogger object(version 1.0.0523), root directory is 'Data'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module IDLogger
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModuleIDLogger [Thread[Thread-2,5,main]] Info: IDLogger started
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module IDLogger
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   RtcMonitor      - expects property file 'BaseConfiguration/RtcMonitor.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module RtcMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module RtcMonitor
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-3,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleRtcMonitor' created, version 1.0.0819
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module RtcMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module RtcMonitor
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   PersistLayer      - expects property file 'BaseConfiguration/PersistLayer.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module PersistLayer
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module PersistLayer
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-4,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModulePersistLayer' created, version 2.0.0929
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module PersistLayer
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module PersistLayer
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   PWtokens      - expects property file 'BaseConfiguration/PWtokens.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module PWtokens
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module PWtokens
Apr 26, 2006 10:08:22... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-5,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModulePWtokens' created, version 1.0.0724
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: Initializing new PWtoken object(version 1.0.0724), root directory is '.'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module PWtokens
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: Getting parameters: default value '<!%' set for parameter 'PWD.beginSeparator'
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: Getting parameters: default value '%!>' set for parameter 'PWD.endSeparator'
Apr 26, 2006 10:08:22... ....aii.messaging.adapter.ModulePWtokens [Thread[Thread-5,5,main]] Info: SLDaccessor started
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module PWtokens
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   GUIBrowserEngine      - expects property file 'BaseConfiguration/GUIBrowserEngine.properties'
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module GUIBrowserEngine
Apr 26, 2006 10:08:22... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module GUIBrowserEngine
Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-6,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleGUIBrowserEngine' created, version 3.0.1930
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module GUIBrowserEngine
Apr 26, 2006 10:08:23... ...saging.adapter.ModuleGUIBrowserEngine [Thread[Thread-6,5,main]] Info: GUIBrowserEngine started
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module GUIBrowserEngine
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   HttpServer      - expects property file 'BaseConfiguration/HttpServer.properties'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module HttpServer
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module HttpServer
Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-7,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleHttpServer' created, version 1.0.0808
Apr 26, 2006 10:08:23... ...ii.messaging.adapter.ModuleHttpServer [Thread[Thread-7,5,main]] Info: Initializing new HttpServer object(version 1.0.0808), root directory is '.\Data'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module HttpServer
Apr 26, 2006 10:08:23... ...ii.messaging.adapter.ModuleHttpServer [Thread[Thread-7,5,main]] Info: Http server started
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module HttpServer
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   SLDaccessor      - expects property file 'BaseConfiguration/SLDaccessor.properties'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module SLDaccessor
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module SLDaccessor
Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-9,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleSLDaccessor' created, version 2.0.1010
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module SLDaccessor
Apr 26, 2006 10:08:23... ...aii.messaging.adapter.ModuleSLDaccess [Thread[Thread-9,5,main]] Info: Initializing new SLDaccessor object(version 2.0.1010), root directory is '.\Data'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Started module SLDaccessor
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   jms_sender2is      - no property file specified - try default 'Configuration/jms_sender2is.properties
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   jms_sender2is      - expects property file 'Configuration/jms_sender2is.properties'
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info: Constructed handler for Module jms_sender2is
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Created module jms_sender2is
Apr 26, 2006 10:08:23... ...i.messaging.adapter.ModuleHandlerImpl [Thread[Thread-11,5,main]] Info: Module 'com.sap.aii.messaging.adapter.ModuleJMS2Transport' created, version 2.0.1626
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Info:   Initialized module jms_sender2is
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Fatal: Adapter engine startup procedure finished: 9 modules started successfully
Apr 26, 2006 10:08:23... ...sap.aii.messaging.adapter.AdapterImpl [Thread[main,5,main]] Fatal: Adapter engine running...
Apr 26, 2006 10:08:23... com.sap.aii.messaging.adapter.IDLogImpl [Thread[Thread-11,5,main]] Info: Attached persistent hashtable to file 'D:\usr\sap\BWXI\SYS\global\tech_adapter\Data\jms_sender2is_ID.dat'
Apr 26, 2006 10:08:23... ....aii.messaging.adapter.ModuleIDLogger [Thread[Thread-11,5,main]] Info: Created new ID log file 'jms_sender2is_ID.dat' in folder 'Data' for module 'jms_sender2is'
Apr 26, 2006 10:08:23... ...p.aii.messaging.adapter.XMBParameters [Thread[Thread-11,5,main]] Info: Getting parameters: default value '' set for parameter 'XI.SenderParty'
Apr 26, 2006 10:08:23... ...p.aii.messaging.adapter.XMBParameters [Thread[Thread-11,5,main]] Info: Getting parameters: default value '' set for parameter 'XI.ReceiverParty'
Apr 26, 2006 10:08:23... ...andler moduleHandler, Parameter para) [Thread[Thread-11,5,main]] Error: java.lang.NoSuchMethodException
     at java.lang.Class.getConstructor0(Native Method)
     at java.lang.Class.getConstructor(Unknown Source)
     at com.sap.aii.messaging.adapter.ModuleJMS2Transport.init(ModuleJMS2Transport.java:351)
     at com.sap.aii.messaging.adapter.ModuleHandlerImpl.run(ModuleHandlerImpl.java:576)
     at java.lang.Thread.run(Unknown Source)
Apr 26, 2006 10:08:28... ...duleSLDaccess.createAdapterEntities() [Thread[Thread-9,5,main]] Info: Adapter Entities for AdapterEngine_bwxi_8200 created successfully
Apr 26, 2006 10:08:29... ...duleSLDaccess.createAdapterServices() [Thread[Thread-9,5,main]] Info: Adapter Services for AdapterEngine_bwxi_8200 created successfully
Apr 26, 2006 10:08:29... ...aii.messaging.adapter.ModuleSLDaccess [Thread[Thread-9,5,main]] Info: SLDaccessor started
Regards
Sathya

Similar Messages

Sender JMS Adapter error: The JMS provider gave the error message as Not permitted, and the error code is null

I am trying to connect tibcoems with PI using a Sender jms adapter.After successfully installing the drivers , the sender adapter goes into error.
"The JMS Provider gave the error message as Not permitted, and the error code is null"
The Transport protocol is 'Access JMS Provider with JNDI' and i have been given the required parameters from the tibco guys.
Your input are highly appreciated.
Shyam

Hi AQmit,
Thanks for the reply.
Please find the screenshots of what i am trying to do.
Also, Can u direct me how to check the right logs?

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

Change of Encoding in Sender JMS Adapter

Hi,
My scenario is like that:-
FTP->MQ Queue->JMS Queue->XI->R/3
From JMS Queue IDOC xml is coming in UTF-8 encoding to XI. In that IDOC xml certain special characters are there, say, some Latin or European character. But for the scenario XI->R/3, data are not getting posted to R/3. In XI side, it is not giving any error, but it is giving a flag (in QRFC Monitor) which is Error between two Character Sets.
I am unable to rectify this error. One solution I have guessed that is, it will be possible to resolve this issue if I can change the encoding in XI to ISO-8859-1. But I dont know how to change the encoding in Sender JMS Adapter in XI. Could you please help me to resolve this issue?
BR
Soumya B

Hi,
Check following:
1. In SXMB_MONI, what is the XML structure generated for inbound and outbound message. Check the encoding used in both. This could be checked by looking at the first line of XML generated. For UTF encoding, usually, the first line should look as follows:
<?xml version="1.0" encoding="UTF-8" ?>
2. If the encoding for both is different, try to figure out which encoding is used for Message Type in XI. For matching the encodings, you could change the XSD used for creating message type in XI. This way, the character encoding could be changed. And this solution should suffice if the problem has occured between XI to R3 scenario.
Also, for learning more about character encodings, you could visit following link:
http://www.cs.tut.fi/~jkorpela/chars.html
Hope it helps.
Bhavish.
Reward points if comments found useful:-)

Sender JMS Adapter - NOT Working

Hello Everybody - We are on SP13, also installed JMS Driver files on the system. We are running, Central Adapter Engine.
We configured the Sender JMS Adapter for WBI MQ->XI->SAP scenario. We need to JMS Adapter to be configured to connect to WBI from XI. Everything looks great in configuration but in the Adpater Monitoring, JMS Adapter is with Error Status and Message says "Sender channel. Details: (No detail information set.)".
Does anybody has any idea about this error ?
I checked SAP Help link as well on this. Based on this link http://help.sap.com/saphelp_nw04/helpdata/en/ca/e7673c86d19b35e10000000a11402f/frameset.htm. Do we need to configure this JMS Adapter somewhere on teh server as well ? If yes, then where ? Pls respond if you have any clue about it.
Thanks in anticipation...

Hello Stefan - Thanks for response.
Here are the Parameters.......
Adapter Type: JMS
Sender Type Clicked
Transport protocol:WebSphereMQ (non-JMS)
Message protocol:JMS 1.x
Adapter Engine:Integration Server
Queue ConnectionFactory Java Class:com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class:com.ibm.mq.jms.MQQueue
IP Address or Server Name:10.9.48.154
Server Port:1414
Queue Manager Name:WBIDEV
Channel Name:WBI.XI.SVRCONN
JMS Queue:XI_REQUEST
Transport/Network Protocol:TCP/IP
JMS-Compliant:JMS-Compliant
Transactional JMS Session:Check box Set
JMS Queue User:XIUSER
JMS Queue Password:********
Set XI message ID(MessageID) to:GUID(recommended value)
Set XI cenversation ID(conversationID) to:No value
Mapping of Message:Message Payload=JMS Payload
Quality of Service:Exactly Once
Time Period for duplicate check for EO(IO)(secs):86400
Wait After Message Error(msecs):1000
Wait before Reconnect(msecs):1000
Status:Active
The Error Message I see in the Adapter Monitor is "Sender Channel. Details: (No detail information set.)
Pls advice If I am missing anything ?
Thanks....
Amrish.

Sender JMS Adapter does not work

Hi all,
We have created a sender JMS adapter with transport protocol "Access JMS Provider with JNDI". The adapter connects to destination successfully, so the connection parameters are right. However, we do not receive any message when the sender sends them.
What parameters should we set to be able to retrieve messages from the queue?
Thanks in advance,
Samantha.

Hi,
Into Communication Channel Monitoring, we get the following errors:
1. Error occurred while processing message: null. Detailed error (if any): java.lang.NullPointerException: at java.text.MessageFormat.applyPattern(MessageFormat.java:414) ...
2. Added dynamic header: DCJMSMessageSelector to XI message null which corresponds to JMS message selector: mentioned in the channel configuration
3. XI message ID corresponding to the JMS message with ID: ID:1109F6E3DF541328-00000000053E as stripped of the "ID:" marker and now has the value: null
4. XI message ID corresponding to JMS message with ID: ID:1109F6E3DF541328-00000000053E will be created with the value of JMSCorrelationID which has the value: null
Where is the problem?
Thanks again,
Samantha.

Sender JMS Adapter

Hi,
I am using a sender JMS adapter. Transport Protocol i have given as "Access JMS Provider with JNDI".
In the field "JNDI Server Address" i have to give the server:port.
Here i am not sure which port to give.
Is it the P4 port i.e. 5XX04 or the J2EE port on which the WAS listens i.e. 5XX00.
Please advise.
Regards
Sidharth

Hello Stefan - Thanks for response.
Here are the Parameters.......
Adapter Type: JMS
Sender Type Clicked
Transport protocol:WebSphereMQ (non-JMS)
Message protocol:JMS 1.x
Adapter Engine:Integration Server
Queue ConnectionFactory Java Class:com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class:com.ibm.mq.jms.MQQueue
IP Address or Server Name:10.9.48.154
Server Port:1414
Queue Manager Name:WBIDEV
Channel Name:WBI.XI.SVRCONN
JMS Queue:XI_REQUEST
Transport/Network Protocol:TCP/IP
JMS-Compliant:JMS-Compliant
Transactional JMS Session:Check box Set
JMS Queue User:XIUSER
JMS Queue Password:********
Set XI message ID(MessageID) to:GUID(recommended value)
Set XI cenversation ID(conversationID) to:No value
Mapping of Message:Message Payload=JMS Payload
Quality of Service:Exactly Once
Time Period for duplicate check for EO(IO)(secs):86400
Wait After Message Error(msecs):1000
Wait before Reconnect(msecs):1000
Status:Active
The Error Message I see in the Adapter Monitor is "Sender Channel. Details: (No detail information set.)
Pls advice If I am missing anything ?
Thanks....
Amrish.

MessageTransformBean in sender JMS Adapter flat file to xml conversion

Hi All,
The scenario is MQ (Flat File ) --->PI -
>Idoc
The flat file structure is
112233
AABBCC
The expected XML Structure after using MessageTransformBean in the sender JMS adapter is
<Record>
<Row>
<f1>11</f1>
<f2>22</f2>
<f3>33</f3>
</Row>
<Row>
<f1>AA</f1>
<f2>BB</f2>
<f3>CC</f3>
</Row>
</Record>
But I am getting 2 SEPARATE xml messages each with only one Row in it like the following
1st XML:
<Record>
<Row>
<f1>11</f1>
<f2>22</f2>
<f3>33</f3>
</Row>
</Record>
2nd XML:
<Record>
<Row>
<f1>AA</f1>
<f2>BB</f2>
<f3>CC</f3>
</Row>
</Record>
I would like to have one xml message with all rows in it.It seems the MessageTransformBean is not recognizing the end of line in the flat file.Do i need to use endSeparator explicitly.
I followed the "How to use Content Conversion in JMS Adapter " and configured the adapter,still no luck..
Any Help greatly Appreciated
Thanks,
C

Hi Chirag,
The parameter name sequence changes alphabetically by itself when I save and activate it eventhough I enter as it is in the document.How to stop changing this sequence or put it the order as required in the Module Processor.
Currently my sequence is
Transform.Class
Transform.ContentType
xml.conversionType
xml.documentName
xml.documentNamespace
xml.fieldFixedLengths
xml.fieldNames
xml.processFieldNames
xml.structureTitle
Let me know how to change the sequence ,if that is the issue.
Thanks,
C

How to hanlde breaked large messages in sender JMS adapter

Hi,
I have been asked like 'how can we handle breaked large messages in sender JMS adapter?'and lets say I am getting some messages as it is and some are breaked into small segements for the mesaages that are large....
do we need to use module,if so is there any standard module that we can use to hanlde this type of scenarios?
thank you in advance.
babu

http://biemond.blogspot.com/2009/10/jms-request-reply-interaction-pattern.html
if you check the blog of edwin, see his comments at the bottom
there he gives a suggestion how to add the selector properties to filter on
and this one is maybe helpfull
http://blogs.oracle.com/adapters/2010/05/configuring_request-reply_in_jmsadapter.html

Sender JMS adapter configuration for IBM MQSeries

Dear All,
i am doing a IBM MQSeries 5.2.x Message ->sender JMS adapter -> XI server -> receiver RFC adapter -> R/3.
i have deployed the JMS adapter with the required jar files of IBM MQSeries 5.2.x in XI server.
in Sender JMS adapter configuration for IBM MQSeries 5.2.x, i have put following data:
1. Transport Protocol: Websphere MQ - is it okay?
in JMS provider settings:
2. in channel name - what should be there?
3. Transport Network protocol should be TCP/IP or WebsphereMQ - how to decide this thing.
4. JMS Complaint - whether WebsphereMQ or JMS API.
in JMS Settings:
5. JMS Queue user - is this IBM MQSeries 5.2.x Queue User or someother user?
6. JMS Message Selector - what data to take here.
So if anybody has connected IBM MQSeries 5.2.x to XI via JMS adapter, please answer my above queries.
Regards,
Rajeev Gupta

Hi Swaroop,
you can send me those documents at my gmail-id : [email protected]
Hi All,
one more question - to connect XI server to IBM MQSeries via JMS adapter in ID, do we need to have a MQSeries Client installed on XI server - or - just by configuring JMS adapter, we can send messages from IBM MQSeries to XI server without any MQSeries client on XI server?
Why Channel name is required in JMS configuration data?
Thanks,
Rajeev Gupta

How to ignore Recordset name in XML(Sender JMS Adapter)?

Hi All.
I am using Sender JMS Adapter along with content conversion.
I have put in Parameter:
Plain2XMLService xml.ignoreRecordsetName true
still the Inbound payload in SXI_MONITOR has Node Recordset, which should not be the case.
Please advice, does this ignoreRecordsetName works in JMS adapter, if Yes does it works same way as in File Adapter content conversion?
Thanks in Advance

>
Gowtham Peddi wrote:
> Hi All.
>
> I am using Sender JMS Adapter along with content conversion.
>
> I have put in Parameter:
> Plain2XMLService xml.ignoreRecordsetName true
>
> still the Inbound payload in SXI_MONITOR has Node Recordset, which should not be the case.
>
> Please advice, does this ignoreRecordsetName works in JMS adapter, if Yes does it works same way as in File Adapter content conversion?
>
> Thanks in Advance
can you try
ignoreRecordsetName true instead of xml.ignoreRecordsetName
also try to not give any value for the xml.recordsetName parameter.
I actually doubt if we can ignore the record set name using the module.

Sender JMS Adapter: Problem in Recordst

Hi All.
I am using Sender JMS Adapter along with content conversion.
I have put in Parameter:
Plain2XMLService xml.ignoreRecordsetName true
still the Inbound payload in SXI_MONITOR has Node Recordset, which should not be the case.
Please advice, does this ignoreRecordsetName works in JMS adapter, if Yes does it works same way as in File Adapter content conversion?
Thanks in Advance

Hi Pravesh,
Check this file on Sender JMS adapter if it helps you in anyway;
http://help.sap.com/saphelp_nw04s/helpdata/en/ca/e7673c86d19b35e10000000a11402f/frameset.htm
Also check this:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50061bd9-e56e-2910-3495-c5faa652b710
Regards,
Subhasha Ranjan

Sender JMS Adapter with EOIO Quality of Service

Hi,
I have a sender JMS adapter with a quality of service as EOIO. In the SAP help it says that I need to specify the "Processing J2EE Cluster Server (Cluster ID)". Just wondering how I get this value? Does anyone have an example?
Thanks,
Krishneel

Hi,
Please go through the bleow Wiki:
http://wiki.sdn.sap.com/wiki/display/XI/FAQ+J2EEJMS+Adapter
http://help.sap.com/saphelp_nwpi71/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
Thanks,
satya

Duplicate MessageID error in sender JMS

Hi,
could anyone provide some inputs in getting through the following error in sender JMS:
A duplicate JMS message was received. It was was received earlier and processed with the XI message ID 3fc663bf-c3ee-4eb8-179e-ad28e0ecde3a. It will be ignored and discarded from the JMS queue.
I have tried changing follwoign settings but still no use...
Under the PROCESSING tab, under XI SETTINGS
Time period for Duplicate Check for EO(IO) (secs) it was set to 86400
I have changed this to 300 seconds
Regards,
Chinna.

remove the duplicate entry from the java table XI_AF_SVC_ID_MAP

File to JMS Scenario - Error is Receiver JMS Adapter

Hi,
I am working on File to JMS scenario. I have deployed all required jars for MQ 6.0.2 in SDM. Create all MQ related objects. I am getting following error for Receiver JMS adapter in CC Monitoring.
Please let me know if I have missed anything. Is there anything to do in Visiual Administrator->JMS Provider or JMS Connector for these kind of Scenarios?
Thanks in Advance...
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'sap:QM_APPLE'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:212)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)

Hi,
I have made my Qmanager as default Qmgr. Now the error is :- Socket connection attempt refused
Recv JMS Communication Channel Error:-
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'sap:QM_APPLE'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2059
MQJE011: Socket connection attempt refused
at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:212)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:318)

Error initializing Sender JMS Adapter

Similar Messages

Maybe you are looking for