SAP XI JMS Adapter

Gud Mrng , can any one provide me the information about JMS Adapter in SAP-XI,
with screen shots.....Plz

Hi,
Please refer into this blog to use the J2EE WAS JMS Service of XI,
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
To connect XI to any other JMS adapters / service, you would need to install the driver of the JMS adapter on your XI server. Please look into this for the same,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
Also, the SAP Library help on JMS adapters is quite good,
http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
Regards
Bhavesh

Similar Messages

Error in JMS Adapter:

Receiving the below error, thought of JMS Drivers problems undeployed and re-deployed several times, but still problem persist in XI.
Success     MP: Processing local module localejbs/SAP XI JMS Adapter/ConvertMessageToBinary
2010-09-09 11:45:21     Error     MP: Exception caught with cause com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
2010-09-09 11:45:21     Error     Exception caught by adapter framework: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.
Error     Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at SAP XI JMS Adapter, the whole lookup name is localejbs/SAP XI JMS Adapter/ConvertMessageToBinary..
2010-09-09 11:45:22     Success     The message status set to WAIT.
2010-09-09 11:45:22     Success     The asynchronous message was successfully scheduled to be delivered at Thu Sep 09 11:50:21 CDT 2010.
The JNDI Libraries are available in Visual Admin, not sure what else causing the issue. Any guru's help is appreciated

XI 3.0 SP20
Regarding the note, that only applied below sp4. We are on SP20. The default values appears but those are not working.This seems to be a problem with Dev only, Q and P is working fine at this moment
If i actually delete module processor's from Sender and Receiver channel, things are working fine. But not sure if it is going to break anything. And this needs to be applied in all landscape. But i have to present a reason, why this weird behavior all of a sudden
Sender
    SAP XI JMS Adapter/ConvertJMSMessageToBinary
    SAP XI JMS Adapter/ConvertBinaryToXMBMessage
Receiver
    SAP XI JMS Adapter/ConvertMessageToBinary
    SAP XI JMS Adapter/SendBinarytoXIJMSService

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>

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

Message format to be send to the JMS Adapter

Hi all,
I have a very strange situation. i have a sender JMS channel where i am trying to use the Message Transformation module
I have done the configuration but the problem is that i have made a .dat file
AAABBBCCC
DDDEEEFFF
and i am using the PutMessage fuction to put the messages in the Queue and process it
dont knw y but the newline characters get disapeared. I am not sure why this is happening on investigation i found that we have 2 modules which are used before the conversion for XML
localejbs/SAP XI JMS Adapter/ConvertJMSMessageToBinary
localejbs/SAP XI JMS Adapter/ConvertBinaryToXMBMessage
Is it because of this.. that the channel is behaving like it. please give your inputs as to what can be done
if so will the messages work fine if the messages are directly put into the queue
what special character should i use to get the desired output with new line characters

Hi Abhisheek,
It doesnt work... i tried adding the ISO 8859 1 in the module and also tried setting the CCSID which is to 819.. for the ISO 8859 1.. bt i doesnt work
i dont understand why its behaving in such a manner but i really feel some silly mistake i am missing out a parameter or something...
I have created a txt file with 2 line only
AAABBBCCC
DDDEEEFFF
And jst trying to pick up this file without any conversion ... kind of a JMS to File senario without any modules.. it still doesnt work..
i dnt think it is recognizing the new line which i have given.. or may be because the conversion modules are stripping out the new line characters
And i have not upgraded my system as well. its XI 7.0 SP 9
RGds
ADitya

Content conversion question for JMS adapter

