Receiver JMS adapter issue in PI 7.1

Hi All,
We are using JMS receiver adapter for one of our scenarios. I'm facing different type of issue in production system
Issues:
If the channel is functioning the messages are successfully delivering to end system. If there are NO messages for long time the channel is not sending any message to end system and messages are getting failed in PI.
If i STOP and START the channel after few minutes channel able to deliver the messages.
I'm not not able to figure out where the issue is causing.
Please assist me to get ride of this issue.
Thanks in advance
- VR

Hello Rajesh and all,
Below is the error message i'm receiving. This issue is happens when there is no message flow for few hours and when a new message comes adapter channel in RWB through below error message.
Please assist with  inputs
Message processing failed. Cause:com.sap.engine.interfaces.messaging.api.exception.MessagingException:Connector for ConnectionProfile of Channel:IN_JMS_xxxx
node:xxxx havingobject id:xxxxxxx encountered error:MQJMSxxx:an internal error has occured. Please contact your system administrator. Detail: com.ibm.mqservices.MQInternalException:MQJE001:
An MQException occurred:Completion Code 2,Reason 2195 MQJE046:Unsupported codeset:0 in sending to destination queue:///xxxxxx.QUEUE?targetClient=1, the message message:JMS Message class:jms_txt JMSType: null
JMSDeliveryMode:2 JMSExpiration:0 JMSPriority: 4 JMSMessageID:  null JMSTimestamp:  0

