JMS Adapter Parameters

Hi All:
I am using XI 3.0 and When I am confuring JMS adapter i am seeing these parametes :-
QueueConnectionFactory Java Class :progress.message.jclient.QueueConnectionFactory
Queue Java Class : progress.message.jclient.Queue
Server Port : 2506
JMS Queue : SampleQ1
Now I want to configure adapter with the Queue that I created in the Visual Admin.
with this info :
JNDI Name :QueueConnectionFactory
Factory Type : QueueConnectionFactory
USer : J2EE_ADMIN
Queue name : MyTestQueue
Can any one tell me now what will be the parameters for JMS as per the above input.
QueueConnectionFactory Java : ?
Queue Java Class : ?
Server Port :
JMS Queue : ? //MyTestQueue

Hello Faooq,
QueueConnectionFactory Java Class
This is the SonicMQ implementation of the QueueConnectionFactory.
A JMS client, in this case the adapter, uses a QueueConnectionFactory object to generate QueueConnection objects of a JMS provider.
The default value for SonicMQ 3.0 is progress.message.jclient.QueueConnectionFactory
Queue Java Class
A queue object encapsulates a provider-specific queue name. This enables a client to make the queue JMS API methods known.
The default value for SonicMQ 3.0 is progress.message.jclient.Queue
<a href="http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/prog_model.html">http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/prog_model.html</a>
<a href="http://edocs.bea.com/wls/docs81/jms/fund.html">http://edocs.bea.com/wls/docs81/jms/fund.html</a>
With Regards,
Raju.
Please give points if useful.

Similar Messages

JMS Adapters Parameters

Hi all
where can i find the jms adapter parameters in oracle fusion?
Edited by: Senthil Raja on Apr 29, 2009 12:05 AM

Hi Senthil,
You can set the headers in this way :
<binding name="Consume_Message_binding" type="tns:Consume_Message_ptt">
<pc:inbound_binding />
<operation name="Consume_Message">
<jca:operation
ActivationSpec="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec"
DestinationName="jms/DemoQue"
UseMessageListener="true"
PayloadType="TextMessage"
OpaqueSchema="true" >
</jca:operation>
<input>
<jca:header message="hdr:InboundHeader_msg" part="inboundHeader"/>
</input>
</operation>
</binding>
The headers/parameters are documented in : http://download.oracle.com/docs/cd/B31017_01/integrate.1013/b28994/adptr_jms.htm
Metalink Note : 743610.1
Hope that helps!
Cheers
A

JMS Adapter - Set Additional JMS Parameters or Replace Default Settings

Hi colleagues,
We are using PI/XI 7.0 (SP 12).
In trying to set up a Communication Channel using JMS Adapter to connect to Oracle AQ, I do not see the checkbox "Set Additional JMS Parameters or Replace Default Settings" , nor is the table for the parameters / value visible.
We have deployed the driver file as described in the How-to- guide: How To Install and Configure External Drivers for JDBC & JMS Adapters
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f04ce027-934d-2a10-5a8f-fa0b1ed4d88f?quicklink=index&overridelayout=true]
In setting up the Communication Channel so far:
Type: Sender
Transport Protocol: Access JMS Provider Generically
Message Protocol: JMS 1.x
Adapter Engine:      Integration Server
After this I expect to see the checkbox "Set Additional JMS Parameters or Replace Default Settings", but it is not there.
Therefore I am not able to select it in order to enter parameters like:
JMS.QueueConnectionFactoryImpl.classname
JMS.QueueConnectionFactoryImpl.method.setHostName
JMS.QueueImpl.classname
JMS.QueueImpl.constructor.... etc
Can someone please share if this because we are on too low SP or do we need to do something additional before it becomes visible? Is this a feature that only became available as of PI/XI 7.0 SP 13 or 14 ?
I checked both Sender and Receiver channel type, and it does not appear for both.
Thanks & Cheers,
Jodie

Hi experts,
We are using PI 7.1 and I've set up a communication Channel using JMS Adapter to send
messages to a Sonic MQ queue.
I need to send some values as JMS parameters, two of which are constants and two are values
from the Sender message. I tried defining and setting up the parameters with constants values
in the Communication Channel under the Advanced tab by selecting the check-box
set Adapter-specific Message Attributes as follows:
Name     TYPE
ContentType     String
ReturnValue     boolean
Name     VAlue
Contenttype     CompanyCode
ReturnValute     true
This however lead to an error in the Adapter Engine (RWB).
My problem is:
1. Can anyone please instruct me as to how to go about defining and setting up
   additional JMS parameters?
2. How to go about defining/setting up variables that will get their values from
   the sender message?
Thanks & Cheers,
Joe

