JMS - Adapter Module

Hi ,
I am using an adapter module in JMS sender communication channel
it is throwing an exception :
NameNotFoundException: Object not found in lookup of TrimMessageIDBean in RWB
I have deployed the EAR file on XI server and in the module tab of communication channel :
localejbs/AF_Modules/TrimMessageIDBean
what parameters should I enter in Module Configuration ??
Regards
KLK

Hi KLK,
Check these on Adapter module dev:
http://help.sap.com/saphelp_nw04s/helpdata/en/96/f04142099eb76be10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/32/43d84072378031e10000000a1550b0/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e21106cc-0c01-0010-db95-dbfc0ffd83b3
Regards,
Subhasha

Similar Messages

JMS Adapter module content conversion

Hi,
I'm developing a module for the jms adapter(sender). My requirement is to parse the XI message(text) using some XML parsing api and do some formatting, logic etc and to make the jms adapter create a xml file with the processed information. Jms File Content Conversion does not suit our requirement and thats the reason we are trying this option.
My understanding is: Access the payload in the "process" method of the local ejb, apply XML parsing using JDOM etc, make a xml which should be the output of the jms adapter. This xml will be the xml with my user defined tag elements after content conversion. Can i form this xml and assign to the inputModuleData? Will the jms adapter use this string to create the xml and send to IS? Are there any other parameters to be set or processes to be done?
Also in which sequence should I put my adapter module in communication channel.
================================================
My code snippet:
public ModuleData process(ModuleContext moduleContext, ModuleData inputModuleData)
 throws ModuleException
 Object obj = null; // Handler to get Principle data
 Message msg = null; // Handler to get Message object
 try
 obj = inputModuleData.getPrincipalData();
 msg = (Message)obj;
 AuditMessageKey amk = new AuditMessageKey(msg.getMessageId(),AuditDirection.INBOUND);
 Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"sample: Inside sample Module---efore reading payload");
 try
 XMLPayload xmlpayload = msg.getDocument();
 String messageStr = xmlpayload.getText();
 String inputStr = null;
 String tags[] = new String[2];
 String values[] = new String[2];
 Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"sample: Inside sample Module---before content conversion");