Hi,
I need to put this again here.
I have the scenario R/3 IDoc -> XI -> MQ (webshpere). MQ requires plain text.
I have the IDoc ORDERS05 in multi level (nested in layers). But using the how to guid to convert the content I could go up to on level.
Based on the thread
Process Integration (PI) & SOA Middleware
It is not possible to use the conversion modules with XML2Plain key with parameter xml.conversionType value StructXML2Plain.
Please confirm if this is possible to convert a structure like below,
<ZSYSEX01>
.<IDOC BEGIN="1">
....<EDI_DC40 SEGMENT="SEGMENT0">
........<FIELD1>HEADER</FIELD1>
....</EDI_DC40>
....<E1STATS SEGMENT="SEGMENT1">
........<FIELD2>100</MANDT>
........<Z1HDSTAT SEGMENT="SEGMENT2">
...........<FIELD3>0200000716</FIELD3>
...........<Z1ITSTAT SEGMENT="SEGMENT3">
...............<FIELD4>1000</FIELD4>
...........</Z1ITSTAT>
........</Z1HDSTAT>
........<Z1HDSTAT SEGMENT="SEGMENT2">
...........<FIELD3>0200000717</FIELD3>
...........<Z1ITSTAT SEGMENT="SEGMENT3">
...............<FIELD4>1000</FIELD4>
...........</Z1ITSTAT>
...........<Z1ITSTAT SEGMENT="SEGMENT3">
...............<FIELD4>1001</FIELD4>
...........</Z1ITSTAT>
...........<Z1ITSTAT SEGMENT="SEGMENT3">
...............<FIELD4>1002</FIELD4>
...........</Z1ITSTAT>
........</Z1HDSTAT>
....</E1STATS>
.</IDOC>
</ZSYSEX01>
to plain text in JMS adapter.
Thanks!
Jason

Hi,
You have to use Content Converiosn in JMS Adapter Receiver side,
Module Sequence in the Receiver Channel
No. Module Name Module Key
1 localejbs/AF_Modules/MessageTransformBean XML2Plain
2 localejbs/SAP XI JMS Adapter/ConvertMessageToBinary CallJMSService
3 localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService Exit
Bases on Structure you have to configure the processing parameters,
please see the below link, it will helps you more
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
Regrads
Chilla..

Debugging JMS adapter with Module Configuration

Hi.
I have a problem debugging my JMS adapter with module configuration.
All I get from the Message Monitor is a status "System Error", and no error category or error message.
I know there's an error in my Module configuration design, since it works fine without.
My configuration looks like this:
PROCESSING SEQUENCE:
1 localejbs/AF_Modules/MessageTransformBean Local Enterprise Bean XML2Plain
2 localejbs/SAP XI JMS Adapter/ConvertMessageToBinary Local Enterprise Bean convert_XI2Bin
3 localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService Local Enterprise Bean exit
MODULE CONFIGURATION:
XML2Plain Transform.Class com.sap.aii.messaging.adapter.Conversion
XML2Plain Transform.ContentType text/plain;charset=utf-8
XML2Plain xml.conversionType StructXML2Plain
XML2Plain xml.addHeaderLine 0
XML2Plain xml.recordsetStructure STARTRECORD,DATARECORD,SERVICEYDELSERRECORD,SLUTRECORD
XML2Plain xml.STARTRECORD.fieldFixedLengths 2,8,6,7,10,7,3,3
XML2Plain xml.DATARECORD.fieldFixedLengths 2,8,6,4,35,17,7,7,7,5,5,5,18,18,18,18,18,18,18,18,18,9
XML2Plain xml.SERVICEYDELSERRECORD.fieldFixedLengths 2,8,6,4,3,20,18,18,18
XML2Plain xml.SLUTRECORD.fieldFixedLengths 2,8,6,7,10,7
XML2Plain xml.STARTRECORD.fixedLengthTooShortHandling Cut
XML2Plain xml.DATARECORD.fixedLengthTooShortHandling Cut
XML2Plain xml.SERVICEYDELSERRECORD.fixedLengthTooShortHandling Cut
XML2Plain xml.SLUTRECORD.fixedLengthTooShortHandling Cut
The structure of the message looks like this:
<STARTRECORD> (occurence = 1)
<DATARECORD> (occurence = 1..unbounded)
--- <SERVICEYDELSERRECORD> (occurence = 0..unbounded)
<SLUTRECORD> (occurence = 1)
I've crosschecked every field, and it length and all looks like it should!
The worst part is the one not getting the reason why it fails. Any way I can get this information?
I've tried to look in the Adapter Framework log, but I have no clue where to look for anything usefull.
Help
Regards Peter

