Problem in configuring JMS adapter

Hello,
My purpose is to send xml data from MQSeries to BW using XI. MQSereies is installed in XI server. For thah I am trying to configure JMS adpter for MQSeries in XI. I have successfully  deployed the necessary external drivers using SDM. I have configured the sender channel with the following parameters.
Adapter type: JMS
Transport Protocol :WEBsphereMQ(non-JMS)
Message protocol :JMS1.x
Queue connection factory java class:com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class: com.ibm.mq.jms.MQQueue
IP address: IP address of XI system.
Port: 1414
Queue manager name : MQ-manager-name_XI-system-name
Channel Name : reciever-channel-name_XI-system-name
JMS queue: postcard
Charecter set ID:
Transport/networkprotocol: TCP/IP
JMS-Compliant : WebsphereMQ(non-JMS)
But when I check it in adapter monitor JMS is shown as red.
When I go to Visual Administrator
      "cluster->server->services->monitoring->runtime->monitor tree->services->Connector Service" is white instead of green.
Can any one tell what could be the problem.
Regards,
Amith

Hi Vijaya,
In VA there is only option to stop or start JMS XI adapter.
I dont know where to activate JMS adapter in VA. It is already started in VA.
Regards,
Amith

Similar Messages

  • Configuring JMS adapter for a BPEL process which puts a msg in a Q of MQ

    Hi,
    I am trying to develop a BPEL process which picks up a message from a Q in Websphere MQ and puts that message in another Q of MQ after processing that.
    I have updated the oc4j-ra.xml with the following inputs:
    <connector-factory location="eis/MQSeries/Queue" connector-name="Jms Adapter">
              <config-property name="connectionFactoryLocation" value="com.ibm.mq.jms.MQQueueConnectionFactory"/>
              <config-property name="factoryProperties" value="QueueManager=TestManager;TransportType=1;Hostname=machine's ip address;Port=1414;Channel=channel name for connecting to client"/>
              <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
              <config-property name="isTopic" value="false"/>
              <config-property name="isTransacted" value="true"/>
              <config-property name="username" value="admin"/>
              <config-property name="password" value="welcome"/>
         </connector-factory>
    But while testing the BPEL process, I get the error:
    <remoteFault>
    <part name="code" >
    <code>null</code>
    </part>
    <part name="summary" >
    <summary>file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. ; nested exception is: ORABPEL-12511 Adapter Framework unable to create outbound JCA connection. file:/D:/OraBPELPM_2/integration/orabpel/domains/default/tmp/.bpel_MQMessaging_1.0.jar/Outbound.wsdl [ Produce_Message_ptt::Produce_Message(SourceEmployee) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141 ERRJMS_CONN_FAC_NOT_FOUND. Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor com.ibm.mq.jms.MQQueueConnectionFactory neither through JNDI nor instantiate it as a Java class Please examine the log file to determine the problem. Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console. </summary>
    </part>
    <part name="detail" >
    <detail>null</detail>
    </part>
    </remoteFault>
    Can anyone tell me what has gone wrong in setting the connection factory for the Q or what else I have to configure to sort out this problem?
    Thanks,
    Jayatu

    I am experiencing the exact same issue while configuring for Tibco EMS!!!
    I have also checked the oc4j-xa.xml file etc and I am also unable to find any guidance on the steps required from XML config files through to adapter wizard entries!

  • Configuring JMS adapter

    We have 3 instance of BPEL process manager - DEV, TEST and PROD. Once development completes in DEV instance, it is moved to TEST for testing and then to PROD.
    When the BPEL process is moved from one environment to another, we have to manully change the JMS adapter settings like IP address etc (3rd Party JMS Topic). This sometimes causes error due to human mistake.
    Is there any method by which we can maintain a seperate configuration/properties file wherein these details can be maintained and referenced in JMS adapter WSDL so that we need not change the settings of JMS adapter everytime we migrate from one env. to another?
    Regards

    Just to understand your problem a little better, say you have processes A and B that you promote b/w these 3 environments. Also, say A is a standalone service invokable by external clients; say B is a service that is invokable by an external client and called by A as well.
    Now, in this example, both A and B have web-service end points that change from one env to another.
    W.r.t process A's caller, it should know the correct endpoint to invoke the service. Now if there is just one external client that is switching b/w the various environments, it has the responsibility of making this switch b/w the various endpoints (dev to test to prod). Now if this external client is an Oracle BPEL process as well, refer to solution below.
    As far as process A's implementation goes, yes, it would have to change to invoke process B correctly. So, in dev, A should call B in dev; in stage/prod, A should call B in stage/prod. BPEL PM provides a solution to accomplish this via a customize ant task - refer to the section titled "Deploying to Multiple Environments with Different Configuration Values" in "Oracle® BPEL Process Manager Developer’s Guide 10g (10.1.3.1.0) B28981-03". Nothing changes for B across these three env as it is not invoking any other internal services.

  • Configuring JMS Adapter (AQJMStoDB)

    Hi All,
    Merry Christmas!
    I think I am reopening the below previous thread but I really am stuck.
    Re: Can ESB JMS adapter read and write from/to Oracle AQ
    I am trying to wrap up the AQJMStoDB example in
    Oracle® Application Server Adapters for Files, FTP, Databases, and Enterprise Messaging User’s Guide 10g Release 3 (10.1.3.1.0)...
    I completed all the necessary steps and when I execute the Send command I am getting the below error...
    C:\ESBSamples\AQJMStoDB\tools>java Send JMSDEMO_TOPIC
    OEMS.155 - simple JMS Send / JMS 1.02 / Database AQ / no JNDI
    Connection factory = oracle.jms.AQjmsTopicConnectionFactory@f72617
    Created connection = oracle.jms.AQjmsConnection@3bb2b8
    Created session = oracle.jms.AQjmsSession@c2ff5
    started connection
    Got topic = JMSUSER.JMSDEMO_TOPIC
    started session = oracle.jms.AQjmsSession@c2ff5
    destination: JMSUSER.JMSDEMO_TOPIC
    message :
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <db:InputParameters xmlns:db="http://xmlns.oracle.com/pcbpel/adapter/db/DBAPP/AD
    DEMPLOYEES/">
    <EMPS>
    <EMPS_ITEM>
    <FNAME>John</FNAME>
    <MIDDLE>W</MIDDLE>
    <LNAME>Doe</LNAME>
    <ADDR>
    <STREET>100 Oracle Parkway</STREET>
    <CITY>Redwood Shores</CITY>
    <STATE>CA</STATE>
    <ZIP>94065</ZIP>
    </ADDR>
    </EMPS_ITEM>
    </EMPS>
    </db:InputParameters>
    message was sent with ID=null
    Can you help me identify the problem.
    I am using XE database and jdk 1.4.12_16.
    Please let me know if you need more information on the setting and stuff.
    Thanks,
    Kalyan.

    Just to understand your problem a little better, say you have processes A and B that you promote b/w these 3 environments. Also, say A is a standalone service invokable by external clients; say B is a service that is invokable by an external client and called by A as well.
    Now, in this example, both A and B have web-service end points that change from one env to another.
    W.r.t process A's caller, it should know the correct endpoint to invoke the service. Now if there is just one external client that is switching b/w the various environments, it has the responsibility of making this switch b/w the various endpoints (dev to test to prod). Now if this external client is an Oracle BPEL process as well, refer to solution below.
    As far as process A's implementation goes, yes, it would have to change to invoke process B correctly. So, in dev, A should call B in dev; in stage/prod, A should call B in stage/prod. BPEL PM provides a solution to accomplish this via a customize ant task - refer to the section titled "Deploying to Multiple Environments with Different Configuration Values" in "Oracle® BPEL Process Manager Developer’s Guide 10g (10.1.3.1.0) B28981-03". Nothing changes for B across these three env as it is not invoking any other internal services.

  • Problem Encountered in JMS adapter using SEEBURGER module

    While testing the receiver JMS adapter for XML to EDI conversion using Seeburger module, I am facing errors.
    <b>1. The error encountered is</b> :
    Error while processing message '4720bc32-2dfc-03d8-0000-00000a2050d3';  detailed error description: java.lang.NullPointerException at com.sap.aii.adapter.jms.core.connector.SendContextImpl.send(SendContextImpl.java:43) ...
    <u>SEEBURGER BICXIADAPTER</u> --- Conversion of synchronous request from module chain ended with errors ---Error: [Error:ID=2061;LEVEL=1] XMLDocReader moveNext(): Cannot move to next trigger : Error in line 1: <u>XML file should begin with white spaces or <. (Found char :U(Hex :85</u>). DESCRIPTION: XMLDocReader Exception: Not able to move to next trigger [not specified] - trigger may not right set.
    <b>2. The targer PAYMUL xml is as follows</b> :
    ( At receiver channel, the above should be converted to EDI-Paymul using the Seeburger Module)
    <u>PAYMUL XML</u>
      <?xml version="1.0" encoding="UTF-8" ?>
    - <LIST>
    - <S_UNA>
      <D_DELIMITER>:+.? '</D_DELIMITER>
      </S_UNA>
    - <S_UNB>
    - <C_S001>
      <D_0001>UNOA</D_0001>
      <D_0002>2</D_0002>
      </C_S001>
    - <C_S002>
      <D_0004>SAPDM</D_0004>
      <D_0007>ZZ</D_0007>
      </C_S002>
    - <C_S003>
      <D_0010>000000000000</D_0010>
      <D_0007>55</D_0007>
      </C_S003>
    - <C_S004>
      <D_0017>070201</D_0017>
      <D_0019>1150</D_0019>
      </C_S004>
      <D_0020>01945678912345</D_0020>
    - <S_UNH>
      <D_0062>1</D_0062>
    - <C_S009>
      <D_0065>PAYMUL</D_0065>
      <D_0052>D</D_0052>
      <D_0054>96A</D_0054>
      <D_0051>UN</D_0051>
      <D_0057>FUN01G</D_0057>
      </C_S009>
    - <S_BGM>
    - <C_C002>
      <D_1001>452</D_1001>
      </C_C002>
      <D_1004>01945678912345</D_1004>
      <D_1225>9</D_1225>
      </S_BGM>
    - <S_DTM>
    - <C_C507>
      <D_2005>137</D_2005>
      <D_2380>20070201</D_2380>
      <D_2379>102</D_2379>
      </C_C507>
      </S_DTM>
    - <G_SSG4>
    - <S_LIN>
      <D_1082>1</D_1082>
    - <S_DTM>
    - <C_C507>
      <D_2005>203</D_2005>
      <D_2380>20070201</D_2380>
      <D_2379>102</D_2379>
      </C_C507>
      </S_DTM>
    - <S_RFF>
    - <C_C506>
      <D_1153>ACK</D_1153>
      <D_1154>01945678912345</D_1154>
      </C_C506>
      </S_RFF>
    - <S_RFF>
    - <C_C506>
      <D_1153>AEK</D_1153>
      <D_1154>01945678912345</D_1154>
      </C_C506>
      </S_RFF>
    - <S_BUS>
      <D_3279>IR</D_3279>
    - <C_C551>
      <D_4383>UGI</D_4383>
      </C_C551>
      </S_BUS>
    - <G_SSG5>
    - <S_MOA>
    - <C_C516>
      <D_5025>9</D_5025>
      <D_5004>5000</D_5004>
      <D_6345>EUR</D_6345>
      </C_C516>
      </S_MOA>
      </G_SSG5>
    - <G_SSG6>
    - <S_FII>
      <D_3035>OR</D_3035>
    - <C_C078>
      <D_3194>ES921998500000000012</D_3194>
      <D_6345>EUR</D_6345>
      </C_C078>
    - <C_C088>
      <D_3433>ABNAES17000</D_3433>
      <D_1131>25</D_1131>
      <D_3055>5</D_3055>
      </C_C088>
      <D_3207>ES</D_3207>
      </S_FII>
      </G_SSG6>
    - <G_SSG7>
    - <S_NAD>
      <D_3035>OY</D_3035>
    - <C_C080>
      <D_3036>XYZ CORPORATION LTD</D_3036>
      </C_C080>
    - <C_C059>
      <D_3042>XX</D_3042>
      </C_C059>
      <D_3164>XX</D_3164>
      <D_3207>ES</D_3207>
      </S_NAD>
      </G_SSG7>
    - <G_SSG11>
    - <S_SEQ>
    - <C_C286>
      <D_1050>1</D_1050>
      </C_C286>
    - <S_MOA>
    - <C_C516>
      <D_5025>9</D_5025>
      <D_5004>5000</D_5004>
      <D_6345>EUR</D_6345>
      </C_C516>
      </S_MOA>
    - <S_DTM>
    - <C_C507>
      <D_2005>227</D_2005>
      <D_2380>2007-02-01</D_2380>
      <D_2379>102</D_2379>
      </C_C507>
      </S_DTM>
    - <S_RFF>
    - <C_C506>
      <D_1153>AIK</D_1153>
      <D_1154>01901234567890</D_1154>
      </C_C506>
      </S_RFF>
    - <S_RFF>
    - <C_C506>
      <D_1153>CR</D_1153>
      <D_1154>01901234567890</D_1154>
      </C_C506>
      </S_RFF>
    - <S_FCA>
      <D_4471>13</D_4471>
      </S_FCA>
    - <G_SSG12>
    - <S_FII>
      <D_3035>BF</D_3035>
    - <C_C078>
      <D_3194>AT921998500000000011</D_3194>
      <D_6345>EUR</D_6345>
      </C_C078>
    - <C_C088>
      <D_3433>ABNAAT14000</D_3433>
      <D_1131>25</D_1131>
      <D_3055>5</D_3055>
      </C_C088>
      <D_3207>ES</D_3207>
      </S_FII>
      </G_SSG12>
    - <G_SSG13>
    - <S_NAD>
      <D_3035>BE</D_3035>
    - <C_C080>
      <D_3036>ABC CORPORATION 1</D_3036>
      </C_C080>
    - <C_C059>
      <D_3042>XX</D_3042>
      </C_C059>
      <D_3164>XX</D_3164>
      <D_3207>ES</D_3207>
      </S_NAD>
      </G_SSG13>
    - <G_SSG16>
    - <S_PRC>
    - <C_C242>
      <D_7187>11</D_7187>
      </C_C242>
    - <S_FTX>
      <D_4451>PMD</D_4451>
    - <C_C108>
      <D_4440>SENDERPN1</D_4440>
      </C_C108>
      </S_FTX>
      </S_PRC>
      </G_SSG16>
      </S_SEQ>
      </G_SSG11>
      </S_LIN>
      </G_SSG4>
    - <S_CNT>
    - <C_C270>
      <D_6069>2</D_6069>
      <D_6066>1</D_6066>
      </C_C270>
      </S_CNT>
    - <S_UNT>
      <D_0074>1</D_0074>
      <D_0062>1</D_0062>
      </S_UNT>
      </S_UNH>
    - <S_UNZ>
      <D_0036>1</D_0036>
      <D_0020>01945678912345</D_0020>
      </S_UNZ>
      </S_UNB>
      </LIST>
    <b>3. The module parameters for Seeburger inputs :</b>
    ( In receiver communication channel)
    <b>Processing Sequence</b>
    localejbs/CallBicXIRaBean               Local Ent Bean     x2e_bic_paymul
    SAP XI JMS Adapter/ConvertMessageToBinary     Local Ent Bean     convert_XI2Bin
    SAP XI JMS Adapter/SendBinarytoXIJMSService     Local Ent Bean     
                    exit
    <b>Module Key</b>
    x2e_bic_paymul     destSourceMsg     MainDocument
    x2e_bic_paymul     destTargetMsg     MainDocument
    x2e_bic_paymul     logAttID          ConverterLog
    x2e_bic_paymul     mappingName     See_X2E_PAYMUL_UN_D96A
    x2e_bic_paymul     newLine          true
    x2e_bic_paymul     saveSourceMsg     XMLEDI

    Hi,
    Check Below links,
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    SAP Adapters
    Regards,
    Phani

  • Want to configure jms adapter to listen two jms topics

    Hi,
    i want to implement an scenario where the single subscriber has to listen two topics. i have created two jms topics and pushing message into that now i want to consume the messages in two topics using single subscriber. is this is possible using JMS Adapter. any suggestions??? Kindly help...
    Thanks in advance...

    This is not possible.
    You can associate one subscriber to one topic only.You can have multiple subscribers listening on same topic but not the reverse.

  • Debugging JMS adapter with Module Configuration

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

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

  • Sender JMS adapter configuration for IBM MQSeries

    Dear All,
    i am doing a IBM MQSeries 5.2.x Message ->sender JMS adapter -> XI server -> receiver RFC adapter -> R/3.
    i have deployed the JMS adapter with the required jar files of IBM MQSeries 5.2.x in XI server.
    in Sender JMS adapter configuration for IBM MQSeries 5.2.x, i have put following data:
    1. Transport Protocol: Websphere MQ - is it okay?
    in JMS provider settings:
    2. in channel name - what should be there?
    3. Transport Network protocol should be TCP/IP or WebsphereMQ - how to decide this thing.
    4. JMS Complaint - whether WebsphereMQ or JMS API.
    in JMS Settings:
    5. JMS Queue user - is this IBM MQSeries 5.2.x Queue User or someother user?
    6. JMS Message Selector - what data to take here.
    So if anybody has connected IBM MQSeries 5.2.x to XI via JMS adapter, please answer my above queries.
    Regards,
    Rajeev Gupta

    Hi Swaroop,
    you can send me those documents at my gmail-id : [email protected]
    Hi All,
    one more question - to connect XI server to IBM MQSeries via JMS adapter in ID, do we need to have a MQSeries Client installed on XI server - or - just by configuring JMS adapter, we can send messages from IBM MQSeries to XI server without any MQSeries client on XI server?
    Why Channel name is required in JMS configuration data?
    Thanks,
    Rajeev Gupta

  • Query: Sender JMS Adapter configuration

    Hi All,
        I'm trying out a scenario which sends data from a Message Queue to SAP.
        For this I need to configure JMS adapter in the sender side. I would like to know whether <b>should I specify any content conversion parameters like "fieldLength" or "fieldSeperator" as we do it in sender file adapter for XI's indivual field identification.</b>
       If no then how the variables will get mapped properly to the XI outbound ( sender ) Structure from Message Queue???..
       Bcoz I believe MQ sends the data as a single stream of characters not as individual field..
       Please advice..
    Regards,
    Joe.
    Message was edited by: Joe

    Hi Satarupa,
              Thanks for your reply.
      But if I'm getting say a stream of 10 characters (Name - 4 characters, Address - 5 characters, Option - 1 character totally 10 characters), how the system will know it has to send first 4 characters to name defined in XI, next 5 characters to Address defined in XI and the next 1 character to Option  if I don't specify the conversion parameters?? 
      Bcoz the data flows in the same way to XI as it flows for file adapter, where we speciy the content conversion parameters which helps it to send it to the variables defined in XI accordingly.
      If you've some docs on both sender and receiver JMS adapters pls. lemme know..
    Thanks,
    Joe.

  • JMS Adapter Configuration (Access JMS Provider Generically)

    Hi Exports,
    How can i configure JMS adapter Using Access JMS Provider Generically, where can we mentioned target server. there is Quename and username and password but there is no target server details field. could you please give me suggetion how to configure this.

    Hi,
    This will help you
    JMS Adapter
    /people/kan.th/blog/2007/02/05/exploring-jms-and-sap-xi-jms-adaper
    http://help.sap.com/saphelp_nw2004s/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
    Sender Jms Adapter
    http://help.sap.com/saphelp_nw2004s/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
    Receiver Jms Adapter
    http://help.sap.com/saphelp_nw2004s/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm
    Regards
    Agasthuri Doss

  • JMS Adapter Configuration at reciver side

    Hi,
    Actaully I have to configure JMS adapter HAving Content Conversion.
    I m getting XML throuh XI and wan to convert it to TEXT File.
    Can anyone tell me wat MODULE NAME, TYPE, MODULE Key , PARAmeter NAMe and VAlue i have to take.
    Hemant

    Hi,
    Take a look at this document,
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
    Regards,
    Bhavesh

  • Sending Msg From HTTP client to XI through JMS Adapter using WebSphereMQ

    Hello
    I am trying to send some msg from Http client
    I configured JMS adapter as receiver
    Transport Protocol :WEBsphereMQ JMS provider
    Message  protocol :JMS1.x
    I have given the Ip  address  of my machine where I installed WEB Sphere MQ
    Server Port :1416
    Transport Protocol :WebSphere MQ
    JMS compliant: JMS-compliant
    In SXMB_MONI
    Http client sends message without any error.
    But while tracing I got message
    <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
    Can anybody tell me the solution..
    Thnaks

    Hi,
      I have not directly faced this but i may suggest ,
    1. What do you see in sxmb_moni, do you have a queue problem?
    2. see this File-to-File Scenario Stopped Working  the reply from Shravan and the last message.
    <i>The XBTO que was the problem. I deleted all LUWs in it and now new transactions are working again</i>
    3. You may also use this /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    Regards,
    Anirban.

  • JMS Adapter Error

    Hi Experts,
                   We are havingone problem in Sender JMS Adapter. From Sender (SeeBeyond) xml files are getting posted into Remote Queue in MQ, then it has been sent to Local Queue of MQ, and then finally from Local MQ Queue PI is picking up the data and sending it to SNC system.
                   The problem lies in PI itself. While coming into PI, the value in the incoming payload where special characters(say, swedish character) are coming, are coming into PI as a garbage value. Whereas, in Sender (SeeBeyond), MQ and in PI Character set is ISO 8859_1. We have stopped the Sender JMS channel in PI, and checked the payload in MQ and in SeeBeyond, in both of the cases it's fine, only when coming into PI, data are getting corrupted.
                    For this we have done some investigation like below,
    1) We had changed the CCSID from 00819 (ISO 8859_1) to 1208 (UTF-8), 1200 (UTF 16), but no luck.
    2) We had added th below mentioned modules into Sender JMS in Processing Sequence with the existing modules,
      AF_Modules/MessageTransformBean                                              Local Enterprise Bean               ContentType
    (ii) AF_Modules/TextCodepageConversionBean                                   Local Enterprise Bean               codepageConversion
    But yet we are getting the same error in encoding in the payload while coming into PI.
    Can anybody help me out with it, or probably let me know if I am missing something in my investigation.
    //BR
    Soumya

    Hi Stefan,
                 Sorry for the late reply. We were testing in different cases in PI, and here what I have found. In Sender JMS adapter we had put the module "AF_Modules/MessageTransformBean"  with Module Key "Transform". And the configuration of this Module Key is as follows:-
    Transform     Transform.ContentType      text/plain;charset="UTF-8"
    And we changed the CCSID to 1208 (UTF-8). Now when we saw the payload in SXI_MONITOR in PI, we have found that the special character is being distorted whereas in View Sourse the payload is fine including special character also. That means there might be some display problem in SXI_MONITOR.
                 Now, the Sender sends the data in XML iin ISO 8859-1nto MQ, MQ send the same as a string in PI, from PI it's going to SCM system (R/3, Supply Chain Management), where we could see ABAP.APPLICATION Error. We tested the interface in SCM system by running SPROXY and found that it's not able to recognise ISO 8859-1, since it's a Non-Unicode System, it will only understan UTF-8 and hence the error. Now manually we have changed the XML Header into UTF-8 and tested at SCM side, and this goes fine.
               So, we could see the changing of XML Header from ISO 8859-1 to UTF-8 would be running fine at receiver end (SCM). Since SCM is a Non-Unicode System, the XML header cannot be changed to UTF-8, is there any possibility in PI that we can change the XML Header from ISO 8859-1 to UTF-8.
               For your information, we are using Sender JMS adapter to receive the File from Sender and we are using Receiver XI adapter to post the file into SCM system.
    What's your suggestion Stefan, how can we change the XML Header from ISO 8859-1 to UTF-8 in PI?
    Many Thanks
    Soumya

  • JMS Adapter service not visible

    Hello All,
    I am trying to configure JMS adapter for my scenarios.
    I am unable to see SAP XI JMS Adapter service in the Visual Admin.
    Also when activate the communication channel. In the RWB it gives error "No adapter registered for the channel"
    What could be the issue?
    Thanks

    Hi Prabhu,
    Is it newly installed server,.??? if yes may be installation not done properly i guess...refresh the cache,is problem persist contact basis team.
    Regards,
    Raj

  • XI JMS adapter after JMS provider reboot

    Hi All,
    I have problem with XI JMS adapter. Adapter is in a JMS client role and JMS provider is Tibco. After reboot of JMS service in JMS provider, XI JMS adapter loose username and pw in connection and try logon to queue as an anonymous user.
    After deactivation + activation of XI JMS adapter, connection seems to work correctly with uname & pw.
    In JMS adapter we have folloving settings and we are connected straight into queue:
    Transport Protocol = SonicMQ JMS Provider
    General JMS Settings:
    Transactional JMS Session is in use
    Delivery Mode of Message Producer = Persist JMS messages..
    + Queue user & pw
    Error Handling Settings:
    Wait After Message Error(msecs) = 60000
    Wait Before Reconnect(msecs) = 60000
    Does anyone ran into this earlier?
    Thanks in advance.
    -Kimmo

    Hi Saravana,
    It seems that no connection is available to queue. In JMS adapter are you using correct path for finding these provider specifig classes in front of class name. Example: javax.jms.QueueConnectionFactory
    It is also possible that username of JMS provider which you configure to JMS adapter does not have correct rights for reading/writing or accessing to queue.
    We are not using any additional settings for JMS adapter. For server name we have also added protocol which is tcp://<servername> and using transactional JMS session.
    We had this same error when trying connect to queue via JNDI. Then we changed JMS adapter to connect straight to queue and it started to work.

Maybe you are looking for