String tagvalue1 = messageStr.substring(messageStr.indexOf("BEGIN+"), messageStr.indexOf("'");
String tagvalue2 = messageStr.substring(messageStr.indexOf("'"), messageStr.lastindexOf("ENDING");
 tags[0] = "tag1";
 tags[1] = "tag2";
 values[0] = tagvalue1 ;
 values[1] = tagvalue2 ;
 Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"sample: Inside sample Module---after content conversion");
 Document xmldoc = null;
 DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
 DocumentBuilder builder = factory.newDocumentBuilder();
 DOMImplementation impl = builder.getDOMImplementation();
 org.w3c.dom.Element e = null;
 Node n = null;
 xmldoc = impl.createDocument(null, "MT940", null);
 org.w3c.dom.Element root = xmldoc.getDocumentElement();
 for(int i = 0; i < tags.length; i++)
 e = xmldoc.createElementNS(null, tags);
 n = xmldoc.createTextNode(values);
 e.appendChild(n);
 root.appendChild(e);
 Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"sample: Inside sample Module---before dom creation");
 DOMSource domSource = new DOMSource(xmldoc);
 ByteArrayOutputStream myBytes = new ByteArrayOutputStream();
 Result dest = new StreamResult(myBytes);
 TransformerFactory tf = TransformerFactory.newInstance();
 Transformer serializer = tf.newTransformer();
 serializer.setOutputProperty("indent", "yes");
 serializer.transform(domSource, dest);
 Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"sample: Inside sample Module---before setting principal data");
 byte[] docContent = myBytes.toByteArray();
 if (docContent != null) {
 xmlpayload.setContent(docContent);
 inputModuleData.setPrincipalData(msg);
 Audit.addAuditLogEntry(amk, AuditLogStatus.SUCCESS,"sample: Inside sample Module---after setting principal data");
 catch(ArrayIndexOutOfBoundsException e)
 e.printStackTrace();
 catch(StringIndexOutOfBoundsException e)
 e.printStackTrace();
 catch(TransformerException e)
 e.printStackTrace();
 catch(Exception e)
 e.printStackTrace();
 catch(Exception e)
 ModuleException me = new ModuleException(e);
 throw me;
 return inputModuleData;

This is for sender channel. The doubt in adapter module is in the process block how will I get the main data being read by the jms adapter from the text file.As I am reading text file from websphere MQ, the content of the text file can be obtained thru xmlpayload.getText() or is there any other way.
obj = inputModuleData.getPrincipalData();
msg = (Message)obj;
XMLPayload xmlpayload = msg.getDocument();
String messageStr = xmlpayload.getText();
At present I am using my adapter module before call sap adapter, but before sap adapter there are two other modules(toBinary and to Xmb), so shld I place it before both or after both the modules.
Thanx in advance
Rachit

JMS Adapter modules source code available?

Hi Experts,
we have to build some modules for the JMS adapter. Is the source code for the existing modules/JavaBeans available somewhere?
e.g. for the
AF_Modules/RequestOnewayBean
AF_Modules/NotifyResponseBean
Thanks in advance
Peter

Hi,
>>>Is the source code for the existing modules/JavaBeans available somewhere?
1. no - not in standard
2. yes - if you decompile the archive
Regards,
Michal Krawczyk

Sync/Async communication in JMS adapter without BPM

Hi,
as of SP19 XI's JMS adapter offers this new feature for Sync/Async communication through JMS Adapter modules instead of using a BPE.
Now I would be interested to know if anybody has already successfully used this feature especially using WebSphere MQ as a JMS Provider (preferredly in the mode JMS Compliant: WebSphere MQ (non-JMS)).
I experienced some issues with the XI Message ID being used as the JMS Correlation ID which is then mapped to the MQ Correlation ID being truncated after 24 characters. So I don't exactly know whether this is due to wrong setup or some general issues with this messaging system.
Please let me know if you have any experiences at all with this new feature (please do not just post links to the following blogs, which I have thoroughly studied as well as the How-to Guide concerning this topic)
/people/venkataramanan.parameswaran/blog/2007/01/18/syncasync-communication-in-jms-adapter-without-bpm-sp19
/people/sudheer.babu2/blog/2007/01/18/asyncsync-communication-using-jms-adapter-without-bpm-sp-19
thanks & regards,
Peter

Hi Peter,
we working on the same Problem. Using IBM Websphere MQ as JMS Provider for the new feature: sync/async bridge without BPE.
we switched on a high level trace for the adapter framework and saw a problem in the receiving Object of the JMS correlation id. The notify bean receives the JMS correlationid in hex format. so the beans have two different correlations, which could not find together.
did you have any solution to get this new feature works with IBM Websphere ?
thanks
joachim

Sender/receiver JMS Adapter XML Format

What is the XML format do we need to pass to Sender/receiver JMS adapter to get it processed. Do we have any specific format like JDBC adapter.
Thanks,
Sam

Hi,
1) The JMS adapter (Java Message Service) enables you to connect messaging systems to the Integration Engine or the PCK
2) Before to use the JMS adapter we must first install the relevant JMS driver.
The required Java libraries are product-specific The provider setting specifications are the same for the receiver and sender adapter
3)We need to configure the JMS adapter in the configuration part of the Integration Builder/PCK
4) The Sender JMS adapter is configured to send JMS messages to the Integration Engine or the PCK.
5)The Receiver JMS adapter is configured to be able to convert XI messages from the Integration Server or the PCK into JMS messages
Please go through this link
1)http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/frameset.htm
2)http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/frameset.htm - Configuring the Sender JMS Adapter
3)http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/frameset.htm -
Configuring the Receiver JMS Adapter
4)http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/frameset.htm -
JMS-Provider-Specific Settings
5)http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/frameset.htm -
JMS Adapter Modules
6)http://help.sap.com/saphelp_nw04/helpdata/en/45/20d1dec20a0732e10000000a155369/frameset.htm -
Async/Sync and Sync/Async Bridge in the JMS Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
Thanks,
Soumya.

Determine Sender and Receiver in adapter module?

All,
Non-XML messages from different senders are received via the same JMS queue. In the text payload, the ID of the sender and receiver is contained.
Would it be technically possible to develop a JMS adapter module that sets the Sender Party, Sender Service, Receiver Party and Receiver Service based on the content of the message payload? Is it possible to influence sender and receiver in an adapter module?
Kind regards, Guy Crets