Hello,
Below is the module configuration in my JMS sender channel:
Check Message Local Enterprise Bean key
ConvertJMSMessageToBinary Local Enterprise Bean convert_JMS2Bin
ConvertBinaryToXMBMessage Local Enterprise Bean convert_Bin2XI
CallSapAdapter Local Enterprise Bean call_AF_MS
CheckMessage is a custom module which does some check on the incoming message.
Now what I want to know is at which position should I include the DynamicConfiguration Bean? Should it be included at position 1 or at position 2 or someother position?
~Thanks.

Receiver JMS Adapter Content Conversion issue

Scenario :
R/3 -->XI -->MQ(XML2Plain)
Hi
We are using Receiver JMS Adapter to send the Message from XI to MQ.
The XML has to be converted to plain file. And Content conversion is
being done.
With the new development, the message type defined consist of 8 fields
with fixed length. The XML message goes successfully from XI to MQ
without any content conversion. But once simple content conversion is
being done for Receiver JMS adapter, even though the message is
received but its empty (without any data records). The adapter
monitoring everything seems fine and it gives the status that message
converted to binary and the message is delivered to MQ. Though on
checking the messages there is no data records.
Below is my content conversion configuration done in Module tab. Kindly
revert back what can be the problem as have done exactly the same way
as described in Content Conversion How to Guide for receiver JMS.
localejbs/AF_Modules/MessageTransformBean Local Enterprise Bean XML2Plain
localejbs/SAP XI JMS Adapter/ConvertMessageToBinary Local Enterprise Bean convert_XI2Bin
localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService Local Enterprise Bean exit
XML2Plain Transform.Class com.sap.aii.messaging.adapter.Conversion
XML2Plain TransformContentType text/plain;charset=utf-8
XML2Plain xml.addHeaderLine 0
XML2Plain xml.addHeaderLine SimpleXML2Plain
XML2Plain xml.fieldFixedLengths 8,10,10,20,40,40,8,8
XML2Plain xml.fixedLengthTooShortHandling Cut
regards.
santosh.

Hi,
check localejbs/SAP XI JMS Adapter/ConvertMessageToBinary Local Enterprise Bean convert_XI2Bin
this is not CallJMSService.
And also check the receiver Structure, if it is falt structure its ok, else
see the below link if it has the complex structure , how to handle..
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
Regards
Chilla..

Module in Receiver JMS Adapter

I am using the following Modules in one of receiver JMS adapter. What is the function of each Bean that we are using here ??
Any links in this regard is appreciated
1-AF_Modules/RequestOnewayBean-Local Enterprise Bean-0
2-SAP XI JMS Adapter/ConvertMessageToBinary-Local Enterprise Bean-convert_XI2Bin
3-SAP XI JMS Adapter/SendBinarytoXIJMSService-Local Enterprise Bean-exit
4-AF_Modules/WaitResponseBean-Local Enterprise Bean-1
thanks
kumar

Hi,
The JMS adapter (Java Message Service) enables you to connect messaging systems to the Integration Engine or the PCK.
This link will help you...
JMS adapter
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/5393. [original link is broken] [original link is broken] [original link is broken]
http://help.sap.com/saphelp_nw2004s/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
ref this weblog by william Li
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
syn-asyn bridge( with out bpm)
/people/venkataramanan.parameswaran/blog/2007/01/18/syncasync-communication-in-jms-adapter-without-bpm-sp19
similary asyn-syn bridge
/people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
also refer
http://help.sap.com/saphelp_nw04/helpdata/en/45/20d1dec20a0732e10000000a155369/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/how%20to%20use%20the%20content%20conversion%20module%20with%20the%20xi%203%20j2ee%20jms%20adapter
/thread/217893 [original link is broken]
JMS adapter -Message format pre-requisites
/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

JMS adapter not registered