Use of Additional Parameters in JMS Adapter

Hi Frnds,
Can any one explain the use of Additional Parameters in JMS Adapter.
Regards,
Raj

HI,
To make additional settings or replace the default settings, enter the parameters and values in the table.
those are JMSMessageClass and JMS.Message.method.setStringProperty.
For more details.
http://help.sap.com/saphelp_nw04/helpdata/EN/10/b1b4c8575a6e47954ad63438d303e4/content.htm
Thanks.

Content conversion in Sender JMS Adapter

Hi,
Scenario is file to IDoc
My source file is   ' ; ' separated file coming from MQ via JMS adapter. now I need to convert this to XI.
Source DT looks like
Root
HEADER (Occurance 1)
     Field 1
     ISOCURCD
     TRANKODE
     IDENTIFIER
     DATO
     TIME
DETAIL(Occurance 1 to unbounded)
     ISOCURCD
     TRANKODE
     EFFDATE
     COMMDATE
     DKKVAL1
     USDVAL1
TRAILER(Occurance 1)
     ISOCURCD
     TRANKODE
      TRANCOUNT
According to How to use content conversion in JMS guide from SDN i have configured the content conversion parameters in the module of JMS sender adapter.
In the processing sequence given the module name as localejbs/AF_Modules/MessageTransformBean and module Key as Plain2XML.
And in module configuration
Parameter Name                      Parameter Value
Transform.Class                          com.sap.aii.messaging.adapter.Conversion
Transform.ContentType                     text/xml;charset=utf-8
xml.keyFieldName                          TRANKODE
xml.keyFieldType                          CaseSensitiveString
xml.recordsetName                          Root
xml.documentName                                   MT_ROOT
xml.documentNamespace                          http://XXX.XXX.XX/xi/XXXXX
xml.processFieldNames          fromConfiguration
xml.conversionType                                   StructPlain2XML
xml.recordsetStructure          HEADER,1,DETAIL,*,TRAILER,1
xml.HEADER.fieldNames           Field1,ISOCURCD,TRANKODE,IDENTIFIER,DATO,TIME
xml.HEADER.fieldSeparator                     ";"
xml.HEADER.keyFieldValue                     H
xml.fieldSeparator                                      ";"(if i don't use this then the file is not being picked and getting an error in the CC monitoring of RWB saying xml.field separator missing.)
Similarily for Detail and Trailer records as well.
But when I run the scenario, the file is being picked up but I am not getting any payload into the inbound message.
Can you please help me where I have configured wrongly. And one more thing will this configuration help for ; separated file .
Thanks & Regards,
Kumar
Edited by: Kumar on Dec 19, 2007 11:11 AM
Edited by: Kumar on Dec 19, 2007 11:15 AM

HI,
Have you gone through the below pdf i think it will help to find ur mistake.
How to use conversion modules in JMS - https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
Thnx
Chiarg

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.

PI 7.11 JMS adapter using JNDI weblogic server issue

Hi SAP experts,
I have a scenario to integrate to a application using JMS adapters. we use SAP PI 7.11 version.
We have deployed JMS drivers successfully and We face issue here to connect to weblogic server
We are using JMS adapter using JNDI to connect to weblogic server version 10.3.
Can anyone help with the exact format to be used in JMS properties table and additional parameters table in JMS communication channel. Your quick help will be appreciated.
A channel error occurred. The detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up destination: AccrualDetailsQueue for profile: ConnectionProfile of channel: CC_SND_JMS on node: 3010950 having object id: 673696a9fe8c39fdab32213f0930afb3: javax.naming.NameNotFoundException: Unable to resolve 'AccrualDetailsQueue'. Resolved '' at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination(JndiConnectorImpl.java:168)<br

Hi Padmini,
Refer to the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
It was very helpful to me, for configuring the additional parameters in the communication Channel JMS.
I leave you some screenshots of the settings that I did.
I seize the opportunity to ask you, where do I can get the drivers (.Jar) for Weblogic?
Regards.
Rodrigo.

File Content Conversion in JMS Adapter

Hello,
I am trying to use module parameters to convert File to XML in Sender JMS adapter. I have followed the instructions in the SAP document (3.1 Example of a Simple Conversion in a Sender Communication Channel)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50061bd9-e56e-2910-3495-c5faa652b710
The problem I am facing is instead of creating one xml message for all the lines in the file; it is creating one message per line. Not sure what I need to do get all the lines in to one xml message.
Please let me know if any of you have faced similar issue.
Thanks
AV

The Parameter xml.recordsetsPerMessage can only be used if it is a complex structure. I mean it needs a recordSet with Keys..etc and What I am trying to do is a simple FCC using
Transform.Class=com.sap.aii.messaging.adapter.Conversion
Transform.ContentType=text/xml;charset=utf-8
xml.conversionType=SimplePlain2XML
xml.documentName=PurchaseOrder_Root
xml.documentNamespace=http://namespace
xml.fieldFixedLengths =2,10,10,3,..
xml.fieldNames = DATA1,DATA2,DATA3....
xml.processFieldNames=fromConfiguration
xml.structureTitle=PurchaseOrder
I am expecting
<PurchaseOrder_Root>
<PurchaseOrder>
<DATA1> </DATA1>
<DATA2> </DATA2>
</PurchaseOrder>
<PurchaseOrder>
<DATA1> </DATA1>
<DATA2> </DATA2>
</PurchaseOrder>
</PurchaseOrder_Root>
When I use the above Module Config it is giving me 
</PurchaseOrder_Root>
<PurchaseOrder>
<DATA1> </DATA1>
<DATA2> </DATA2>
</PurchaseOrder>
</PurchaseOrder_Root>
</PurchaseOrder_Root>
<PurchaseOrder>
<DATA1> </DATA1>
<DATA2> </DATA2>
</PurchaseOrder>
</PurchaseOrder_Root>

Using JMS adapter with J2ee native queuing system

Hi there,
As far as I have understood J2EE contains it's own native queuing system (JMS). Since the J2EE is part of the WAS, shouldn't it be possible to somehow use XI's JMS adapter in conjunction with this native JMS?
I've tried to search many places in many ways, but haven't been able to find any info. Is it possible at all?
Hope, some of u guys can help out there:-)
Regards,
Daniel