Hi Steven,
It seems like you can not convince XI to pick up a new message. The code below works when you use "inputModuleData.setPrincipalData(msg);" but not with "inputModuleData.setPrincipalData(msgnew);".
The error in the Runtime Workbench is: "Catching exception calling messaging system' found, cause: javax.transaction.InvalidTransactionException: Cannot invoke call from within a transactional context.".
I tried to set the RefToMessageId on the new message, but this does not work either.
Does anybody know why the InvalidTransactionException is thrown?
Here is the example code:
public ModuleData process(ModuleContext moduleContext, ModuleData inputModuleData) throws ModuleException
try {
    Message msg = (Message) inputModuleData.getPrincipalData();
    Context ctx = new InitialContext();
    ConnectionFactory cf = (ConnectionFactory) ctx.lookup(
      com.sap.aii.af.ra.ms.api.ConnectionFactory.JNDI_NAME);
    MessageFactory factory = cf.createMessageFactory("XI");
    Message msgnew = factory.createMessage(
      msg.getFromParty(),msg.getToParty(),
      msg.getFromService(),msg.getToService(), msg.getAction());
    msgnew.setConversationId(msg.getConversationId());
    msgnew.setDocument(msg.getDocument());
    inputModuleData.setPrincipalData(msgnew);
catch (Throwable t)
    ModuleException me = new ModuleException("MyException");
    throw me;
return inputModuleData;
Best regards,
Simon

JMS Adapter Content conversion using Webspear MQ

Hi All,
I have a scenario where I have to pick a flat file from WebSpear JMS Q.In turn I should convert flat structure into xml structure to parse to the RFC structure(YOTCS_I090_INV_S) and map to the traget structure.
Below is the Source structure:
Messages
->Message1
-->YOTCI_I090_INV_SYNC
--->YOTCS_I090_INV_SYNC
>item
>ZDATE
>TIME
>TZONE
>WERKS
>MATNR
>LGORT
>CHARG
>SOBKZ
>INSMK
>LIFNR
>ZMENGE
>ZMEINS
>LOT_NUMBER
>CODE_DATE
Source file look's as below:
YOTCS_I090_INV_S                                                                                4928
YOTCS_I090_INV_S                                                                                3
YOTCS_I090_INV_S                                                                                3
YOTCS_I090_INV_S                                                                                1
I am doing the file contact conversion as below in JMS Adapter:
Module Key      ParameterName                           ParameterValue
Plain2XML        Transform.Class                           com.sap.aii.messaging.adapter.Conversion
Plain2XML        Transform.ContentType                 text/xml;charset=utf-8
Plain2XML        xml.conversionType                      StructPlain2XML
Plain2XML        xml.documentName                      YOTCI_I090_INV_SYNC
Plain2XML        xml.documentNamespace            urn:sap-com:document:sap:rfc:functions
Plain2XML        xml.item.fieldFixedLengths           8,8,6,4,18,4,10,1,1,10,13,3,10,8
Plain2XML        xml.item.fieldNames ZDATE,TIME,TZONE,WERKS,MATNR,LGORT,CHARG,SOBKZ,INSMK,LIFNR,ZMENGE,ZMEINS,LOT_NUMBER,CODE_DATE
Plain2XML        xml.processFieldNames             fromConfiguration
Plain2XML        xml.recordsetStructure               item,*
Can any one help me in configuring the Content conversion? Hope you got my issue.
Thanks in Advance.
Best Regards,
Jose

Joseph,
Go thru the Below Link
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
Cheers
Agasthuri Doss

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

Regarding Module Configuration of Receiver JMS Adapter

Hi,
Now i am working on IDoc to JMS interface, I am facing complexity in creating the structure in Module tab of Receiver JMS Adapter. Because the target system is expecting fixed length file so i should use the Local EJBs available in Module tab of Receiver JMS adapter and i need to pass the fieldFixedLegth parameters for all the nodes coming from DELVRY01 Idoc. I think creating structure for all the nodes in receiver jms adapter is so complex, If you are having any other alternatives, please share with me.
The below is the IDoc xml which is coming from source side.
<?xml version="1.0" encoding="UTF-8" ?>
<DELVRY01>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>100</MANDT>
<DOCNUM>000000000999999</DOCNUM>
<DOCREL>1145</DOCREL>
<STATUS>1</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>2</OUTMOD>
<IDOCTYP>DELVRY01</IDOCTYP>
<MESTYP>abcde</MESTYP>
<SNDPOR>efghi</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>LMNOP100</SNDPRN>
<RCVPOR>A000000023</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>TB</RCVPRN>
<CREDAT>20056556</CREDAT>
<CRETIM>183734</CRETIM>
<SERIAL>12345678</SERIAL>
</EDI_DC40>
<E1EDL20 SEGMENT="1">
<VBELN>006456451</VBELN>
<VSTEL>4656</VSTEL>
<VKORG>1665</VKORG>
<ABLAD>ABCDEDFJSDFDF</ABLAD>
<ROUTE>DFSDF</ROUTE>
<VSBED>08</VSBED>
<BTGEW>3.000</BTGEW>
<NTGEW>333.000</NTGEW>
<GEWEI>NNN</GEWEI>
<VOLUM>450.190</VOLUM>
<VOLEH>DMBG55TERTQ</VOLEH>
<ANZPK>00000</ANZPK>
<XABLN>0001995346331</XABLN>
<LIFEX>N</LIFEX>
<E1EDL22 SEGMENT="1">
<VSTEL_BEZ>ABCDEFGHIIJFLD</VSTEL_BEZ>
<VKORG_BEZ>SDFKJSDFSDF</VKORG_BEZ>
<ROUTE_BEZ>FSDNFKSDJFKJASDKFJSDJFL</ROUTE_BEZ>
<VSBED_BEZ>FNSDKFSD,F,MSDF,</VSBED_BEZ>
</E1EDL22>
<E1EDL21 SEGMENT="1">
<KDGRP>10545</KDGRP>
<BEROT>teGHGHst FGHHFGHXI </BEROT>
<TRAGR>0001</TRAGR>
<E1EDL23 SEGMENT="1">
<LFART_BEZ>Outbound delivery</LFART_BEZ>
<KDGRP_BEZ>LPHG Wholesale</KDGRP_BEZ>
<TRAGR_BEZ>On HHFH</TRAGR_BEZ>
</E1EDL23>
</E1EDL21>
<E1EDL18 SEGMENT="1">
<QUALF>ORI</QUALF>
</E1EDL18>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>AG</PARTNER_Q>
<PARTNER_ID>00000GHF12889</PARTNER_ID>
<LANGUAGE>EN</LANGUAGE>
<FORMOFADDR>Makro SA</FORMOFADDR>
<TELEPHONE1>041 3600TERTE605-C...</TELEPHONE1>
<TELEFAX>041 36006TRT47</TELEFAX>
<COUNTRY1>ZHFGHA</COUNTRY1>
<REGION>EHGHC</REGION>
<E1ADRE1 SEGMENT="1">
<EXTEND_Q>100</EXTEND_Q>
<EXTEND_D>6HG15FGHFG05006416</EXTEND_D>
</E1ADRE1>
</E1ADRM1>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>WE</PARTNER_Q>
<PARTNER_ID>00000178E87T</PARTNER_ID>
<LANGUAGE>EN</LANGUAGE>
<FORMOFADDR>Makro SA</FORMOFADDR>
<NAME1>Makro Port Elizabeth Br 14</NAME1>
<NAME3>t/a Makro SA</NAME3>
<STREET1>CDFJSDLFJLS d</STREET1>
<COUNTRY1>ZFSDFA</COUNTRY1>
<REGION>EFSDFC</REGION>
<E1ADRE1 SEGMENT="1">
<EXTEND_Q>100</EXTEND_Q>
<EXTEND_D>6001534453505006416</EXTEND_D>
</E1ADRE1>
</E1ADRM1>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>54OSP</PARTNER_Q>
<PARTNER_ID>404534501</PARTNER_ID>
<LANGUAGE>EN</LANGUAGE>
<COUNTRY1>Z5454A</COUNTRY1>
</E1ADRM1>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>OSO</PARTNER_Q>
<PARTNER_ID>1054400</PARTNER_ID>
<COUNTRY1>Z5453A</COUNTRY1>
</E1ADRM1>
<E1EDT13 SEGMENT="1">
<QUALF>006</QUALF>
<NTANF>2005455470706</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>2005453470706</NTEND>
<NTENZ>00053454000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00005340000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>003</QUALF>
<NTANF>20070706</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>200705345706</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000053455400</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>001</QUALF>
<NTANF>20070706</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>20070706</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>007</QUALF>
<NTANF>20070709</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>20070709</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>010</QUALF>
<NTANF>20070705</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>20705</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDL28 SEGMENT="1">
<ROUTE>ED545S1</ROUTE>
<DISTZ>0.000</DISTZ>
<E1EDL29 SEGMENT="1">
<ROUTE_BEZ>FKLSDJFLSJDFJSDFJLSDJFLKSD</ROUTE_BEZ>
</E1EDL29>
</E1EDL28>
<E1EDL24 SEGMENT="1">
<POSNR>000010</POSNR>
<MATNR>000000000000</MATNR>
<MATWA>000000000</MATWA>
<ARKTX>OmFDFS 2kg.</ARKTX>
<MATKL>FSD5345FSDFLAUND</MATKL>
<WERKS>10FDF40</WERKS>
<LGORT>01</LGORT>
<LFIMG>10545.000</LFIMG>
<VRKME>C54T</VRKME>
<LGMNG>10553545.000</LGMNG>
<MEINS>CT534555345545345</MEINS>
<NTGEW>1653454.000</NTGEW>
<BRGEW>181.000</BRGEW>
<GEWEI>KGM</GEWEI>
<VOLUM>450.190</VOLUM>
<VOLEH>DMQ</VOLEH>
<LADGR>0534543002</LADGR>
<TRAGR>0001</TRAGR>
<VKBUR>UF53401</VKBUR>
<VKGRP>160</VKGRP>
<VTWEG>00</VTWEG>
<SPART>00</SPART>
<GRKOR>000</GRKOR>
<EAN11>16001085031034</EAN11>
<POSEX>000000</POSEX>
<E1EDL25 SEGMENT="1">
<LGORT_BEZ>Main s53453453454tore</LGORT_BEZ>
<LADGR_BEZ>Forklift</LADGR_BEZ>
<TRAGR_BEZ>On pallets</TRAGR_BEZ>
<VKBUR_BEZ>Gener534534al Trade</VKBUR_BEZ>
<VKGRP_BEZ>RSM E534 Cape</VKGRP_BEZ>
<VTWEG_BEZ>FKLSDFKLS</VTWEG_BEZ>
<SPART_BEZ>FSDFSDFJoducts</SPART_BEZ>
</E1EDL25>
<E1EDL26 SEGMENT="1">
<PSTYV>TAN</PSTYV>
<MATKL>FGUND</MATKL>
<PRODH>0125VH</PRODH>
<UMVKZ>1</UMVKZ>
<UMVKN>1</UMVKN>
<KZTLF>B</KZTLF>
<UEBTO>0.0</UEBTO>
<UNTTO>0.0</UNTTO>
<KVGR1>Z4FDFSDFSD</KVGR1>
<KVGR2>TPS</KVGR2>
<E1EDL27 SEGMENT="1">
<PSTYV_BEZ>Standard Item</PSTYV_BEZ>
<PRODH_BEZ>OmoFFD Regular 8X2kg.</PRODH_BEZ>
<WERKS_BEZ>ConFSDFgella DC</WERKS_BEZ>
<KVGR1_BEZ>PE Cust Del</KVGR1_BEZ>
<KVGR2_BEZ>rd party sales</KVGR2_BEZ>
</E1EDL27>
</E1EDL26>
<E1EDL43 SEGMENT="1">
<QUALF>C</QUALF>
<BELNR>FDF</BELNR>
<POSNR>000010</POSNR>
<DATUM>FFSDF</DATUM>
</E1EDL43>
<E1EDL41 SEGMENT="1">
<QUALI>54</QUALI>
<BSTNR>test I Link</BSTNR>
<BSTDT>00000000</BSTDT>
<POSEX>000010</POSEX>
</E1EDL41>
</E1EDL24>
</E1EDL20>
</IDOC>
</DELVRY01>

duplicate blog

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.

Regarding Module Configuration of JMS Adapter

Hi,
Now i am working on IDoc to JMS interface, I am facing complexity in creating the structure in Module tab of Receiver JMS Adapter. Because the target system is expecting fixed length file so i should use the Local EJBs available in Module tab of Receiver JMS adapter and i need to pass the fieldFixedLegth parameters for all the nodes coming from DELVRY01 Idoc. I think creating structure for all the nodes in receiver jms adapter is so complex, If you are having any other alternatives, please share with me.
The below is the IDoc xml which is coming from source side.
<?xml version="1.0" encoding="UTF-8" ?>
<DELVRY01>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>100</MANDT>
<DOCNUM>000000000999999</DOCNUM>
<DOCREL>1145</DOCREL>
<STATUS>1</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>2</OUTMOD>
<IDOCTYP>DELVRY01</IDOCTYP>
<MESTYP>abcde</MESTYP>
<SNDPOR>efghi</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>LMNOP100</SNDPRN>
<RCVPOR>A000000023</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>TB</RCVPRN>
<CREDAT>20056556</CREDAT>
<CRETIM>183734</CRETIM>
<SERIAL>12345678</SERIAL>
</EDI_DC40>
<E1EDL20 SEGMENT="1">
<VBELN>006456451</VBELN>
<VSTEL>4656</VSTEL>
<VKORG>1665</VKORG>
<ABLAD>ABCDEDFJSDFDF</ABLAD>
<ROUTE>DFSDF</ROUTE>
<VSBED>08</VSBED>
<BTGEW>3.000</BTGEW>
<NTGEW>333.000</NTGEW>
<GEWEI>NNN</GEWEI>
<VOLUM>450.190</VOLUM>
<VOLEH>DMBG55TERTQ</VOLEH>
<ANZPK>00000</ANZPK>
<XABLN>0001995346331</XABLN>
<LIFEX>N</LIFEX>
<E1EDL22 SEGMENT="1">
<VSTEL_BEZ>ABCDEFGHIIJFLD</VSTEL_BEZ>
<VKORG_BEZ>SDFKJSDFSDF</VKORG_BEZ>
<ROUTE_BEZ>FSDNFKSDJFKJASDKFJSDJFL</ROUTE_BEZ>
<VSBED_BEZ>FNSDKFSD,F,MSDF,</VSBED_BEZ>
</E1EDL22>
<E1EDL21 SEGMENT="1">
<KDGRP>10545</KDGRP>
<BEROT>teGHGHst FGHHFGHXI </BEROT>
<TRAGR>0001</TRAGR>
<E1EDL23 SEGMENT="1">
<LFART_BEZ>Outbound delivery</LFART_BEZ>
<KDGRP_BEZ>LPHG Wholesale</KDGRP_BEZ>
<TRAGR_BEZ>On HHFH</TRAGR_BEZ>
</E1EDL23>
</E1EDL21>
<E1EDL18 SEGMENT="1">
<QUALF>ORI</QUALF>
</E1EDL18>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>AG</PARTNER_Q>
<PARTNER_ID>00000GHF12889</PARTNER_ID>
<LANGUAGE>EN</LANGUAGE>
<FORMOFADDR>Makro SA</FORMOFADDR>
<TELEPHONE1>041 3600TERTE605-C...</TELEPHONE1>
<TELEFAX>041 36006TRT47</TELEFAX>
<COUNTRY1>ZHFGHA</COUNTRY1>
<REGION>EHGHC</REGION>
<E1ADRE1 SEGMENT="1">
<EXTEND_Q>100</EXTEND_Q>
<EXTEND_D>6HG15FGHFG05006416</EXTEND_D>
</E1ADRE1>
</E1ADRM1>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>WE</PARTNER_Q>
<PARTNER_ID>00000178E87T</PARTNER_ID>
<LANGUAGE>EN</LANGUAGE>
<FORMOFADDR>Makro SA</FORMOFADDR>
<NAME1>Makro Port Elizabeth Br 14</NAME1>
<NAME3>t/a Makro SA</NAME3>
<STREET1>CDFJSDLFJLS d</STREET1>
<COUNTRY1>ZFSDFA</COUNTRY1>
<REGION>EFSDFC</REGION>
<E1ADRE1 SEGMENT="1">
<EXTEND_Q>100</EXTEND_Q>
<EXTEND_D>6001534453505006416</EXTEND_D>
</E1ADRE1>
</E1ADRM1>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>54OSP</PARTNER_Q>
<PARTNER_ID>404534501</PARTNER_ID>
<LANGUAGE>EN</LANGUAGE>
<COUNTRY1>Z5454A</COUNTRY1>
</E1ADRM1>
<E1ADRM1 SEGMENT="1">
<PARTNER_Q>OSO</PARTNER_Q>
<PARTNER_ID>1054400</PARTNER_ID>
<COUNTRY1>Z5453A</COUNTRY1>
</E1ADRM1>
<E1EDT13 SEGMENT="1">
<QUALF>006</QUALF>
<NTANF>2005455470706</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>2005453470706</NTEND>
<NTENZ>00053454000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00005340000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>003</QUALF>
<NTANF>20070706</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>200705345706</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000053455400</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>001</QUALF>
<NTANF>20070706</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>20070706</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>007</QUALF>
<NTANF>20070709</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>20070709</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDT13 SEGMENT="1">
<QUALF>010</QUALF>
<NTANF>20070705</NTANF>
<NTANZ>000000</NTANZ>
<NTEND>20705</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
<E1EDL28 SEGMENT="1">
<ROUTE>ED545S1</ROUTE>
<DISTZ>0.000</DISTZ>
<E1EDL29 SEGMENT="1">
<ROUTE_BEZ>FKLSDJFLSJDFJSDFJLSDJFLKSD</ROUTE_BEZ>
</E1EDL29>
</E1EDL28>
<E1EDL24 SEGMENT="1">
<POSNR>000010</POSNR>
<MATNR>000000000000</MATNR>
<MATWA>000000000</MATWA>
<ARKTX>OmFDFS 2kg.</ARKTX>
<MATKL>FSD5345FSDFLAUND</MATKL>
<WERKS>10FDF40</WERKS>
<LGORT>01</LGORT>
<LFIMG>10545.000</LFIMG>
<VRKME>C54T</VRKME>
<LGMNG>10553545.000</LGMNG>
<MEINS>CT534555345545345</MEINS>
<NTGEW>1653454.000</NTGEW>
<BRGEW>181.000</BRGEW>
<GEWEI>KGM</GEWEI>
<VOLUM>450.190</VOLUM>
<VOLEH>DMQ</VOLEH>
<LADGR>0534543002</LADGR>
<TRAGR>0001</TRAGR>
<VKBUR>UF53401</VKBUR>
<VKGRP>160</VKGRP>
<VTWEG>00</VTWEG>
<SPART>00</SPART>
<GRKOR>000</GRKOR>
<EAN11>16001085031034</EAN11>
<POSEX>000000</POSEX>
<E1EDL25 SEGMENT="1">
<LGORT_BEZ>Main s53453453454tore</LGORT_BEZ>
<LADGR_BEZ>Forklift</LADGR_BEZ>
<TRAGR_BEZ>On pallets</TRAGR_BEZ>
<VKBUR_BEZ>Gener534534al Trade</VKBUR_BEZ>
<VKGRP_BEZ>RSM E534 Cape</VKGRP_BEZ>
<VTWEG_BEZ>FKLSDFKLS</VTWEG_BEZ>
<SPART_BEZ>FSDFSDFJoducts</SPART_BEZ>
</E1EDL25>
<E1EDL26 SEGMENT="1">
<PSTYV>TAN</PSTYV>
<MATKL>FGUND</MATKL>
<PRODH>0125VH</PRODH>
<UMVKZ>1</UMVKZ>
<UMVKN>1</UMVKN>
<KZTLF>B</KZTLF>
<UEBTO>0.0</UEBTO>
<UNTTO>0.0</UNTTO>
<KVGR1>Z4FDFSDFSD</KVGR1>
<KVGR2>TPS</KVGR2>
<E1EDL27 SEGMENT="1">
<PSTYV_BEZ>Standard Item</PSTYV_BEZ>
<PRODH_BEZ>OmoFFD Regular 8X2kg.</PRODH_BEZ>
<WERKS_BEZ>ConFSDFgella DC</WERKS_BEZ>
<KVGR1_BEZ>PE Cust Del</KVGR1_BEZ>
<KVGR2_BEZ>rd party sales</KVGR2_BEZ>
</E1EDL27>
</E1EDL26>
<E1EDL43 SEGMENT="1">
<QUALF>C</QUALF>
<BELNR>FDF</BELNR>
<POSNR>000010</POSNR>
<DATUM>FFSDF</DATUM>
</E1EDL43>
<E1EDL41 SEGMENT="1">
<QUALI>54</QUALI>
<BSTNR>test I Link</BSTNR>
<BSTDT>00000000</BSTDT>
<POSEX>000010</POSEX>
</E1EDL41>
</E1EDL24>
</E1EDL20>
</IDOC>
</DELVRY01>

not related

Content Conversion module in JMS Adapter - MessageTransformBean

Hi All,
We are using Content Conversion module using MessageTransformBean in JMS adapter to read a flat file from MQ Queue.It works fine and the file is getting picked and successfully converted into a xml structure in XI.
The flat file is multiple line file with each line as one xml record.But the xml structure after conversion has only one record in it.So we end up getting multiple messages each with one record instead of ONE xml structure with multiple records in it.
Could I know why I am not getting multiple records in one xml structure as expected.
Do I need to change xml.structureTitle as MyTitle,* or should I put something endSeparator like we do in File Content Conversion.
Any Help appreciated.
Thanks,
V
Edited by: CollinsV on Aug 9, 2010 6:28 AM
Edited by: CollinsV on Aug 9, 2010 6:36 AM
Edited by: CollinsV on Aug 9, 2010 6:38 AM
Edited by: CollinsV on Aug 9, 2010 6:39 AM
Edited by: CollinsV on Aug 9, 2010 6:56 AM

Thanks Shabarish .I did follow the same document , but the xml is not converted as multiple records in it .we are getting only one xml message for each record in the file .
The xml structure we are getting :
<ns:MyDocument xmlns:ns="http://xi.com/test">
<MyTitle>
<field-name1>111</field-name1>
<field-name2>222</field-name2>
<field-name3>333</field-name3>
</MyTitle>
</ns:MyDocument>
We need onle one xml message instead as below.
<ns:MyDocument xmlns:ns="http://xi.com/test">
<MyTitle>
<field-name1>AAA</field-name1>
<field-name2>BBB</field-name2>
<field-name3>CCC</field-name3>
</MyTitle>
<MyTitle>
<field-name1>111</field-name1>
<field-name2>222</field-name2>
<field-name3>333</field-name3>
</MyTitle>
</ns:MyDocument>
Any Help ...
Thanks
V

Complex XML to Plain in JMS adapter "Content conversion module"

Hi!
I have read the document on "How To use the content conversion module with XI3.0 J2EE JMS Adapter", and it says only SimpleXML can be converted in the receiver channel.
I had hoped for a solution at least as good as in the File/ftp adapter, where complex XML can be transformed to files.
Are there plans to include complex XML conversion in the JMS adapter?
I can not use the file adapter as I need to change the file name and destination, and that can not be done by adding own module to its single module.
Any idea how I can achieve what I want?
To only way I can find, is to create a file using the file/ftp adapter, and then pick it up again and treat all the lines as the same structure (one row = one xml field). Then output this new xml message to file, using the JMS adapter and add any modules with name and destination determination.
Appreciate any help!
Regards,
Oeystein Emhjellen

Hello,
Have you tried to use an XSLT mapping within the IE?
I have, at one customer site, created a XSLT message mapping which converts the XML to a fixed length ASCII file format. I than added the XSLT message mapping as a second mapping step on the interface mapping.
In this case I was able to publish a fairly complex fixed length file format to MQ Series via the JMS adapter.
/Johan

JMS content conversion adapter module

Hi All,
In JMS Content conversion module Xml2Plain how do u put two new lines 'nl'.
I am using localejbs/AF_Modules/MessageTransformBean in adapter module.
If I put xml.record.fieldSeparator in parameter name and in parameter value if I put one 'nl' it gives me one new line. Now I require two new lines in my output text so I put 'nl' 'nl' in parameter value but it takes only one new line.
e.g
Vivek
mumbai
India
John
Delhi
India
Now I want the output as:
Vivek
mumbai
India
John
Delhi
India
Thanks in advance.
ravijeet

try,
xml.record.fieldSeparator '0x0D''0x0D'
or
xml.record.fieldSeparator '0x0A''0x0A'

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 Module

Similar Messages

Maybe you are looking for