We are integrating Weblogic JMS with SAP using JMS adapter in XI and in communication Channel we are getting message as "JMS_SENDER - n/a - No adapter registered for this channel " , How to register the JMS adapter ??

Sorry,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ffd890-0201-0010-708f-d5dad2dfcf3a
or try it other:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a05b2347-01e7-2910-ceac-c45577e574e0
Edited by: Carlos Ivan Prieto Rubio on Dec 17, 2007 5:17 PM

JMS Adapter - data conversion xml- structured data has extra characters

Further to [Using MQ / JMS adapter with legacy system to talk to SAP;, I am using the Module tab on my receiver JMS Adapter to convert the xml payload to a structured format. It converts to the mainframe ebcdic code set. I am on PI 7.11, and the MQ Series (which JMS interacts with) is 6.0. The code I have is comparable to the wiki:[http://wiki.sdn.sap.com/wiki/display/XI/HowTo...ContentconversionmodulewithJ2EEJMS+adapter], i.e. the example at the very bottom of that article.
The issue we are having is that an extra character gets inserted at the end of each structure (within the message), i.e. our message contains 4 structures, but when we view the structured data on our mainframe system (that arrives from PI), the entire message is shifted by 4 characters... by 1 after the end of each structure. On the mainframe, this extra character appears as '.'. It must be an end-of-line or something...
Has anyone had the same issue? If so, were you able to resolve? I could probably set up my message data type to just be one big declare (thus eliminating the use of structures within it), but that is something I'd rather not do.
We are in the process of reviewing Note 856346, #6 but not sure if it applies.
Regards,
Keith

Hi,
check localejbs/SAP XI JMS Adapter/ConvertMessageToBinary Local Enterprise Bean convert_XI2Bin
this is not CallJMSService.
And also check the receiver Structure, if it is falt structure its ok, else
see the below link if it has the complex structure , how to handle..
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
Regards
Chilla..

JMS adapter ModuleProcessorException

Hello experts,
I am trying to set up a MQ -> XI connection through the JMS adapter.
Setting up the CC was fairly easy, and I can see the nice green light in the adapter monitor for the sender channel. But so quickly I try to send a message from MQ to XI I get the following error:
26.06.2006 12:38:05.522 ERROR Error during processing local bean: localejbs/SAP XI JMS Adapter/ConvertBinaryToXMBMessage
26.06.2006 12:38:05.523 WARNING Catching com.sap.aii.af.mp.processor.ModuleProcessorException: Error during processing local bean: localejbs/SAP XI JMS Adapter/ConvertBinaryToXMBMessage caused by: com.sap.aii.af.mp.module.ModuleException caused by: com.sap.aii.af.service.cpa.impl.exception.CPAObjectException: Value with name enableDynConfigSender not available
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:266)
 at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
 at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java:949)
 at com.ibm.mq.jms.MQQueueReceiver.receiveAsync(MQQueueReceiver.java:861)
 at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:401)
 at java.lang.Thread.run(Thread.java:534)
Caused by: com.sap.aii.af.mp.module.ModuleException caused by: com.sap.aii.af.service.cpa.impl.exception.CPAObjectException: Value with name enableDynConfigSender not available
 at com.sap.aii.af.mp.jms.ejb.ConvertBinaryToXMBMessage.process(ConvertBinaryToXMBMessage.java:212)
 at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl10.process(ModuleLocalLocalObjectImpl10.java:103)
 at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:250)
 ... 5 more
Caused by: com.sap.aii.af.service.cpa.impl.exception.CPAObjectException: Value with name enableDynConfigSender not available
 at com.sap.aii.af.service.cpa.impl.container.CPAObject.checkNameForValue(CPAObject.java:380)
 at com.sap.aii.af.service.cpa.impl.container.CPAObject.getValueAsBoolean(CPAObject.java:676)
 at com.sap.aii.af.service.cpa.impl.container.AttributeExtendedCPAObject.getValueAsBoolean(AttributeExtendedCPAObject.java:310)
 at com.sap.aii.af.mp.jms.ejb.ConvertBinaryToXMBMessage.process(ConvertBinaryToXMBMessage.java:143)
 ... 7 more