Hi Keith,
It looks as if you are in the same situation.
We have this working very nicely now and I'm happy to share. In fact I was just granted wiki permissions so I can add the information there along with screen shots.
Informaiton on this configuration is very scattered but I imagine many people would find it useful for integrating with Mainframes without adding any complexity to the legacy environment. Let me come back to you with some more inormation, but for now you can get started with this:
Insert a module as the 3rd line in your Module Processing Sequence to use AF_Modules/MessageTransformBean and give it a key in order to associate with the parameters you will need to type in below. These parameters are very similar to normal XI File adapter parameters.
SAP Note 793922 has more info on the parameters... not the greatest reference I know.
Also this has some info...
http://help.sap.com/saphelp_nw04/Helpdata/EN/57/0b2c4142aef623e10000000a155106/content.htm
I'll try and get some screen shots up on the Wiki.

XML document conversion to Plain document in XI using JMS Adapter?

Hi,
We are trying to send an soap based XML document from ECC to MQSeries 6.0 using PI 7.0. I created receiver communicaiton channel to MQ with the below modules
1. AF_Modules/MessageTransformBean - Module Key XML2Plain
2. SAP XI JMS Adapter/ConvertMessageToBinary - Module Key CallJMSService
3. SAP XI JMS Adapter/SendBinarytoXIJMSService - Module Key Exit
Module configuration parameters I provided are
XML2Plain- Transform.Class com.sap.aii.messaging.adapter.Conversion
 TransformContentType text/plain;charset=utf-8
 xml.addHeaderLine 0
 xml.conversionType SimpleXML2Plain
 xml.fieldSeparator ,
 xml.fixedLengthTooShortHandling Cut
The payload I am using is
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Company xmlns:ns0="http://bnsf.com/hr/tm">
 <Row CCODE="1001" DESC="test company"/>
</ns0:MT_Company>
When I test in RWB
1. The channel monitoring shows green and the below message
"Successfully connected to destination 'queue:///QL_DAVEOUT?targetClient=1"
2. RWB shows error message "Error while sending message:invalid content type for SOAP:TEXT/HTML;HTTP 500 Timeout"
3. when I look at the message, I see the last message shows as
"2008-06-16 15:16:44 Success Transform: transforming the payload ..." and I do not see any more messages.
Can anyone help me here? Thanks in advance

I changed the payload to
<xml version="1.0" encoding="UTF-8">
<ns0:MT_Company xmlns:ns0="http://bnsf.com/hr/tm">
<row CCODE="1001" DESC="TEST" />
</ns0:MT_Company>
this time i am getting
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_SAP_COMPANY_TO_MQ_COMPANY_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17)</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_SAP_COMPANY_TO_MQ_COMPANY_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor411.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy220.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:118) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor411.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy220.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17)(:main:, row=4, col=17) -> com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1872) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1846) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1872) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1846) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more</Trace>

Configuration of JMS Adapter in Central Adapter Engine

