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

Similar Messages

  • 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

  • How to configure the jms adapter

    hi all,
           i got some trouble trying to configure de JMS adapter, i 'd be glad if some colud give me a hand with this. i'am wordering if there is a complete document about this topic to help me out with de configuration.
    thk u all very much.
    Regards, Pablo

    Hi,
    The below URL will help you to understand what is JMS, how to configure and do a testing.
    http://learn-oraclesoa.blogspot.co.uk/2013/04/oracle-jms-adapter-tutorial.html
    Below will help you to configure the JNDI for JMS
    http://manojm-nair.blogspot.co.uk/2013/02/configuring-connection-jndis-for-jms_13.html
    Thanks,
    Vijay

  • Configuration of JMS  adapter Using WebSphereMQ

    Hi All
    I am trying Http to JMS scenario.
    I configured my JMS adapter as receiver
    Trasport protocol: Web sphereMQ JMS provider.
    Queue Connection Factory : com.ibm.mq.jms.MQQueueConnectionFactory
    Queue Java class : com.ibm.mq.jms.MQQueue
    IP address : 172.17.50.150Where I installed Web Sphere MQ
    In SXMB_MONI my http client sends msg without any error
    But In runtime work bench whn  I observe Adapter monitoring I got error as
    Receiver channel. Details: MQJMS2005: failed to create MQQueueManager for '172.17.50.150:QM_APPEL'
    PLZ ell me d coz
    Thanks

    Hi,
    for the configuration of a Websphere MQ JMS adapter, you will have to also give details like, Queue Manager Name, channel name, etc.
    Just check this link for the same,
    http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
    Provide all the correect details and it will hopefully work.
    Regards,
    Bhavesh

  • Configuration for JMS Adapter Sensor action and JMS Queue sensor action..!!

    Hi,
    Id like my BPEL process to send an XML message to JMS on Websphere,I was able to do this through a JMS adapter.But I would more like to add sensors into my process which would really do the same thing - send an XML message to JMS Q.
    Now I understand that there are two ways to do this,JMS Queue and JMS Adapter - thorugh bpel sensor action.
    I am able to use JMS Queue and it works fine , but adds its own xml tags to the message,Is there any way I could send only my xml payload as a message to the queue??
    Also could any1 tell me what is the configuration for JMS Adapter sensor action?
    Any suggestions how do I go about it??

    Hey Anirudh,
    Thanx for the response :-)
    All these hold good when I have an AQ adaptor right,But the thing is I want to send a message to a 'JMS' queue with out actually using an adapter configuration wizard and everythng..So I resolved to JMS queue Sensor action..Heres the xml snippet from the sensorAction.xml files which is generated..
    <actions targetNamespace="http://xmlns.oracle.com/Test_JMS_Logging" xmlns="http://xmlns.oracle.com/bpel/sensor" xmlns:tns="http://xmlns.oracle.com/Test_JMS_Logging" xmlns:pc="http://xmlns.oracle.com/bpel/sensor">
    <action name="JMS_LogEntry" publishName="" publishType="JMSQueue" enabled="true" filter="" publishTarget="jms/L_Queue">
    <property name="JMSConnectionFactory">jms/L_QueueCF</property>
    <sensorName>ActivitySensor_JMS</sensorName>
    </action>
    </actions>
    This works grt and adds messages to the queue..But adds its own header info according to the sensor.xsd loacted at the Oracle_home\bpel\system\xmllib\ folder.
    Right now the XML message added to the Queue is:-
    <actionData xmlns="http://xmlns.oracle.com/bpel/sensor">
    <header>
    <sensor sensorName="ActivitySensor_JMS" classname="oracle.tip.pc.services.reports.dca.agents.BpelActivitySensorAgent" kind="activity" target="AddLEntr
    y" xmlns:pc="http://xmlns.oracle.com/bpel/sensor" xmlns:ns2="http://www.ulrhome.com/2008/10/L_Entry" xmlns:tns="http://xmlns.oracle.com/Test_JMS">
    <activityConfig evalTime="completion">
    <variable outputDataType="string" outputNamespace="http://www.w3.org/2001/XMLSchema" target="$WriteL_Produce_Message_InputVariable/L_Entry/ns2:L_Entry/ns2:LCName"/>
    </activityConfig>
    </sensor>
    <instanceId>950016</instanceId>
    <processName>Test_JMS</processName>
    <processRevision>v2009_04_15__40833</processRevision>
    <domain>default</domain>
    <timestamp>2009-04-15T11:21:23.596-04:00</timestamp>
    <midTierInstance>app01.ulrhome.com:9700</midTierInstance>
    </header>
    <payload>
    <activityData>
    <activityType>scope</activityType>
    <evalPoint>completion</evalPoint>
    <durationInSeconds>0.011</durationInSeconds>
    <duration>PT0.011S</duration>
    </activityData>
    <variableData>
    <dataType>12</dataType>
    <data>
    <ns0:LCName xmlns:ns0="LC_Test1http://www.ulrhome.com/2008/10/L_Entry">LC_Test1</ns0:LCName>
    </data>
    <queryName/>
    <target>$WriteL_Produce_Message_InputVariable/L_Entry/ns2:L_Entry/ns2:LCName</target>
    <updaterName>AddL_Entry</updaterName>
    <updaterType>scope</updaterType>
    </variableData>
    </payload>
    </actionData>
    My requirement is that I need to add a sensor to the BPEL process which posts 'Only my payload message to the JMS queue'..
    What I would want the message in the Queue to be is : -
    <data>
    <ns0:LCName xmlns:ns0="LC_Test1http://www.ulrhome.com/2008/10/L_Entry">LC_Test1</ns0:LCName>
    </data>
    Also while creating a Sensor action I get another option as JMS Adaptor,I am not sure of what value to type in this wizard..Heres what I keyed in..M sure this is not right..Cos it dosnt work :-)
    <action name="SensorAction_JMS" publishName="" publishType="JMSAdapter" enabled="true" filter="" publishTarget="jms/LoggingQueue">
    <property name="JMSConnectionName">Log</property>
    </action>
    </actions>
    Could any 1 tel me what values are the right values..And does JMS Adapter mean that I have to create a JMS Apator in the project and give that connection name as a Value..
    I am not finding sufficiant Documentation for 'JMS Adapter' so M clueless and right now any help will be appriciated :-)
    Regards,
    Akshatha.

  • How to configure an jms adapter to use ActiveMQ?

    Does anyone have an example of how to configure an jms adapter of oracle esb
    for third party JMS provider to use ActiveMQ?
    I had done something as follow:
    1、add activemq shared-library in $SOA_INSTANCE/config/service.xml
    2、config a jms adapter fro third party use paramter:
         java.naming.factory.initial     org.apache.activemq.jndi.ActiveMQInitialContextFactory
         java.naming.provider.url     tcp://10.20.30.26:61615
    but I got a error:ERRJMS_CONN_FAC_NOT_FOUND.
    Caused by: javax.naming.NameNotFoundException: org.apache.activemq.ActiveMQConnectionFactory
         at org.apache.activemq.jndi.ReadOnlyContext.lookup(ReadOnlyContext.java:225)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at oracle.tip.adapter.jms.JMS.JMSFactory.jndiLookup(JMSFactory.java:237)
         at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:138)
         ... 51 more
    what should I do? can someone give me a detail resolvent?

    I also had done as follows:
    1、add activemq shared-library to shared-library named "oracle.esb" in server.xml :
    <shared-library name="oracle.esb" version="10.1.3">
              <import-shared-library name="apache.activemq"/>
    </shared-library>
    2、add in $SOA_INSTANCE\j2ee\soa\application-deployments\default\JmsAdapter\oc4j-ra.xml
         <imported-shared-libraries>
              <import-shared-library name="apache.activemq"/>
         </imported-shared-libraries>

  • 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

  • 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

  • Store and Forward agent configuration in jms adapter - jdeveloper

    I am created the store and forward (SAF) agent in weblogic to communicate with another weblogic server.
    after creating it i tried to configure it in jms adapter wizard but i can't able see my SAF Queue there.
    so now how can i give payload to my SAF queue for testing it.
    Please provide any suggestions, i will provide with the points.
    Thanks,
    Ajay Athuluri

    So I don't know much of the details of AIA, and next to nothing of the pre-built integrations, so can't help you much there. However are you sure you've got all the requisite SAF configuration right? The JMS and SAF component hierarchies are a real rats' nest of trouble. This is a setup I've found to work:
    * SAF Agent, targeted to a managed server; needs to use the default filestore (ie when configuring it you don't specify one)
    * JMS Module containing:
         * SAF Remote Context, pointing at your remote WLS instance
         * JMS SubDeployment, targeted to the SAF Agent
         * Connection Factory, targeted at the managed server
         * SAF Imported Destination, targeted at the SubDeployment
         * Queue in the Imported Destination, with WLS and JNDI names set up so they're different in the sending domain and receiving domain
    The pre-built integrations will (probably) have the JNDI names you need to configure in the documentation.
    HTH!
    Paddy

  • QoS EOIO - How to Configure in JMS adapter?

    Hi there,
    In order to configure the JMS sender-adapter with EOIO QoS, I need to provide 2 "extra" parameters. These are
    1)Queue ID
    2)Processing J2EE Cluster Server (ClusterID)
    So far I was able to find out the name of the ClusterId in our system but for the Queue ID I still have some doubts.
    From the XI documentation I understand that for QoS EOIO , all messages share the same queue. They also say; <i>The "suffix" of this queue must be explicitly set in the application program by a <u>serialization context</u> before the client proxy is called.</i> What exactly is <i>serialization-context</i> in this context?
    Can someone provide me with a clear explanation which steps I need to follow in order to use the functionality of QoS EOIO? And if possible some example of the name of an EOIO queue?
    Thanks,
    R.

    Hi Roberto,
    For queue ID, you can specify any arbitrary queue ID for example, POQueue1, jayqueue or salesorder...
    It can be anything you want and no additional configuration is needed.  Just specify any name you like to use for queue ID and you are all set.
    Thanks,
    Jay

  • Login Module configuration for soap adapter ?

    Hi Guys,
    I have configured XISOAPAdapter for client certificate Authentication and i have created 1443 as the HTTPS port on the ABAP stack and defined this port in the instance profile.
    Under SSL provider i have selected 50101 as the HTTPS port and the user mapping to the certificate works fine and i was able to login directly.
    https://host:50101/XISOAPAdapter/MessageServlet - I was able to login with the user mapping to certifcate.
    but when i try https://host:1443/XISOAPAdapter/MessageServlet - it is asking for the basic password authentication and the automatic login with the certifcate is not working. Our customer will be using this url to send messages to soap adapter.
    under policy configurations for XISOAPAdapter, i have defined only clientcertificateloginmodule and define the rule as Rule1.getUserFrom=wholecert.
    any help or suggestions would be appreciated.
    Thanks,
    Srini

    Hi,
    We also experienced that limitation when a vendor is connecting to our XI SOAP Sender Adapter. It is asking for basic username/password. What we did was to create a Generic XI user with a password on it and use SSL authentication at the same time. Our Scenario was PI --> XI --> SAP R3, with the PI system using an HTTP RFC destination with a Basic Logon and Active SSL option to connect to the same system as yours https://host:portnumber/XISOAPAdapter/MessageServlet
    Let me know if this helped...
    Regards,

  • Query regarding durable subscribers in JMS Adapter (11g)

    Hi , I am facing some issue with using durable subscribers..
    I am doing a POC in which I have two consumers (consumer 1 and consumer 2) listening to a topic.
    On the server console, the monitor tab of the JMS topic shows number of consumers as 2 which is good.
    Also, when any message is put on the topic , BPEL processes for both consumers get triggered as expected.
    Now, I add durable subscriber ID as 123 to one of the consumers (consumer 1)
    After deploying the code, the count for the number of current consumers listening becomes 1.
    So I create a durable subscriber on the console with id as 123 after which the consumer count is back to 2.
    The issue however is that, now when I put a message on topic , only consumer 2 is triggered.
    The message for consumer 1 can be seen on the durable subscriber 123's page.
    My question is that, since the consumer is listening to the topic then why is the message going to the subscriber instead of creating instance ?
    I also tried following :
    1. created a new outbound connection pool in the resource adapter
    2. setting property FactoryProperties to value "ClientID=123"
    3. pointing the adapter connection factory to this new location
    but this is also not helping.
    Could anyone please help me out in this ?
    Thanks and Regards,
    Ketan

    did u have any luck? can u tell me steps

  • Dynamic configuration bean in JMS Adapter

    Hello Experts,
    My scenario is JMS(Active MQ) to File.Its just Passthrough scenario and no mapping involved.
    Filename will be coming in one of the JMS Property (say businessId) and I need to set this filename to file adapter.
    I have refered the stefan's blog and used the Dynamic configuration bean module in sender JMS adapter.
    getFilename key.1 write http://sap.com/xi/System/JMS DCJMSMessageProperty4
    getFilename value.1 module.filename
    setFilename key.1 read http://sap.com/xi/System/File FileName
    setFilename value.1 module.filename
    But required filename is not populated in the target File.Any other configuration is missing here?

    Hi Karthiga
    Did you set the ASMA properties in both your sender JMS channel and receiver File channel?
    For the JMS adapter, as shown below, you will need to enter the DCJMSMessageProperty4 into the table
    Configuring the Sender JMS Adapter - Configuring the JMS Adapter in the Integration Directory/PCK - SAP Library
    If you want to set additional JMS message attributes, select Specify Additional JMS Message Properties (Maximum of 10).
    In the table, enter the names of the JMS message properties whose values are to be included in the message header of the PI message.
    The technical names of the additional attributes are DCJMSMessageProperty0, DCJMSMessageProperty1, ..., DCJMSMessageProperty9.
    For the File adapter, you need to check the ASMA FileName attribute.
    Once you have this configured, in your message, you should be able to see that the value is in the DynamicConfiguration section of the SOAP header.
    Rgds
    Eng Swee

  • 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

  • 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<i>);
                                  n = xmldoc.createTextNode(values<i>);
                                  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

Maybe you are looking for