I have rasied the trace level, so I was able to see the actual MQ message in the trace, and the first module (convertJMSMessageToBinary) seems to run without any problem. Furthermore, I have added the 3 mandatory configuration parameters for the ConvertBinaryToXMBMessage module, but it didnt help.
Any help would be greatly appreciated.

I am getting the following error on a JMS Sender channel
XI inbound processing failed for message at time 2008-04-21|13:28:09.251+0200. JMS and XI identifiers for the message are ID:ffffffffa4d02a43:57210022:1196FC3DEAC and 04e37730-0f96-11dd-a0ae-001b78018d64 respectively. The JMS adapter will rollback the database and JMS session transactions. If the session is transacted, the message is not lost and will be retried later. The exception stack trace is java.lang.Exception: Value with name enableDynConfigSender not available
at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java:963)
at progress.message.jimpl.Session.deliver(Unknown Source)
at progress.message.jimpl.Session.run(Unknown Source)
Any id's
Sender channel is SONICMQ
wondering what "Value with name enableDynConfigSender not available " means.

Error with the Receiver JMS Adapter (Connection On-Demand feature)

Hi,
In high volume we are experiencing errors with the Receiver JMS Adapter and the connection On-demand feature:
Adapter Framework caught exception: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'
Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: while trying to invoke the method com.sap.aii.adapter.jms.api.connector.DisconnectorListener.notifyEvent(java.lang.String) of an object loaded from local variable 'listener'.
The message status was set to WAIT.
Looks like the message is successfuly reprocess after the wait period but the ALEAUD/Akcnowledgment are not successful in the sender ECC system. (SAP -> PI - > JMS)
Any idea?
PI 7.1 EHP1
Thanks,
Martin
/people/sunil.ojha5/blog/2010/08/31/review-of-sap-pi-jms-adapter-on-demand-connection-feature
Edited by: Martin Lavoie Rousseau on Jun 3, 2011 3:21 PM

Please ensure to have specified an User and password to connect to JMS server (don't leave the fields empty).

How does PI delivery acknowledment work in JMS adapter? Please help!

Hi Experts,
In JMS receiver communication channel there is an option (check box) for "Return PI delivery acknowledgment". I want to know how does this work? In what format (email, alert) we get the acknowledgment? What all configurations are need to do get the acknowledgment?
Kindly help ASAP! Any blog or doc on this will be really helpful.
Thanks
Gopal

Hi Gopal,
1)notes for JMS adapter
Go thru these notes 790963,747601,746393,856346,802754,
837501 and 790224.
2)information regarding use of JMS Adapters,Go thru these links of help.sap.com
JMS Adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
Configuring the Sender JMS Adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
Configuring the Receiver JMS Adapter:
http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
JMS-Provider-Specific Settings:
http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
And to deploy the jars which are given in the JMS Adapter link go thru this article "How To Install and Configure External Drivers for JDBC and JMS Adapters"
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/how%20to%20install%20and%20configure%20external%20drivers%20for%20jdbc%20and%20jms%20adapters.doc
Hope it helps.
Regards
joel

JMS Adapter and Conversion Agent

Hi,
Has anyone worked on JMS adapter and Conversion module? JMS adapter is working fine without the conversion agent module.
processing sequence is as follows
1 SAP XI JMS Adapter/ConvertJMSMessageToBinary Local Enterprise Bean convert_JMS2Bin
2 SAP XI JMS Adapter/ConvertBinaryToXMBMessage Locl Enterprise Bean convert_Bin2XI
3 sap.com/com.sap.nw.cm.xi/CMTransformBean Local Enterprise Bean 0
4 CallSapAdapter Local Enterprise Bean call_AF_MS
Also I have given the Parameter Name and value.
Let me know if i am missing something.

I have done the configuration in sender JMS channel. I even created file sender and it is not working.
when i went and checked the initialization events in http://xxxx:50000/CMViewer, I can see some errors under service Initialization.

SAP XI JMS Adapter

Similar Messages

Maybe you are looking for