Hi all,
I have configured Sender JMS Adapter in Central Adapter Engine with the following parameters:
Adapter type : JMS
Transport Protocol : WebSphere MQ (non-jms)
Message Protocol : JMS1.x
Adapter Engine : Integration Server
Queue Connection Factory java class :Com.ibm.mq.jms.MQQueueConnectionFactory
Queue java class : com.ibm.mq.jms.MQQueue
ipadd : localhost
port : 1414
Queue Manager name : TEST.QMGR
Channel Name : CH1
JMS Queue : LQ
CCSID : 437
Protocol : TCP/IP
JMS-compliant : WebSphere MQ(non-jms)
JMS Queue user : MUSR_MQADMIN
Mapping of message : Entire Message = JMS Payload
But the status is red with an error message Sender Details : NULL
Could you please tell me what went wrong?
Regards
Sathya

Hi,
Make sure that Websphere MQ server is running.
If u r comfortable with java, you can even write a Java code to acces the server and check if the JMS server is working fine. Some times there will be sample applications provided by Websphere MQ itself.
Once the java program works then it will be easy to debug the error over here.
Regards,
P.Venkat

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

JMS adapter settings for response to dynamic queue

Hello,
We are sending a message through JMS to SAP in a synchronous manner (client waiting for the reply after sending the request). The SAP is receiving and processing the message.
We configured the JMS Sender & Receiver channel as per solution given in SDN for the quetion. ( (2.8) Does the JMS Adapter support the JMSReplyTo feature? )
1. In Sender communication channel, checked the "JMS Message ReplyTo Destination" attribute of 'Adapter specific message attributes'
2. In Receiver communication channel, added the "JMS.Message.DynamicDestination" parameter and value 'true' (without quotes for both strings) in "Set JMS Additional Parameters" table
3. Added the "JMSReplyTo" header syntax in input xml message as below:
 a. Message : <?xml version="1.0" encoding="UTF-8"?>
 <ns0:getEmployeeInfo xmlns:ns0="namespace">
 <employeeId>0000001</employeeId>
 </ns0:getEmployeeInfo>
 b. Destination = com.someDestination
 c. JMSReplyTo= com.someReplyQueue
We have selected Transport protocol option "Access JMS Provider Generically"
But it is not able to send the reply to replyTo destination of the message.
Wondering if there is anything in the JMS Adapter setting like reply to Destination (technical term DCJMSReplyTo) which can be set to reply queue of the message (to a dynamic destination).
Please let me know in case anybody knows about the same.
Thanks & Regards,
Jayashri Rade

Refer: http://docs.oracle.com/cd/B14099_19/integrate.1012/b25307/adptr_jms.htm
•The JMS API specifies three types of acknowledgments that can be sent by the JMS publisher:
◦DUPS_OK_ACKNOWLEDGE, for consumers that are not concerned about duplicate messages
◦AUTO_ACKNOWLEDGE, in which the session automatically acknowledges the receipt of a message
◦CLIENT_ACKNOWLEDGE, in which the client acknowledges the message by calling the message's acknowledge method

How to set ApplIndentityData header field in JMS adapter

Hi Guys ,
    I have one requirement for update the field in SAP JMS header. I am using transport protocol for IBM Websphere MQ in JMS adapter.
While sending data to IBM Websphere MQ Queue via JMS Adapter, need to set the field called ApplIndentityData with the appropriate value which is populate to a MQHRF2 header of a message.
So, regarding that where will do it? Means JMS receiver adapter or IBM MQ level. If JMS receiver adapter, I think using ASMA, So please guide me how to set this filed value in JMS adapter or share any document you have.
Thanks & regards
Vijaykumar S

Hi RejaSekar,
       I reffered your blog and did the below settings in JMS module and ASMA settings.
1) Changed the mode for u201CJMS-Complaintu201D instead of u201CWebsphere MQ(non JMS)u201D
2) Additional JMS message properties tab created below property name and java type.
       LocalName    --> String
       Partname      --> String
3) In module parameter tab added the below module name and key
    AF_Modules/DynamicConfigurationBean   --> LocalEnterpriseBean --> RFH2HEADER
4) Under parameter Tab
     RFH2HEADER       -->   key.0      -->     insert http://sap.com/XI/System/JMS DCJMSMessageProperty0
     RFH2HEADER       -->   key.1      -->     insert http://sap.com/XI/System/JMS DCJMSMessageProperty0
     RFH2HEADER      --> value.0    -->    LocalName
     RFH2HEADER      --> value.1    -->    PartnerName
Kindly check the above settings whether this is correct or wrong. If anything wrong please let me know what we need to change JMS receiver adapter.
Actually my requirement is need to set these parameters and set the value to that parameters and pass in to /usr folder of a WebsphereMQ message.
Kindly check and help me out.
Thanks & regards
Vijayakumar S

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

JMS Adapter Parameters

Similar Messages

Maybe you are looking for