Append in Receiver JMS

Hi Friends,
Is there any feature in Receiver JMS adapters for append.. like Rcvr file adpater?
And also.. is jMS adapter flexible enough like FILE adpater.. i mean to say.. is it possible for JMS adapter to do complex content conversions...
thanks in advance
Biplab

Hi,
For file content conversion, you can use StrictPlain2XML adapter module in the receiver JMS adapater. Refer to http://help.sap.com/saphelp_nw04/helpdata/en/44/748d595dab6fb5e10000000a155369/content.htm
Regards,
Ratan

Similar Messages

  • How to pass dynamic filename to Receiver JMS channel

    Hi experts,
    I want to pass the dynamic filename to receiver JMS message Properties.
    for example
    I am passing directory name via adapter module AF_Modules/DynamicConfigurationBean with key and value combination like below. How to pass dynamic filename value to a dynamic property ( say DCJMSMessageProperty1)
    eg.
    key.0 - >insert http://sap.com/xi/XI/System/JMS DCJMSMessageProperty0
    value.0 - >  testdirectory ( which is static value)
    Note: Im have not created any ESR object . i just have to bypass the file to a jms queue. I have used AAE integrated configuration scenario ( file to jms )
    Regards,
    Balaji
    Edited by: Balaji Pichaimuthu on Jan 27, 2011 4:45 PM
    Edited by: Balaji Pichaimuthu on Jan 27, 2011 4:46 PM

    Already given link for the dynamic configuration code snippet in the earlier reply... Below is the code snippet
    Note: Use Adapter Specific Message Attributes for the target Communication Channel(CC).Check the indicator for filename in the advanced tab of CC
    //UDF code
    String filename="";
    String NameSpace = "http:/"+"/sap.com/xi/XI/System/JMS";
    try{
          DynamicConfiguration conf = (DynamicConfiguration) param.get(
            StreamTransformationConstants.DYNAMIC_CONFIGURATION);
          DynamicConfigurationKey key  =  DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/File",   "FileName");
           // read filename value
           filename = conf.get(key);     
          // So far we extracted filename value .. now do your logic  something like this...
          DynamicConfigurationKey key2 = DynamicConfigurationKey.create(NameSpace,"yourjmsvalue goes here");
           conf.put(key2,filename);
         } catch(Exception e){

  • 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

  • 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.

  • 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 it’s 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

  • File to JMS Scenario - Error is Receiver JMS Adapter

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

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

  • JMS Queue Vs JMS replyTo Queue name for Receiver JMS channel.

    HI,
    I am working with receiver JMS adapter and using the protocol WbeSphereMQ JMS provider.
    Here I could not able to figure out the difference between the following parameter.
    Target tab JMS Queue  and Processing tab-JMS replyTo Queue name.
    I tries the find the same in help.sdn.com but here also not able to find correct information .
    for Processing tab -JMS replyTo Queue name Parameter it is written that "Specify the name of the queue to which the responses are to be sent."
    But what is the use of Target tab JMS Queue Parameter. No information is given against this parameter.
    http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm
    regards,
    Navneet.

    the initial JMS Queue is the queue you will connect too.
    i guess SAP felt an explanation to that was not required....
    SAP does not even bother to explain it here in the specific link to JMS-Provider-Specific Settings (for Webshpere although it does for SonicMQ!).
    http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/frameset.htm
    I do not use the "ReplyTo" in my current scenarios.

  • 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).

  • JMS ReplyTo Queue Name parameter in the receiver JMS communication channel

    Hi All,
    Can any please explain the use of JMS ReplyTo Queue Name parameter in the receiver JMS communication channel?
    Thanks
    Karthik.

    Hi karthik,
    JMS ReplyTo Queue Name parameter  is used for Specify the name of the queue to which the responses are to be sent.
    Thanks
    Govind.

  • Receiver JMS ( websphere MQ ) error  - No transition found from state:ERROR

    Hi all
    we are using JMS adapter to connect to the Queue manager . whenever the queue manager restarts , the messages is not getting thru and it is struck in the adapter engine with status " not to be delivered "
    i am getting error in receiver communication channel audit log....its showing
    *MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_XXXXXXXXX:15fa03eb9fd837849906f512610314c4*
    note : already i have gone thur many forum  and nothing helps.
    Thanks in advance
    Faheem

    If you are using the FCC then this could be because of that. What is the connection status with MQ? Are there any connection errors with MQ.
    If you are using FCC in your Receiver JMS channel then just to confirm, first remove the FCC configuration and try to send a xml file. If the xml file goes in successfully then the problem is in your FCC configuration.

  • CorrelationId in receiver JMS adapter.

    hi to all,
    i need to send the correltionId in the message header of a receiver jms adapter.
    which parameter i need to specify?
    i've cheked the flag "set the additional JMS parameters...." as the documentation says: DCJMSCorreleationID with value 0001.
    but nothing change in the message header.
    thanks in advance
    Claudio.

    <i>here is a new parameter in  JMS adapter  now. There is an option of saving the JMS correlation ID of the request in the receiver JMS adapter. In the sender adapter, one can then set the XI conversation ID to the saved JMS correlation ID of the request. This makes the additional parameters that were required in previous Support Packages obsolete. However, the configuration settings that were made prior to SP7 are still valid.</i>
    From
    /people/kan.th/blog/2007/02/05/exploring-jms-and-sap-xi-jms-adaper
    Also this would b helpful
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8060448a-e56e-2910-f588-9af459e7ce21
    <i>[Reward if helpful]</i>
    Regards,
    Prateek

  • EDI Idoc -- Receiver JMS Adapter.

    Hi,
    I'm facing this issue from few days.
    Sender is EDI Idoc and contains header and Footer.
    This is placed in the application server of SAP system.
    From there xi picks the EDI Idoc and sends to JMS server.
    Facing problem on the receiver JMS Adapter.
    Find the error message.
    "Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_RCV_DEVWR0000000:165b1638fd823a8f822f0db8a9b1d488"
    I have provoded the "dict" and "doc" value also.
    Pls suggest.
    Thanks in advance,
    Jeevan.

    Hi Guys,
    There could be some problem while deploying the libraries. Check out the thread No transition found from state: STARTING
    Thanks,
    PP

  • Receiver JMS Configuration

    Hi Friends,
    I am configuring the receiver JMS adapter-
    1.In the JMS Settings section there is a option called "JMS ReplyTo Queue Name". I am not sure about the significance of it.
    2.Also let me know whether it is mandatory to fill?
    I have seen few blogs but nothing discussed on this point.
    Regards,
    Suresh.

    Suresh,
    Its not mandatory and its the queue where responses will be send. Please check the settings here:
    http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
    Its worth looking at this blog for some help on JMS:
    /people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
    Regards,
    ---Satish

  • Receiver JMS adapter content conversion

    Hi All,
    Can anyone provide me guidelines on how to do content conversion for the receiver JMS adapter??
    Thx
    Navin

    Hi,
    Based on your structure , you need to configure the JMS CC parameters.
    see the below link
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
    regards
    Chilla

Maybe you are looking for