Similar Messages

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

  • Jms adapter issue

    PI 7.31 is getting issue while connecting to Webshere MQ version 6.0.2.10.
    The error in JMS sender communication channel is - "Error connecting due to missing class com.ibm.mq.jms.MQQueueConnectionFactory. Please ensure all resources are present in JMS provider library : com.sap.aii.adapter.lib.sda"
    Few weeks back, MQ jar files were deployed by Basis.
    I have attached jar file content. Do we have to deploy different jar files,the jar files are of websphere mq 6.0.2.10.
    They were deployed on com.sap.aii.adapter.lib.sda
    rgds

    Hi ,
    Go through below links once.
    Receiver JMS Adapter Communication channel Error
    JMS inbound and outbound queue
    Regards
    Venkat

  • 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

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

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

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

  • 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

  • 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

  • Converting QoS from EO to EOIO in Receiver JMS Adapter

    Hello All -
    We are currently working with SAP XI 3.0 SP12. Our scenario is something like this:
    IDoc -> XI (BPM) -> JMS Adapter
    The BPM splits up the incoming IDoc into multiple JMS messages.
    The problem is that when the BPM sends the message to the JMS adapter the QoS changes from EOIO to EO. This essentially means that when the messages are written to the JMS Queues, there is no gurantee that they would be written in exactly the same order in which they are produced.
    The requirement is to write the messages in exactly the same order in the target queues.
    One solution is to capture the transport level acknoledgements and then send the next message from the BPM only on the receipt of the acknoledgement which takes a lot of time.
    Is there any other mechanism to ensure the messages going out in an EOIO fashion.
    Ashish

    Its like this , i ve file -> bpm -> idoc scenario. 've configured EOIO as the QOS for both adapters. file adapter is configured to pick up a pattern , say *.abc.
    The picking option is "By Date". Say there are 5 files in the directory before a particular polling interval which has about 5 sec time delay b/w them in their timestamp.
    Now the file adpater picks the files in order , delivers it to ccBPM, i can see 5 diff ccBPM instances(diff workitem IDs).
    Say, the third file has less data , the transformation happens faster in the 3rd ccBPM instance and so it delivers it to the idoc adapter vefore the 1st or 2nd one completes. So my order is lost.
    Now , i tried setting "transport ack" in send step , but didnt help.Is there any other specific setting to be done ?
    Thanks
    Saravana

  • Receiver Idoc adapter - issue

    Hi,
    I need to send an IDoc (CRMXIF_ORDER_SAVE_M01) to SAP CRM. The trouble occur when having/wanting to use/send only the segments that apply to release 620.
    In order to do that I have in my receiver IDoc adapter specified the value '620' in the Segment Version part.
    As soon as having done this my IDocs fail in the adapter giving me the following error:
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>Segment 'E101CRMXIF_ACTIVITY_X', segmentnumber '000001' not correct in structure CRMXIF_ORDER_SAVE_M01</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: Segment 'E101CRMXIF_ACTIVITY_X', segmentnumber '000001' not correct in structure CRMXIF_ORDER_SAVE_M01</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    The segment specified in the above corresponds to the very fist sub-segment to the main segment (BUSTRANS). So if removing that segment the error jumps to the next segment (which would then be the first sub-segment).
    Should be noted that I have no trouble sending IDocs if I've either not specified a Segment version (meaning latest version is automatically used) or if I explicitly request the latest by entering the latest segment release (700 in my case).
    <Trace level="1" type="T">Convert one IDoc</Trace>
      <Trace level="2" type="T">Convert Control Record</Trace>
      <Trace level="2" type="T">Convert Data Records</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_BUSTRANS</Trace>
      <Trace level="2" type="T">Ignore unknown Segment E101CRMXIF_BUSTRANS</Trace>
      <Trace level="2" type="T">Ignore segment field: APPL_SNAME</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_TASK</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_GUID</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_ID</Trace>
      <Trace level="2" type="T">Ignore segment field: PROCESS_TYPE</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_TYPE</Trace>
      <Trace level="2" type="T">Ignore segment field: POSTING_DATE</Trace>
      <Trace level="2" type="T">Ignore segment field: DESCR_LANGUAGE</Trace>
      <Trace level="2" type="T">Ignore segment field: DESCR_LANGUAGE_ISO</Trace>
      <Trace level="2" type="T">Ignore segment field: LOGICAL_SYSTEM</Trace>
      <Trace level="2" type="T">Ignore segment field: CRM_RELEASE</Trace>
      <Trace level="2" type="T">Ignore segment field: CLIENT</Trace>
      <Trace level="2" type="T">Ignore segment field: CREATED_AT</Trace>
      <Trace level="2" type="T">Ignore segment field: CREATED_BY</Trace>
      <Trace level="2" type="T">Ignore segment field: CHANGED_AT</Trace>
      <Trace level="2" type="T">Ignore segment field: CHANGED_BY</Trace>
      <Trace level="2" type="T">Ignore segment field: LOCAL_TIMEZONE</Trace>
      <Trace level="2" type="T">Ignore segment field: OBJECT_ID_OK</Trace>
      <Trace level="2" type="T">Ignore segment field: HIGHEST_ITEM_NO</Trace>
      <Trace level="2" type="T">Ignore segment field: CRM_CHANGED_AT</Trace>
      <Trace level="2" type="T">Ignore segment field: CALC_SCHEMA</Trace>
      <Trace level="2" type="T">Ignore segment field: SCENARIO</Trace>
      <Trace level="2" type="T">Ignore segment field: VALID_FROM_EXT</Trace>
      <Trace level="2" type="T">Ignore segment field: VERIFY_DATE</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ACTIVITY_X</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ACTIVITY</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ADDRESS</Trace>
      <Trace level="3" type="T">Segment= E103CRMXIF_ADDRESS</Trace>
      <Trace level="3" type="T">Segment= E107CRMXIF_ADDRESS</Trace>
      <Trace level="2" type="T">Ignore unknown Segment E107CRMXIF_ADDRESS</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ADDRESS_F</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ACT_REASON</Trace>
      <Trace level="3" type="T">Segment= E101CRMXIF_ACT_REASON_F</Trace>
    Hope someone can help me so that I can succesfully limit the segment version used when sending Idocs.
    Best regards,
    Daniel

    Hi,
    Thanks for your quick reply.
    The funny thing is that even if a try to post the exact same idoc (except for the EDI part) that I have received from CRM it still fails in XI with the before mentioned error.
    But to answer your questions:
    1. I'm not using java mapping but traditional message mapping (meta-data are up-to-date and structure is newly loaded).
    2. No blank segments are being created
    3. All segments have value 1 or blank (using blank works fine for me, that is when not trying to limit Segment version. But using 1 makes no difference)
    Best Regards,
    Daniel

  • How to send alert when receiver JMS adapter fails? Please help!

    Hi experts,
       I have the following Asynchronous scenario:
       SAP R/3 -
    >IDOC----->XI>JMS--->BizTalk.
       I am sending IDOC from a given SAP R/3 system to XI. XI then sends the same to BizTalk via JMS adapter. In SXMB_MONI the message is successfully processed as it shows checked flag. But if I see the JMS communication channel status in runtime workbench then there it shows error saying JMS queue user id or password not found.
    How to send this JMS adapter error as alert?
    I also tried configuring alert rule in runtime workbench but still it does not trigger any error.
    I have also verified the alert category and everything is fine with that.
    What could be the problem? How can I send an alert when an Async adapter fails?
    Thanks & Regards,
    Gopal

    Hi! GOPAL,
    Once make sure whther all the below mentioned steps are configured correctly or not ok
    1: First make sure whether you are working on SAP XI or PI 7.1
               a) If XI you need to create Alerts (ALert Category) in CCMS ABAP stack in the
                        Tcode. ALRTCATDEF
               b) Open the alert category/classification definition environment (transaction ALRTCATDEF).
         ensure you are in change mode.
               c) In the group box with the alert classifications, right-click All classifications to open the   
                    context menu, and choose Create.
               d) Under Classification, enter a name for the classification.
               e) Under Description, enter a description of the classification.
               f)  Save your entries.
               g) Then go to RWB-->Go to ALERT Configuation and ADD the RULES to your alert category gor 
         which created there in the abap stack.
    Note Suppose if you want those ALERTS to come to your MAIL then again go to ABAP STACK and go to Tcode.  ALRTCATDEF and select your alert category press FIxed Recepients and there give your SAP XI ID's then  u can see those alerts in RWB-->ALERT INBOX
    Suppoe if you want those to mail then ask the basis team to link your company mail or personal mail ID to your SAP ID.
    2. Supppose if you are working on PI 7.1 Server.
         Only difference is creating Alert Category...Here you can create your ALERT Classification I mean   
         alert caltegory in the ESR (Enterprise Service Repository )
         Software Component >S CVersion>NameSpace-->Alert Category.
         You can configure how u configure there in abap stack such as long and short text every thing 
          except Fixed Receipients you need to give that recepients there only in ABAP STACK.
          what ever ALERT CATEGORY you are creating will reflect there in the ABAP STACK
         even you can Use these alerts Category in BPM --> CONTROL STEP -->Configure here in this step
    You can also reach alerts like this.
    NOTE  Most Important point is You can also view your mails or Alerts in the T Code:: SOST.
    Regards:
    Amar Srinivas ELi

  • Receiver RFC adapter issue! Please help!

    Hi Experts,
       I have 4 XI interfaces. All of these are Webservice to RFC scenarios. Moreover all of them are synchronous.
      Request message: Webservice (SOAP Adapter) ---> XI -
    > RFc Adapter ---> ECC Function modules
      Response message: Webservice (SOAP Adapter) <- XI < RFc Adapter <- ECC Function modules
    As you can see above, external system calls XI web service via SOAP Adapter. The input data is then sent from SOAP Adapter to RFC adapter to call RFC function module in the receiving side.  The receiving system is SAP ECC system.
    The receiver ECC system has two instances. For example SP0 ad SP1. 
    In the receiver determination step we have maintained a rule such that if the Plant value in the input message is XYZ then send data to SP0. But if the plant value in ABC then send data to SP1.
    This Conditional rule is working fine.
    However we are getting couple of issues with only one instance of ECC (SP0).
    1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-001cc495e48a(INBOUND) expired
    2. NO_MAPPINGPROGRAM_FOUND. Mapping program is not available in runtime cache: Object ID C2B41FFDFD4635BAB1E41AE53C0D10CE Software Component 5394F420463611DAC1CFFBBC0A01BC16
    3. com.sap.engine.interfaces.messaging.api.exception.MessagingException: No response available
    The above listed errors are generated occasionally. Sometimes no errors are generated even when the same input data is sent again and message is successfully processed.
    I have verified the input data and everything is OK with that.
    Mapping object is available in XI and cache was also refreshed. I additionally reactivated the objects in XI as well.
    So what could be the real root cause of this? Please help!
    Thanks
    Gopal

    1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-
    001cc495e48a(INBOUND) expired
    Check the Timeout parameter of your adapter.....for requests which expire with this error confirm from the SAP end that the message processing is done well within the Timeout period of the adapter.
    Refer this note for more info on the above occuring error and the possible way to avoid it: https://service.sap.com/sap/support/notes/791379
    Update:
    Even problem 3 seems to be occuring due to insufficient Timeout specified for the adapter.....if possible try increasing the Timeout in VA
    Regards,
    Abhishek.
    Edited by: abhishek salvi on Oct 6, 2009 1:42 PM

Maybe you are looking for

  • Goods Recipt againest KANBAN SumJC

    Hello Team , Im facing one error while doing the Goods receipt for KANBAN Summarized JIT call. We received the Summarized JIT call for KANBAN and trying to post the goods receipt using transaction code : PJWE and BORGR_C. The system is giving error t

  • Image not displayed in WebHelp output

    Hi, I've updated two images in my project file (image92.gif and image93.gif) with new images. In the source file, everything looks great. In my output, I see empty spots where these images should be. In the source file directory, the images do appear

  • Password for Airport Wireless Network

    I have a wireless connection with a third party router (dlink). I also have an AE that I use solely to run itunes through my stereo system. I DO NOT use the AE to connect to the internet. I'm not concerned about a password for the AE, but I want to p

  • The smartcover has damaged my iPad, is Apple liable for this?

    The apple smartcover I purchased with my iPad has over the past few months been creating a dent where the magnet goes. It looks like someone has drilled into it slightly. The aluminium that has been taken off the iPad has been penetrated into the sma

  • HR_PERSON_EXTRA_INFO_API.create_person_extra_info

    Please tell me the table that is getting updated by HR_PERSON_EXTRA_INFO_API.create_person_extra_info.