SetStringProperty in JMS receiver adapter doesn't work

I want to set a property in the RFH2-header to my MQ-message but it doesn't work.
I try to do this by setting the additional JMS Parameter "JMS.Message.method.setStringProperty" but nothing happens in the resulting MQ-message.
The resulting MQ-message (the header) looks like this.
  (0x01000000):MQRFH2     = (
     (0x03000000):Version        = 2
     (0x03000000):Format         = 'MQSTR   '
     (0x03000000):Encoding       = 273
     (0x03000000):CodedCharSetId = 1208
     (0x03000000):Flags          = 0
     (0x03000000):NameValueCCSID = 1208
     (0x01000000):mcd            = (
       (0x01000000):Msd = (
         (0x02000000): = 'jms_text'
     (0x01000000):jms            = (
       (0x01000000):Dst = (
         (0x02000000): = 'queue:///SOMEQ'
       (0x01000000):Tms = (
         (0x02000000): = '1180524893525'
       (0x01000000):Cid = (
         (0x02000000): = '465c8ee5-91a5-00ae-0000-0000c0a82364'
       (0x01000000):Dlv = (
         (0x02000000): = '2'
Where can I expect to see my assigned property? I thought it should show up like below.
(0x01000000):usr            = (
      (0x01000000):MyProperty       = (
        (0x02000000): = 'MyValue'
Can somebody please help me?
regards
/Helé

Did you solve your issue? If so, could you please share? I'm facing a similar problem.
Thanks
Cheers
Jens

Similar Messages

  • Send Idoc flat file message in JMS receiver adapter

    Hello,
    I am working on a scenario where we send Delvry 03 idoc from ECC to external system. To external system, we send the whole Idoc in flat file structure through JMS queue. I have used Idoc to flat file program in my interface mapping and have configured JMS receiver adapter with just default Module configs but, I am getting an error in communication channel monitoring for the messages.
    Please note that Idoc xml to flat file structure conversion is already done in the mapping, I need to just pass this idoc flat structure in the jms adapter. Hence ther eis no content conversion i nthe adapter..
    Please give some inputs..Here are the modules in my receiver adapter and nothing else..
    SAP XI JMS Adapter/ConvertMessageToBinary
    SAP XI JMS Adapter/SendBinarytoXIJMSService
    The error I get is in audit log
    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_R:ca336a6689f837da8bd3387140fc4447
    in turn the message has this error if I open the message
    Whitespace is not allowed at this location. Error processing resource 'http://host:port/mdt/messageconten...
    and it shows one of the lines from idoc..flat file
    Any idea is greatly appreciated..Thank you..Thanujja

    The difference in what I suggest is that it is way simpler.
    Maybe you did not understand this, so will try to explain it better. Its not the best thing to do, but if JMS adapter doesn't budge then you can give it a shot.
    1. You continue to use the ABAP mapping in your interface mapping to map the Idoc xml to Idoc flat.
    2. Write a Java Map that will take the output of the ABAP mapping ; and then create a XML output which would be something like,
    <Root>
    <Idoc_Flat>
    <Data>ABAP Mapping Output<Data>
    </Idoc_Flat>
    </Root>
    3. Now use the simple content conversion in the JMS adapter to convert this to flat file.
    Regards
    Bhavesh

  • Adapter-specific message attributes for the JMS Receiver adapter

    Dear SAP Community,
    We are trying to activate some parameters at message level when SAP XI sent an interface (XML data) to IBM Websphere MQ. Programmaticaly, this is done the following way:
           TextMessage outMessage = session.createTextMessage();
           MQQueue replyToQ = new MQQueue("TESTQM01","SYSTEM.ADMIN.ACTIVITY.QUEUE");
           Destination replyTo = (Destination) replyToQ;
           outMessage.setJMSReplyTo(replyTo);
           outMessage.setIntProperty("JMS_IBM_Report_Exception", MQC.MQRO_EXCEPTION);
           outMessage.setIntProperty("JMS_IBM_Report_Expiration", MQC.MQRO_EXPIRATION);;
           outMessage.setIntProperty("JMS_IBM_Report_COA", MQC.MQRO_COA);
           outMessage.setIntProperty("JMS_IBM_Report_COD", MQC.MQRO_COD);
           outMessage.setIntProperty("JMS_IBM_Report_Discard_Msg", MQC.MQRO_DISCARD_MSG);
    This code is working fine.
    Since the documentation about this feature (Adapter-specific message attributes) is very light, We am not sure about the interpretation we made.
    First, we defined the following attributes: MS_IBM_Report_Exception, JMS_IBM_Report_Expiration, JMS_IBM_Report_COA, JMS_IBM_Report_COD, JMS_IBM_Report_Discard_Msg. All of them are with type int.
    Then we changed the mapping (XSL) to pass the value to the dynamic configuration, using the technical names (DCJMSMessageProperty0, ..., DCJMSMessageProperty4) and the value of the constants. We also specified a value in the Reply To Queue parameter of the adapter. As a test, We also change another parameter via the mapping (the correlation ID, to use the idoc number) and according to the log of the processed message, every thing is finde. According to the trace of the JMS adapter, everything is fine to. However, this has no impact on the message, only the correlation ID is changed.
    The JMS server is IBM Websphere MQ (v6.0.2.1). It is already in production and working fine. This is a change we have been asked to implement.
    Has anyone experience with the JMS receiver adapter-specific message attrbitutes ? What have we done wrong ?
    Any help is greatly appreciated.
    Regards,
    Gregory PFISTER
    SAP XI Analyst - Holcim

    Hi Neha,
    pls do chk the below links for SOAP adapter message attributes
    http://help.sap.com/saphelp_nwpi71/helpdata/en/fc/5ad93f130f9215e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/content.htm
    http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst38.htm
    http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/webservices/webservices16.htm
    Regards
    Sampath

  • SAP PI - JMS Receiver Adapter

    Hi All:
    Is it possible to override the queue name of the receiver JMS adapter from the Payload?
    I checked Adapter Specific Message Attributes of JMS receiver adapter, but could not find queue name attribute. I need to assign receiver JMS queue name from Payload.
    Any idea? Appreciate your quick reply.
    Thanks
    Farooq

    >
    Farooq Farooqui wrote:
    > As the Dynamic Configuration will not work here...so, any other alternative? Can we override/create adapter parameters values using peace of code (Not ASMA)?
    >
    > I am trying to find out solution..otherwise I have to change my design.
    >
    > Thanks
    > Farooq
    well then it would be as good as u r creating a new adapter
    i suggest a change of design would be the best here.

  • Error in JMS receiver adapter: "Error creating initial context with environment"

    Hello,
    I have some trouble with a JMS receiver adapter (access to JMS-provider with JNDI).
    The message in adapter monitoring is:
    A channel error occurred. Detailed error (if any) :
    com.sap.aii.adapter.jms.api.connector.ConnectorException: Fatal Error looking up connection factoryJMSQueueConnectionFactory, for profile: ConnectionProfile of channel: CC_JMS_RCV_XLIMI00001on node: 503473150 having object id: 5b424f2f79b6350ca636ab35d528cfdd:
    ConnectorException: Error creating initial context with environment: java.naming.provider.url=wcsefdev.example.com:9064; java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory; for profile: ConnectionProfile of channel:
    CC_JMS_RCV_XLIMI00001on node: 503473150 having object id: 5b424f2f79b6350ca636ab35d528cfdd: javax.naming.NoInitialContextException:
    Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory
    (JndiConnectorImpl.java:152)<br> ....
    Message processing failed. Cause:
    com.sap.aii.adapter.jms.core.fsm.DFA$InvalidTransitionException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_RCV_XLIMI00001:5b424f2f79b6350ca636ab35d528cfdd
    The third party assured me that the specified JNDI parameters are right and everything is configured on their site, so it should work...
    Might there be a problem with the JMS drivers?
    Regards,
    Marcus

    Hi Marcus,
    Have a look at below thread
    Connecting to PI 7.11 JMS Queue from other PI 7.11 Server

  • JMS Receiver Adapter - com.ibm.websphere.naming.WsnInitialContextFactory

    Hello experts,
    I am trying to configure JMS Adapter to Access Websphere Application Server via JNDI. The configuration is as follow:
    Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
    Connection Factory: jms/messageQueueCF
    Server URL: iiop://ammtnode.iubs.intra:2809/
    Queue Name: jms/EXT_INPUT_QUEUE
    I deployed all required jar files but Iu2019m still unable to connect to WAS because adapter cannot initialize ORB:
    javax.naming.NamingException: Failed to initialize the ORB
    I wrote a small java class to check where the problem was:
    ============================================================================
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY,"com.ibm.websphere.naming.WsnInitialContextFactory");
    env.put(Context.PROVIDER_URL, "iiop://ammtnode.iubs.intra:2809/");
    env.put("java.naming.corba.orb",org.omg.CORBA.ORB.init((String[])null,null));
    Context jndiContext = null;
    try {
    jndiContext = new InitialContext(env);
    ConnectionFactory connectionFactory = (ConnectionFactory) jndiContext.lookup("jms/messageQueueCF");
    Connection qConn = connectionFactory.createConnection();
    Session qSession = qConn.createSession(false,Session.AUTO_ACKNOWLEDGE);
    Queue q = (Queue) jndiContext.lookup("jms/EXT_INPUT_QUEUE");
    MessageProducer producer = qSession.createProducer(q);
    TextMessage message = qSession.createTextMessage();
    message.setText(text);
    producer.send(message);
    producer.close();
    qSession.close();
    qConn.close();
    } catch (Exception e) {
         e.printStackTrace();
    ============================================================================
    I got the same error until I wrote this line:
    env.put("java.naming.corba.orb",org.omg.CORBA.ORB.init((String[])null,null));
    And everything worked fine. Now I want to do the same in my JMS Receiver adapter but I donu2019t know how to introduce this line in the Initial Context Environment. I tried as JMS additional parameters and additional properties as well. However, nothing worked. Does anybody know what Iu2019m doing wrong?
    Thank you in advance!

    Here I post the entire error:
    0#0#Warning##Java###Catching #1#com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up connection fact
    oryjms/messageQueueCF, for profile: ConnectionProfile of channel: CC_I002_AMM_JmsReceiveron node: 5949650 having object id: 0
    360697bc61b3666aba07a2708ca095a: javax.naming.NamingException: Failed to initialize the ORB
            at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:134)
            at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:247)
            at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:185)
            at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:170)
            at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:153)
            at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:279)
            at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:166)
            at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:411)
            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
    Caused by: javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class
    com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:libra
    ry:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
            at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
            at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
            at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
            at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
            at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
            at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
            at javax.naming.InitialContext.lookup(InitialContext.java:351)
            at javax.naming.InitialContext.lookup(InitialContext.java:351)
            at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
            ... 11 more
    Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
    patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
    LoaderAT131b92e6ATalive
            at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
            at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
            at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
            at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
            at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
            at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
            ... 19 more
    Caused by:
    javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class com.sap.eng
    ine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:library:com.sap.
    aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
            at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
            at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
            at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
            at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
            at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
            at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
            at javax.naming.InitialContext.lookup(InitialContext.java:351)
            at javax.naming.InitialContext.lookup(InitialContext.java:351)
            at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
            ... 11 more
    Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
    patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
    LoaderAT131b92e6ATalive
            at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
            at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
            at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
            at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
            at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
            at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
            ... 19 more
    Caused by:
    javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class com.sap.eng
    ine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:library:com.sap.
    aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
            at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
            at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
            at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
            at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
            at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
            at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
            at javax.naming.InitialContext.lookup(InitialContext.java:351)
            at javax.naming.InitialContext.lookup(InitialContext.java:351)
            at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
            at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:247)
            at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:185)
            at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:170)
            at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:153)
            at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:279)
            at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:166)
            at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:411)
            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
    Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
    patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
    LoaderAT131b92e6ATalive
            at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
            at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
            at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
            at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
            at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
            at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
            ... 19 more

  • JMS Receiver Adapter to MQ - additional message property error

    Hi,
    I'm trying to add addional message properties to a Receiver JMS message for MQ Server queue. Creating the message in the MQ queue only works when I don't try to
    add additional message properties. As soon as I try to add additional message properties the XI-Monitor says it's OK but there is no message in the queue.
    Our system constellation is a bit odd cause we implemented the JMS/MQ classes of release 5.3 in XI/J2EE.
    Our actual used MQ Server is on release 5.1 due to compatibilty reasons of other productive software.
    Is there a need to use a MQ server of release 5.3 ?
    Has anybody a step by step description for implementing a JMS receiver Adapter for MQ with with additional message property (f.ex. mesType = salesOrder) in the MQ header?
    Thanx a lot in advance
    Hans

    Hi,
    You also might want to look at sap note 856346...for this ..
    2.6) I am connecting to a JMS provider using JNDI mode. How do I add pass an extra name,value property pair while setting up the JNDI initial context?
    Answer: Assuming that your property value is a string, please add the following name, value pair in "JMS Additional properties" table of your channel configuration:
    JNDI.InitialContext.property.X=java.lang.String propertyName, java.lang.String propertyValue
    where X is a number, the LHS part needs to be put in the name column and the RHS part in the value column of the table respectively.
    This note covers frequently asked questions that arise during the installation, configuration or administration of the XI JMS Adapter from the Adapter Framework (AF).
    Other terms
    JMS - Java Message Service
    AF - Adapter Framework
    AE - Adapter Engine
    SP - Service Pack
    Reason and Prerequisites
    This note clarifies the frequently asked questions on the XI/PI JMS adapter for released 3.0, 7.0 and 7.1 in the form of an FAQ. References to external information is provided at the end.
    Solution
    1. Documentation
    1.1) Where do I find the JMS adapter documentation?
    Answer: In the SAP online help. Go to http://help.sap.com and select  SAP Netweaver-> SAP Netweaver 7.1 or SAP NetWeaver 7.0 (2004s) or SAP Netweaver 2004. This opens up SAP Library topic page for that release.
    For releases 3.0 and 7.0:
    Select SAP Netweaver Library -> SAP Netweaver by Key capability-> Process Integration by Key Capability -> SAP Netweaver Exchange Infrastructure -> Runtime -> Connectivity -> Adapters -> JMS Adapter.
    For releases 7.1:
    Select SAP Netweaver Process Integration 7.1 -> SAP Netweaver Process Integration Library -> Function Oriented View > Advanced Adapter Engine.
    In the topic page click on the JMS Adapter link.
    Alternatively, you may simply enter the search string "JMS adapter" and navigate to the documentation page directly from the relevant search results. This is much faster.
    1.2) Which JMS providers are supported?
    Answer: The JMS Adapter supports JMS 1.02b and 1.1. JMS providers that also claim to be compatible with JMS 1.02b or 1.1 can be accessed using the JMS Adapter.
    Furthermore, SAP makes no assertions as to whether a particular JMS provider is tested or can be recommended, because SAP has not set up a certification or testing process.
    2. Functions and architecture
    2.1) Does the JMS Adapter support JMS topics (publish&subscribe)?
    Answer: No. Currently the JMS Adapter works with JMS queues because 100% Exactly Once (In Order) service quality can only be guaranteed with  JMS queues. However, this capability might be planned for introduction at a future release. (no planned time estimate)
    2.2) I have JMS message properties that are of significant. How do I get this data into XI? How do I get this data out of XI?
    Answer:
    A feature generically referred to as XI adapter-specific message properties was introduced in the adapter framework. This allowed additional adapter information to be attached to a XI message which can be used the routing, mapping and BPE. The message properties of different adapters are differentiated by namespaces.
    If you are on XI 3.0 support pack 18 onwards, the JMS adapter allows you to copy JMS message properties into these XI adapter specific message properties (at the sender JMS channel), and to copy the values of XI adapter specific message properties back into JMS message properties (at the receiver JMS channel).
    The JMS adapter currently supports upto 10 JMS message properties to be copied into the XI message properties with the name DCJMSMessageProperty0 to DCJMSMessageProperty9. The configuration details of how to achieve this are explained in the sub-topic pages of the JMS adapter documentation. (See sub topics: "Configuring the Sender JMS adapter", "Configuring the Receiver JMS adapter")
    JMS Message properties can have values belonging to types: boolean, byte, short, int, long, float, double, and String (defined in the specification). These are all normalized to strings when converted to the their respective XI message properties at the sender JMS channel.
    However, in the receiver JMS channel configuration, you can enter specific JMS message property types, such that these normalized XI message properties may be coerced back into their original types (or any compatible JMS message property type) when translating a XI message into a JMS message.
    Transfer of custom JMS Message properties from/to XI adapters-specific message attributes is only supported for JMS compliant messages, i.e. this feature will not work for Websphere MQ in legacy mode.
    Deprecated Information on this feature
    Between support pack 14 to support pack 18, the JMS adapter allowed the allowed you append only up to two JMS string properties to the XI message in the sender channel, which could then be analyzed in XI routing, mapping and BPE. In the JMS receiver channel, the XI adapter-specific message attributes could be read, and up to two JMS string properties could be set. The names of the (now deprecated) XI message properties were DCJMSStringProperty1 and DCJMSStringProperty2.
    Regards
    Ravi Raman

  • Create and Handle empty msg in JMS receiver Adapter

    Hi,
    In my interface scenario, I will have to create a msg output if certain conditions are met and should not create a msg if otherwise..
    I am using a Graphical Mapping and the receiver is JMS. I have some questions..
    1. Using Graphical mapping, Can I create an empty msg - If I dont map the root node if the conditions are not met, what happens to the msg during runtime ?? Will it create empty payload and does it error out as there is empty payload ??
    2. Like File adapter - is there a way to Ignore empty msg in JMS receiver adapter - so that it doesnt write any empty msgs i nthe queue..
    Any ideas/suggestions/experiences greatly appreciated please...
    Thank you
    Thanujja..

    Natesa,
    My bet. I am sorry I am wrong.
    One thing comes to my mind is you can do a multi mapping. So if it is ok then send to one receiver and if it exception then send as flat file which you dont use.
    Here since only one mapping is going to execute and the other going to fail you can write your own message exception in mapping stating "Its a know error". This is because if it is in produciton if this fails then it creates an alert. So just to tell to the end users it is ok you are populating the generic error. I know its not a good solution, but a work around kind of thing.
    Regards,
    ---Satish

  • Receiver determination doesn't work for same IDoc type but in differentSWCV

    hi guys,
    we have an emergency now. Receiver determination doesn't work for same IDoc type but in different SWCV.Please check below for detail.
    1. The process flow is : R/3 IDoc -> XI -> Third party system
    2. In previous release R13, IDoc ORDERS05 was imported and used in XI and software component version is R13. And receiver determination was created.
    3. Now, in new release R17, IDoc ORDERS05 was imported from R/3 to XI again and software component version is R17. And in R17, the receiver determination created in R13 was used for both old interface(R13) and new interface in R17.
    Then we encountered the problem, both interfaces doesn't work now, even we deleted the receiver condition(In R13, IDoc ORDERS05 was sent to system A, and in R17 IDoc ORDERS05 was sent to system B, RCVPRN was used as an condition).
    Does anyone encounter this problem? really need and appreciate your help.
    -Eddie

    information from monitor:
    Status     Sender               Service Sender Namespace                         Sender Interface
    reschedul  XXXCLNT100     urn:sap-com:document:sap:idoc:messages   ORDRSP.ORDERS05
    columns for "Receiver Service","Receiver Namespace", "Receiver Interface" are blank
    And then double click records in monitor, go into detail information...
    Normally there's lots of setps existed, such as
    Inbound Message ( CENTRAL )
    Receiver Identification
    Interface Determination
    Receiver Grouping
    Message Branch According to Receiver List
    Technical Routing
    Call Adapter
    But now there's only one setp -
    "Inbound Message ( CENTRAL )" existed, no any another setp..., and payload in inbound message looks good.
    And in SMQ2, I checked the queue information, found there's an error - "An exception occurred that was not caught." No any other detail information for this error.

  • How do I use a NORMAL headset (dual 3.5mm) on my new Macbook pro retina? No usb ports available and headset buddy adapter doesn't work.

    Title says it all:
    How do I use a NORMAL headset (dual 3.5mm) on my new Macbook pro retina? No usb ports available and headset buddy adapter doesn't work.

    Hi Auracles1,
    Here's a pretty discussion regarding wireless printing with this device and a Mac.
    http://h30434.www3.hp.com/t5/Printer-networking-and-wireless/HP-Officejet-6500-E 709n-wireless-issue/m-p/258853
    I have a similar OfficeJet and it was a multi-step process. (1) Install printer drivers on the machine, (2) Add the printer queue in print & fax, (3) Run the "setup wizard" from the disc for wireless printing.

  • My iphone 5s with lightning to 30 pin adapter doesn't work in my audi A6 to play music, only to charge the phone. is there a fix for this?

    my iphone 5s with lightning to 30 pin adapter doesn't work in my audi A6 to play music, only to charge the phone. is there a fix for this?

    Is the adapter the genuine Apple product or a copy

  • Email send/receive suddenly doesn't work ; can't change email settings as BB phone won't accept valid username and password -- what to do?

    email send/receive suddenly doesn't work (as of September 24th); I can't change email settings (one suggestion from tech) as BB phone won't accept *valid* username and password -- what to do?
    I understand from a support note that if I keep trying my password/username combination, my BB will eventually delete all data!
    I can't understand this. I'm completely lost now. I can't remember what I've done or tried to do. A plethora of usernames and passwords is swimming in my head.
    Thanks for any hints. I have always loved this BB Bold and have never had any trouble with it.

    But the real question is why for the past year did the passwords work and then all of the sudden after this anomaly the disk password doesn't work?  I'm not 100% sure of what my configuration was, but I know that most of the time it required one password -- supervisor, and occasionally it asked for 2 -- disk password as well I believe.  This may have been related to the Password on Restart setting I think -- asking for the disk password on cold vs. warm boot.  But I know both were exactly the same.  But after this incident only the Supervisor password worked.

  • My magsafe adapter doesn't work, how can i solve this problem?

    my magsafe adapter doesn't work, how can i solve this problem?

    You can get a 60W power adapter for about $20 on eBay http://www.ebay.com/sch/i.html?_trkparms=65%253A1%257C66%253A2%257C39%253A1&rt=n c&_nkw=macbook+power+adapter&_dmpt=Laptop_Adapters_Chargers&_sticky=1&_trksid=p 3 286.c0.m14&_sop=12&_sc=1

  • WLAN adapter doesn't work on my Satellite A200

    Hi,
    My WLAN adapter doesn't work under Vista. If I press FN + F8 nothing happens. The wireless-communication is still offline.
    What can I do?
    Details:
    Typ: Atheros AR5008X Version: 7.2.0.164
    Notebook Satellite 200
    PSAE6E
    Please help me!
    Thx in advance!
    Phil

    BIOS bug? I dont think so
    Firstly you should ensure that this is not a hardware issue. In such case insert the Toshiba Recovery CD and reinstall the OS on this unit. This will set the notebook to the factory settings. Note; this would format the whole HDD.
    After new installation, you have to enable the WLan switch at the notebooks side and then you could use the button switch FN+F8 to select the WLan.
    I presume you have already configured your Wlan router. So the same settings like SSID, WLan encryption, etc must be set on the notebook too.

  • JMS receiver adapter Error

    Hi Experts,
    Any idea about this error. We are getting following in JMS receiver adapter in PI 7.1.
    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: Connector for ConnectionProfile of channel: JMS_Receiver_THQPRD2_Slow_Replyon node: 284760550 having object id: cf2f6eb7d6c93902b64b27bfcaad0ba5 encountered error: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException: while trying to read the field 'ccsid' of an object loaded from field com.ibm.mq.MQSESSIONClient.comms of an object loaded from local variable '<0>' in sending to destination queue:///QR.EAIPRD.THQPRD2.REPLY.SLOW?targetClient=1, the message message: JMS Message class: jms_text  JMSType:         null  JMSDeliveryMode: 2  JMSExpiration:   0  JMSPriority:     4  JMSMessageID:    null  JMSTimestamp:    0  JMSCorrelationID:ID:414d5120504c535748353533202020204e6324ae23eb5b2d  JMSDestination:  null  JMSReplyTo:      null  JMSRedelivered:  false XPLOR     PIPXSDI2030 45219q00282YSDI2030PROCESS_MQSERIES              PLSWH553                     Another 12,761 character(s) omitted: javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException: while trying to read the field 'ccsid' of an object loaded from field com.ibm.mq.MQSESSIONClient.comms of an object loaded from local variable '<0>'.
    Thanks,
    Hari

    Hello,
    The error indicates a JMS driver issue.
    Another customer resolved this issue by updating their MQ and the MQ drivers version (in their case to 6.0.2.8.)
    You could try contacting IBM for advice on a similar upgrade.
    #1086303 XI JMS Adapter and IBM Websphere MQ: FAQ
       12)What is the recommended version of MQ drivers for the PI JMS
    Adapter - IBM MQ connectivity ?
    Kind regards,
    Sarah

Maybe you are looking for