JMS Adapter timeout property

How do I set timeout property for JMS adapter in BPEL in SOA Suite 10g ?
Scenario :
In one of the business scenarios, a JMS message in enqueued to WebLogic JMS queue from BPEL process.
There is a asyncronus invoke activity to the JMS adapter partner link.
This invoke activity to the JMS adapter took 15 mins in one of the invocations and hence giving timeout to the bpel client.
Query :
Is there any way I could set the timeout for this invocation, either at partner link level or a JMS adapter connection factory level.

Hi,
This is supposed to solve ERRJMS_PROVIDER_ERR error for JMS adapter.
Please refer metalink NOTE:393468.1.
I am not sure if it works for 10.1.2.0.2 version but probably it works on 10.1..3.X version.
Regards,
Ved

Similar Messages

  • JMS Adapter UseMessageListener property...

    What is the use of the 'UseMessageListener' property that needs to be set as true / false while configuring an Inbound JMS Adapter Service. What difference does the true / false value make to the runtime working of the Service? Thanks in advance.

    Hi,
    This is supposed to solve ERRJMS_PROVIDER_ERR error for JMS adapter.
    Please refer metalink NOTE:393468.1.
    I am not sure if it works for 10.1.2.0.2 version but probably it works on 10.1..3.X version.
    Regards,
    Ved

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

  • ORABPEL-12141 JMS Adapter

    BPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
    Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
    Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
    Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
    XML file entry for JMS Adapter in BPEL :-
    <connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
    <config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
    <config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
    <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
    <config-property name="isTopic" value="true"/>
    <config-property name="isTransacted" value="false"/>
    <config-property name="username" value=""/>
    <config-property name="password" value=""/>
    </connector-factory>
    Portion of Domain.log file :-
    <2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
    <2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
    <2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
    <2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
    ORABPEL-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.connection.factory neither through JNDI nor instantiate it as a Java class
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
    at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
    at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
    at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
    at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
    at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
    at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
    at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
    at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
    ... 16 more
    Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
    at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
    ... 21 more

    BPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
    Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
    Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
    Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
    XML file entry for JMS Adapter in BPEL :-
    <connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
    <config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
    <config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
    <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
    <config-property name="isTopic" value="true"/>
    <config-property name="isTransacted" value="false"/>
    <config-property name="username" value=""/>
    <config-property name="password" value=""/>
    </connector-factory>
    Portion of Domain.log file :-
    <2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
    <2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
    <2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
    <2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
    ORABPEL-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.connection.factory neither through JNDI nor instantiate it as a Java class
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
    at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
    at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
    at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
    at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
    at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
    at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
    at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
    at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
    ... 16 more
    Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
    at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
    ... 21 more

  • Sensors in BPEL (JMS Adapter)

    Hi there! I'm trying to send Sensor-Data into a MQQueue, but this always results in an
    error. The results are in the following Error-Log (sorry, some messages are german but the
    messages are nearly equal to english):
    Caused by: ORABPEL-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    Instanziieren von Connection Factory nicht möglich. JMS-Adapter konnte Connection Factory com.ibm.mq.jms.MQQueueConnectionFactory weder JNDI nicht finden noch als Java-Klasse instanziieren
    Weitere Informationen hierzu finden Sie in der Log-Datei.
         at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:207)
         at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getQueueConnectionFactory(JMSConnectionFactoryFactory.java:98)
         at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:191)
         at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:132)
         at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:426)
         at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:417)
         at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:380)
         at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:104)
         at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
         at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:125)
         at com.collaxa.cube.engine.sensor.sa.publisher.JMSAdapterPublisher.publish(JMSAdapterPublisher.java:277)
         at com.collaxa.cube.engine.sensor.sa.FilteredDataPublisher.publish(FilteredDataPublisher.java:99)
         at com.collaxa.cube.engine.sensor.sa.BpelPublisher.publish(BpelPublisher.java:129)
         ... 83 more
    Caused by: javax.naming.NameNotFoundException: com.ibm.mq.jms.MQQueueConnectionFactory not found
         at com.evermind.server.rmi.RMIServerContext.lookup(RMIServerContext.java:207)
         at com.evermind.server.ApplicationContext.unprivileged_lookup(ApplicationContext.java:257)
    The following Steps were made:
    - I added two library-paths in the application.xml (D:\Programme\SOA_Suite\10.1.3.1\OracleAS_1\j2ee\oc4j_soa\config\application.xml)
    <library path="../../home/lib/com.ibm.mq.jar"/>
    <library path="../../home/lib/com.ibm.mqjms.jar"/>
    - In the oc4j-ra.xml (D:\Programme\SOA_Suite\10.1.3.1\OracleAS_1\j2ee\oc4j_soa\application-deployments\default\JmsAdapter\oc4j-ra.xml)
    a new connector-factory was added
         <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=MQ_TEST;TransportType=1;HostName=10.1.1.1;Port=1414;Channel=SYSTEM.DEF.TEST"/>
              <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
              <config-property name="isTopic" value="false"/>
              <config-property name="isTransacted" value="true"/>
              <config-property name="username" value=""/>
              <config-property name="password" value=""/>
              <connection-pooling use="none">
              </connection-pooling>
              <security-config use="none">
              </security-config>
         </connector-factory>
    I assume I have to enter a new JNDI-Entry somewhere but the JNDI-Browser in the Application Server is readonly.

    There are two ways to get data into BAM. There is the ADC web service that BPEL uses and then there's Enterprise Link which is the ETL tool that can grab data from Databases and other sources. I only used EL for jms and for ETLing data into a a BAM data object, I never used it for real time. The only real time BAM I've done is with BPEL projects with BAM sensors. I don't think EL is sophisticated enough for looking for changes in rows of data.
    Maybe you can have a db trigger that publishs the changed data to table specially designed for your task. Then you can create an EL "Plan" that runs periodically at a high enough rate that it appears to be in real time in BAM.
    Another possibility is to have the db trigger fire off an xml message that contains the data to the BAM ADC webservice. The BAM ADC web service is http://server:port/OracleBAM/Services/DataObject/DataObjectOperations.asmx.
    It has documentation on how to use it. I don't know if you're db can execute application code or not though.

  • How to set property for Cluster Environment for JMS Adapter

    Hi All,
    I am moving from DEV to Prod environment which is cluster.
    Can you Please explain me what property I need to Set for Cluster Environment for JMS Adapter, so that I could avoid race condition for Dequeue/enqueue.
    I am using soa suite 10.1..3.4
    Thanks in Advance.
    Edited by: vikky123 on Jul 12, 2010 7:03 AM

    put something like this
    <activationAgents>
          <activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="PARNERLINKNAME">
            <property name="clusterGroupId">SOMEUNIQUEVALUE</property>
            <property name="portType">PARTNERLINK_PORTTYPE</property>
          </activationAgent>
        </activationAgents>

  • How to set JMS user property in JMS Adapter.

    I am using Jdeveloper and SOA 11g. I want to filter some JMS messages from a topic based on a JMS user property. It is consumed using (JMS Adapter) consumer --> Mediator---> DBAdapter.
    My Question is how to define a JMS user property using Jdeveloper 11g.
    Thanks
    Edited by: user5108636 on 24/06/2010 16:10

    In Mediator mplan Assign Values use a property expression in the "to" side like:
    jca.jms.JMSProperty.XXX
    where XXX is the name of the property you would like to have created and populated. In source it will look like:
    <Mediator name="A03QueueWFeedMediator" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.oracle.com/sca/1.0/mediator"
    wsdlTargetNamespace="http://www.oracle.com/integration/b2b/A03QueueWFeedFromB2B/">
    <operation name="receive" deliveryPolicy="AllOrNothing" priority="4"
    validateSchema="false">
    <switch>
    <case executionType="direct" name="A03QueueWFeedToJMS.Produce_Message">
    <action>
    <transform>
    <part name="$out.body"
    function="xslt(xsl/ADT_AXX_To_ADT_AXX.xsl, $in.body)"/>
    </transform>
    <assign>
    <copy target="$out.body/imp1:ADT_AXX/imp1:MSH/@Type"
    value="$in.property.b2b.documentDefinitionName"
    xmlns:imp1="NS_64FCBED013AA409D933F624674E67BF220070423183755"/>
    <copy target="$out.body/imp1:ADT_AXX/imp1:MSH/@ID"
    value="$in.property.b2b.fromTradingPartnerId"
    xmlns:imp1="NS_64FCBED013AA409D933F624674E67BF220070423183755"/>
    <copy target="$out.body/imp1:ADT_AXX/imp1:MSH/@Name"
    value="$in.property.b2b.toTradingPartnerId"
    xmlns:imp1="NS_64FCBED013AA409D933F624674E67BF220070423183755"/>
    <copy target="$out.property.b2b.conversationId"
    value="$in.property.b2b.conversationId"/>
    <copy target="$out.property.b2b.documentDefinitionName"
    value="$in.property.b2b.documentDefinitionName"/>
    <copy target="$out.property.b2b.documentProtocolName"
    value="$in.property.b2b.documentProtocolName"/>
    <copy target="$out.property.b2b.documentProtocolVersion"
    value="$in.property.b2b.documentProtocolVersion"/>
    <copy target="$out.property.b2b.documentTypeName"
    value="$in.property.b2b.documentTypeName"/>
    <copy target="$out.property.b2b.fromTradingPartnerId"
    value="$in.property.b2b.fromTradingPartnerId"/>
    <copy target="$out.property.b2b.fromTradingPartnerIdType"
    value="$in.property.b2b.fromTradingPartnerIdType"/>
    <copy target="$out.property.b2b.toTradingPartnerId"
    value="$in.property.b2b.toTradingPartnerId"/>
    <copy target="$out.property.b2b.toTradingPartnerIdType"
    value="$in.property.b2b.toTradingPartnerIdType"/>
    *<copy target="$out.property.jca.jms.JMSProperty.conversationId"*
    value="$in.property.b2b.conversationId"/> <copy target="$out.property.jca.jms.JMSProperty.documentDefinitionName"
    value="$in.property.b2b.documentDefinitionName"/>
    <copy target="$out.property.jca.jms.JMSProperty.documentProtocolName"
    value="$in.property.b2b.documentProtocolName"/>
    <copy target="$out.property.jca.jms.JMSProperty.documentProtocolVersion"
    value="$in.property.b2b.documentProtocolVersion"/>
    <copy target="$out.property.jca.jms.JMSProperty.documentTypeName"
    value="$in.property.b2b.documentTypeName"/>
    <copy target="$out.property.jca.jms.JMSProperty.fromTradingPartnerId"
    value="$in.property.b2b.fromTradingPartnerId"/>
    <copy target="$out.property.jca.jms.JMSProperty.fromTradingPartnerIdType"
    value="$in.property.b2b.fromTradingPartnerIdType"/>
    <copy target="$out.property.jca.jms.JMSProperty.toTradingPartnerId"
    value="$in.property.b2b.toTradingPartnerId"/>
    <copy target="$out.property.jca.jms.JMSProperty.toTradingPartnerIdType"
    value="$in.property.b2b.toTradingPartnerIdType"/>
    </assign>
    <invoke reference="A03QueueWFeedToJMS" operation="Produce_Message"/>
    </action>
    </case>
    </switch>
    </operation>
    </Mediator>
    The runtime will see something like:
    [2010-09-09T11:48:06.353+10:00] [AdminServer] [TRACE] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@60ddbc76] [userId: weblogic] [ecid: 0000Ifo9olH2zGWjLxmJOA1CY0sg0001jY,0] [SRC_CLASS: oracle.integration.platform.blocks.adapter.fw.log.LogManagerImpl] [APP: soa-infra] [dcid: 02d1ff4621073810:26418f01:12af379c141:-7fd3-0000000000000219] [SRC_METHOD: log] Jms Adapter A03QueueWFeed:A03QueueWFeedToJMS [ Produce_Message_ptt::Produce_Message(body) ] XMLHelper_convertJmsMessageHeadersAndPropertiesToXML: <JMSInboundHeadersAndProperties xmlns="http://xmlns.oracle.com/pcbpel/adapter/jms/">[[
    <JMSInboundHeaders>
    <JMSCorrelationID></JMSCorrelationID>
    <JMSDeliveryMode>2</JMSDeliveryMode>
    <JMSExpiration>0</JMSExpiration>
    <JMSMessageID>ID:&lt;911867.1283996886119.0></JMSMessageID>
    <JMSPriority>4</JMSPriority>
    <JMSRedelivered>false</JMSRedelivered>
    <JMSType></JMSType>
    <JMSTimestamp>1283996886119</JMSTimestamp>
    </JMSInboundHeaders>
    <JMSInboundProperties>
    <Property name="documentProtocolVersion" value="2.3"/>
    <Property name="toTradingPartnerIdType" value="Name"/>
    *<Property name="conversationId" value="C0A83C0712AF42D840E0000074BA3CCC"/>* <Property name="documentTypeName" value="ADT"/>
    <Property name="tracking_conversationId" value="C0A83C0712AF42D866F0000074BA3CD9"/>
    <Property name="tracking_ecid" value="C0A83C0712AF42D866F0000074BA3CDA"/>
    <Property name="tracking_compositeInstanceId" value="60019"/>
    <Property name="documentProtocolName" value="HL7"/>
    <Property name="documentDefinitionName" value="QH_ADT_Generic"/>
    <Property name="tracking_parentComponentInstanceId" value="mediator:45E076D0BBB411DFAF05817F5F0DD1A1"/>
    <Property name="fromTradingPartnerIdType" value="Name"/>
    <Property name="fromTradingPartnerId" value="HOMER"/>
    <Property name="toTradingPartnerId" value="Self"/>
    <Property name="JMSXDeliveryCount" type="integer" value="1"/>
    </JMSInboundProperties>
    </JMSInboundHeadersAndProperties>
    Edited by: Michael.Czapski on 8/09/2010 18:58

  • How  to Set JMS property and Read JMS property in BPEL using JMS adapter

    Does any one know how to set or read more than one JMS property in BPEL using JMS adapter. My queue server is Oracle JMS server.
    Any help and sample is well appreciated

    Hi Van
    I have noted that only the attribute "type" is missing. It seems that when you create a "string" property, the attribute "type" is droped from the XML. If you use another type (as "integer" or "double") it stays there.
    If you try to read your properties, except for the "type" attribute, you should be successful, as I am. If you need, please tell me your email, I can send you my code.
    Source Code:
    in ASSIGN activity (process which SENDS the JMS message):
    <assign name="TESTES">
    <copy>
         <from expression="'string'"/>
         <to variable="HeaderJms" part="outboundHeader"
         query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[1]/@type"/>
    </copy>
    <copy>
         <from expression="'name'"/>
         <to variable="HeaderJms" part="outboundHeader"
         query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[1]/@name"/>
    </copy>
    <copy>
         <from expression="'value1'"/>
         <to variable="HeaderJms" part="outboundHeader"
         query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[1]/@value"/>
    </copy>
    <bpelx:append>
         <bpelx:from>
         <Property name="" type="" value=""
              xmlns="http://xmlns.oracle.com/pcbpel/adapter/jms/"/>
         </bpelx:from>
         <bpelx:to variable="HeaderJms" part="outboundHeader"
              query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties"/>
    </bpelx:append>
    <copy>
         <from expression="'string'"/>
         <to variable="HeaderJms" part="outboundHeader"
         query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[2]/@type"/>
    </copy>
    <copy>
         <from expression="'name2'"/>
         <to variable="HeaderJms" part="outboundHeader"
         query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[2]/@name"/>
    </copy>
    <copy>
         <from expression="'value2'"/>
         <to variable="HeaderJms" part="outboundHeader"
         query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[2]/@value"/>
    </copy>
    </assign>
    in ASSIGN activity (process which READS the JMS message)
    <assign name="Assign_1">
    <copy>
    <from variable="Variable_1" part="inboundHeader"
    query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[10]/@name"/>
    <to variable="temp"/>
    </copy>
    <copy>
    <from variable="Variable_1" part="inboundHeader"
    query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[10]/@value"/>
    <to variable="temp"/>
    </copy>
    <copy>
    <from variable="Variable_1" part="inboundHeader"
    query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[12]/@name"/>
    <to variable="temp"/>
    </copy>
    <copy>
    <from variable="Variable_1" part="inboundHeader"
    query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[12]/@value"/>
    <to variable="temp"/>
    </copy>
    </assign>
    Note that I do not try to read the "type" attribute, otherwise it will fail.
    Here is the JMS Header Message received:
    <inboundHeader>
    <JMSInboundHeadersAndProperties xmlns="http://xmlns.oracle.com/pcbpel/adapter/jms/">
    <JMSInboundHeaders>
    <JMSCorrelationID>
    bpel://localhost/pi_lms-c001e/BpelPiAtualizacaoC001E~1.0/3200025-BpInv0-BpSeq1.6-2
    </JMSCorrelationID>
    <JMSDeliveryMode>2</JMSDeliveryMode>
    <JMSExpiration>0</JMSExpiration>
    <JMSMessageID>ID:467DFA1FA1ED459EBF37F51F596C3F12</JMSMessageID>
    <JMSPriority>4</JMSPriority>
    <JMSRedelivered>false</JMSRedelivered>
    <JMSType>com.mercurio.lms.integration.c001eip.c001EIntegrationPoint</JMSType>
    <JMSTimestamp>1201552046253</JMSTimestamp>
    </JMSInboundHeaders>
    - <JMSInboundProperties>
    <Property name="JMSXDeliveryCount" type="integer" value="1"/>
    <Property name="JMSXRecvTimestamp" type="long" value="1201552046698"/>
    <Property name="JMSXUserID" value="lms_dev_int_v1_user"/>
    <Property name="JMS_OracleDeliveryMode" value="2"/>
    <Property name="JMS_OracleTimestamp" type="long" value="1201552046253"/>
    <Property name="JMS_OracleDelay" type="long" value="0"/>
    <Property name="JMSXState" type="integer" value="0"/>
    <Property name="IAS_VERSION" value="10.1.3"/>
    <Property name="JMS_OracleDeliveryMode" value="2"/>
    <Property name="name" value="value1"/> ("type" attribute was droped!!!)
    <Property name="JMS_OracleTimestamp" type="long" value="1201552046253"/>
    <Property name="name2" value="value2"/> ("type" attribute was droped!!!)
    </JMSInboundProperties>
    </JMSInboundHeadersAndProperties>
    </inboundHeader>
    Regards
    Marcelo

  • How to add the JMS adapter property in BPEL1.1 version

    Hi,
    I am working on the Jms adapter by using BPEL version1.1 and i am want to add some Jms property to send with Jms message.We have option to add the Jms property in BPEL2.0 version. But i am not able to add Jms property in BPEL version1.1.
    Please help me
    SOA 11g : 11.1.1.5

    Thanks for everyone's replies. I am now able to set the parameters for the sequence file, just that I added a property node for the sequence file path and the sequence before loading the parameters. That did the trick and the rest was easy. Also for Goto, with some digging, I was able to add a custom property step if it fails or passes the step. It works like a charm. I'm attaching a modified version of my code in LV 7.0 format.
    Attachments:
    Dynamic Sequence File-1.vi ‏175 KB

  • Processing messages from MQ by JMS adapter

    Hi,
    I have a JMS adapter which reads messages from MQ and invokes a real time service.
    I am facing a problem.
    Suppose after processing my 3rd message fails , i get the error
    com.acta.adapter.sdk.RecoverableOperationAdapterException: JMS GET OPERATION ERROR : TIMEOUT.UNABLE TO RECEIVE RESPONSE FROM THE INVOKED DATA SERVICES SERVICE.ADAPTER OPERATION TO CONTINUE.
    Now ideally the error messages should go into an error queue and the remaining messages should be processed.
    But the remaining messages are also not getting processed.All subsequent  messages after erroneous message also get into error q.
    I have set continue after error property(In operations configuration) to True.
    I am using Get operation for JMS adapter.
    Any idea what could solve this issue?

    Hi Manoj,
    I have a very similar if not identical issue,
    Error while running realtime jobs that read from JMS tables via JMS MQ adapter:
    15/11/12 09:10:08  JMS GET OPERATION ERROR : TIMEOUT.UNABLE TO RECEIVE RESPONSE FROM THE INVOKED DATA SERVICES SERVICE.ADAPTER OPERA
    TION TO CONTINUE.
    15/11/12 09:10:15  Communication Error. See real time job log for details.
    Dump available:
    https://sapmats.wdf.sap.corp/download/download.cgi?id=5C0KZAHA3RSXBJW3ABLMUUT2P5UUKWO2TM3EJDM5W2HGDZUDID
    Version of DS:14.0.3.273
    Any comments?
    Thansk and kind Regards,
    Kenneth

  • JMS Adapter Infinite Retries

    Hi,
    How can i restrict the JMS Adapter from retrying for infinite number of times?
    when we try to deploy a composite that connects to webmethods topic, it createConsumer failure exception (ClientId not Set) and it keeps retrying for n number of times but the deployment is successful. As a result of this, the Admin server health goes to warning state. How can we restrict  the retry to a specific count. Note: we have already set jca.retry.count in composit.xml but has no effect.
    Please see the error message below:
    [2013-10-28T12:36:56.481+01:00] [soa_server2] [WARNING] [] [oracle.soa.adapter] [tid: ReplicatedCache:sit_soa_domain_soa_clusterCacheService:EventDispatcher] [userId: <anonymous>] [ecid: 30865ccf2ac3cf83:-5242106e:141f0815285:-8000-0000000000000002,1:23297] [APP: soa-infra] JMSAdapter <CompositeName> JMSMessageConsumer_init:[destination = jms/WMTopic (payload = 1, subscriber = WMASIN)]: Retrying connection; attempt #82
    [2013-10-28T12:36:56.482+01:00] [soa_server2] [WARNING] [] [oracle.soa.adapter] [tid: ReplicatedCache:sit_soa_domain_soa_clusterCacheService:EventDispatcher] [userId: <anonymous>] [ecid: 30865ccf2ac3cf83:-5242106e:141f0815285:-8000-0000000000000002,1:23297] [APP: soa-infra] JMSAdapter <CompositeName> [[
    BINDING.JCA-12134
    ERRJMS_ERR_CR_TOPIC_CONS.
    ERRJMS_ERR_CR_TOPIC_CONS.
    Unable to create Topic consumer due to JMSException.
    Please examine the log file to determine the problem.
    Thanks in advance.

    you can try setting receive timeout property value.

  • Unable to get BPEL composite with JMS Adapter running.

    Hello All,
    I have tried to build a BPEL Composite to use JMS Adapter, by following the link http://blogs.sun.com/malkit/entry/oracle_soa_suite_bpel_to
    Steps in WebLogic console:
    1. Created a new JMS Server JMSServer-0 (file persistent store) this is targeted to AdminServer
    1. Created a new JMS Module SystemModule-0
    3. Created a connection factory in this module JNDI jms/SendRecvConnectionFactory
    4. Created a queue in this module JNDI jms/ReceiveQueue
    5. Created a SubDeployment Subdeployment0 for these two components.
    6. Created a new JMSAdapter connection pool JNDI eis/tst/TestJMSConn and set the ConnectionFactoryLocation property to jms/SendRecvConnectionFactory
    Next, I created a simple Java client and tested the JMS Queue to work fine. This went well.
    Next, used JDeveloper to create a BPEL Composite to use JMSAdapater, and followed the guidelines given in the above URL to create the JCA file.
    While deploying this BPEL composite, I hit a warning in SOA diagnostic server:
    JMSAdapter JMSSampleProj JmsDDEndpoint_onFailure: Unable to resolve 'jms.ReceiveQueue'
    As a result of this warning, the BPEL Composite instances do not get created when I send a message from the test client.
    Please find herewith the log details.
    I am using JDeveloper Build JDEVADF_11.1.1.4.0_GENERIC_101227.1736.5923 and FMW 11g R1 PS3 RC11.
    Any help here?
    [2011-04-20T08:33:12.098-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.bpel.engine.deployment] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] BPEL Component "default/JMSSampleProj!1.0*soa_8a1f7f5d-5ede-4e3a-8740-20fb90ffdab2/JMSampleProcess" successfully loaded.
    [2011-04-20T08:33:12.098-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.deploy] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] [Deployment] Component: JMSampleProcess was successfully deployed to service engine:implementation.bpel, for composite:JMSSampleProj
    [2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.OutBound/1.0] :init Initializing OutBound_jms.jca
    [2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> OutBound JCAEndpointInteraction::initInteraction - Activating Endpoint Interaction, Endpoint Id='OutBound
    [2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.OutBound/1.0] :init Successfully initialized OutBound_jms.jca
    [2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.mesh] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] EventBus not null
    [2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.integration.platform.blocks.mesh] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] component : Component Name: JMSampleProcess[[
    implementation: oracle.fabric.composite.component.implementation.BPELImplementation@51db9e4
    oracle.fabric.composite.model.ComponentTypeModel@51db9e6
    [2011-04-20T08:33:12.114-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.bpel.engine] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] CubeServiceEngine=> initing default/JMSSampleProj!1.0*soa_8a1f7f5d-5ede-4e3a-8740-20fb90ffdab2/JMSampleProcess
    [2011-04-20T08:33:12.458-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :load Loading InBound_jms.jca ..
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound Performing JCAEndpointActivation::prepareActivation for {PayloadType=TextMessage, UseMessageListener=false, DestinationName=jms/ReceiveQueue}
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::prepareActivation - Locating JCA Binding Component instance: SCA_AS11R1
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::initiateInboundJcaEndpoint - Creating and initializing inbound JCA endpoint for:[[
    endpoint='InBound'
    WSDL location='oramds:/deployed-composites/default/JMSSampleProj_rev1.0/InBound.wsdl'
    portType='Consume_Message_ptt'
    operation='Consume_Message'
    activation properties={PayloadType=TextMessage, UseMessageListener=false, DestinationName=jms/ReceiveQueue}
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::initiateInboundJcaEndpoint - Creating endpoint (0) for InBound
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::prepareActivation - Done preparing JCAEndpointActivation for Service 'InBound'
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :load Successfully loaded InBound_jms.jca
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :init Initializing InBound_jms.jca
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound JCAEndpointActivation::performActivation - Performing JCA Endpoint Activation, Endpoint Id='InBound'
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> InBound Performing endpoint activation (1) for InBound
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - endpointActivation for portType=Consume_Message_ptt, operation=Consume_Message
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj Creating new instance of Resource Adapter oracle.tip.adapter.jms.JmsResourceAdapter
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - starting Resource Adapter oracle.tip.adapter.jms.JmsResourceAdapter
    [2011-04-20T08:33:12.473-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JmsResourceAdapter_start: Jms Adapter started
    [2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JmsResourceAdapter_endpointActivation: Activating endpoint Endpoint_1
    [2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_start: Starting endpoint Endpoint_1
    [2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_run: Calling register...
    [2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> JMSSampleProj JCA Binding Component instance: SCA_AS11R1 - successfully completed endpointActivation for portType=Consume_Message_ptt, operation=Consume_Message
    [2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> [JMSSampleProj.InBound/1.0] :init Successfully initialized InBound_jms.jca
    [2011-04-20T08:33:12.520-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] JCABinding=> :defaultRevisionChanged - updated default revision to default/JMSSampleProj!1.0 for default/JMSSampleProj
    [2011-04-20T08:33:12.567-05:00] [soa_server1] [NOTIFICATION] [SOA-21538] [oracle.integration.platform.blocks.deploy.servlet] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] Removing temporary directory: C:\DOCUME~1\abhatika\LOCALS~1\Temp\1\sar_base_dir_1303306387379.
    [2011-04-20T08:33:12.567-05:00] [soa_server1] [NOTIFICATION] [SOA-21557] [oracle.integration.platform.blocks.deploy.servlet] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041f2,0] [APP: soa-infra] CompositeDeploymentServlet-----> completed deploying sca_JMSSampleProj_rev1.0.jar successfully. Time spent: 5.188 sec.
    [2011-04-20T08:33:13.036-05:00] [soa_server1] [WARNING] [] [oracle.soa.adapter] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: epm_admin] [ecid: 1351f73362dee8bb:-13137bc6:12f727dea12:-8000-00000000000041fd,0] [APP: soa-infra] JMSAdapter JMSSampleProj JmsDDEndpoint_onFailure: Unable to resolve 'jms.ReceiveQueue'. Resolved 'jms'

    Hi,
    Try targetting it to soa_server1 instead of admin server.

  • Dynamic configuration bean in JMS Adapter

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

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

  • JMS adapter: Adapter specific message attributes

    Hi,
    I have a synchronous SOAP to JMS (MQ series) scenario where I’m using sync/async bridge (without BPM).
    I need to correlate the message being put on JMS queue (JMS receiver adapter) and the response (JMS sender adapter).
    The “standard” receiver JMS adapter only allows the JMS correlation ID to be set to one of three different values (excluding NULL). 2 of these (reference and conversation ID) will be empty in my scenario, leaving me with only the XI message ID. This ID however exceeds the length of ie. the JMS correlation ID and thus isn’t suitable for correlating anything using the field JMS Correlation ID.
    NB: it is of no use to try and set the conversation ID at mapping time (using container object) since the changed value only is available during mapping execution.
    Surely one way of setting the conversation ID would be to use an adapter module in SOAP sender, but this is not an option. Also the sender system will not provide one either.
    Now the problem isn’t setting the JMS correlation ID dynamically at runtime (this is achieved without trouble using the dynamic configuration API with the key ‘DCJMSCorreleationID’). The problem is to actually have XI correlate the request with the response.
    Since the JMS collelation ID is smaller than the XI message ID and the conversation and reference ID isn’t available, what I figure is that I need to find a MQ message property to use and then use the ‘Set MSProperty to’ part instead – this property surely needs to be large enough to contain the XI message ID.
    So what I did was I looked in http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.amqwak.doc/js50938.htm
    where a list of fields in the message descriptor is available figuring I can just use one of these. Looking through the list I notice the field MDRQ (‘Name of reply queue’, 48-byte character string) should be able to hold the XI message ID. So I add ‘MDQR’ in the ‘Specify additional JMS message properties’ and set the ‘Java Type’ to String and also enter this field in the Correlation Setting of the receiver JMS adapter.
    Runtime:
    When looking in MDT I see:
    New JMS message will be correlated with the XI message. Correlation rule: XI_MESSAGEID, correlated property: JMS property MDRM, correlation value: 36158680-5a0c-11dc-8c14-000f203cd3c8
    I looks like a success! No data is however set in the field when looking at messages being put on MQ.
    If I increase the trace level of the JMS adapter I can see (in defaultTrace) the following:
    Cannot read the switch setting for property name DCJMSStringProperty0, switch name dynConfigDCJMSStringProperty0. It is switched off.
    What does this error mean?
    I have of course clicked ‘Use adapter Specific Message-Attributes’ and also the ‘Specify additional…’. In other words everything look ok in configuration.
    Since I’ve also put a check mark in ‘Fail if adapter specific message attributes is missing’ I can see that I successfully put a value (using dynamic conf. at mapping time) in the field... but still something isn’t right – the value of the property never reached MQ.
    Now I’ve tried with a couple of fields in the message descriptor from the previous URL. XI complains all the time.
    Anybody got some ideas?
    Best Regards,
    Daniel

    Hi Vijay,
    Thanks for your replay,as per your input i creted dynamic configuration method,
    i taget structure  luks like this
       <Data>
           <Mesage>
                 <gl_update>
                      <header>
                            <ean1>
                            <ean2>
                      </header>
                  <gl_update>
           <Message>
    i written UDF and mapped to header element gl_update,
    but i am getting  below error message in MONI
    SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_MM_ ffjms_</SAP:P1>
      <SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
      <SAP:P3>on: Cannot create target element /ns0:MT_jms_ _a</SAP:P3>
      <SAP:P4>sync_out/Data/Message/ GLUpdate. Values missi~</SAP:P4>
      <SAP:AdditionalText />
      <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_ ffjms_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:MT_jms_ asyncout/Data/Message/ GLUpdate. Values missi~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    i want to know i mapped to UDF to GL_Update is is correct, to which element i have to map.
    i think there is no prob with UDF,its executing ,giving warning messages
    help me on this,
    Regaards
    Raj

  • Correlation issue in JMS adapter - SYNC/ASYNC scenario without BPM

    Hi,
    I am working on a SYNC/ASYNC scenario with JMS adapter without using BPM. My scenario is SOAP<>PI>JMS. I configured the interface as below:
    1. SOAP Sender channel
    2. JMS Receiver Channel writing to Queue A.
         Module used:      a. RequestOneWayBean
                   b. WaitResponseBean
         Correlation Settings:
                   a. Set JMS Correlation ID to "XI Message ID"
                   b. Store JMS CorrelationID of request (Checked)
                   c. Set JMS Property to "JMS Correlation Id"
                   d. Value = "XI MEssage ID"
    3. JMS Sender channel reading from queue B ( I am exporting the message from queue A and importing into queue B)
         Module used:      a. NotifyResponseBean
         Correlation Settings:
                   a. Set XI MEssage Id to "GUID"
                   b. Set XI Conversation ID to "Stored JMS COrrelationID of Request"
    I can see the cid in the message from queue A. But I observed thhat the header format of the message in Queue A is "MQSTR".
    ISSUE:
    1. While writing the message to queue A, below adapter log details(part b) concerned me:
         a. Message '8747a7c2-2b06-11df-8055-005056a70ed6' successfully processed by channel
         b. Could not create acknowledgements for message '8747a7c2-2b06-11df-8055-005056a70ed6'
    I am not sure why I am receiving the message that "  could not create acknowledgements"
    2. While reading the message from the sender channel,I consistently get the error message as below:
         a. XI message ID corresponding to JMS message with ID 'ID:414d51205341504449442e514d202020c67b954b20005602'
              will be created as a new GUID with value '21bca916-424f-41f6-3347-c71090392b58'
         b. Error while processing message '21bca916-424f-41f6-3347-c71090392b58';  detailed error description:
              com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: found no correlation ID: RecoverableException:
              found no correlation ID at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
    Below are the blogs which I have already gone through:
    1. JMS Synchronous Scenario without BPM - Correlation Settings and Transactional JMS Session
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b028f6f6-7da5-2a10-19bd-cf322cf5ae7b
    2. Note: 1086303
    3. Sync / Async Bridge without BPM
    In the note, they mentioned something about header being "MQRFH2". BUt in our case, the header is "MSSTR". Not sure whether it makes any difference.
    Please help.
    Edited by: GP on Mar 9, 2010 4:24 AM

    Hi,
    detailed error description:
    com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: found no correlation ID: RecoverableException:
    found no correlation ID at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
    This error would generally arose when there are multiple messages, got stuck in the outbound queue. Try to stop both the sender and receiver JMS comunication channels and clear both the inbound and outbound queues.
    Once all the messages in the queue are cleraed, try posting the message again.
    Regards,
    Swetha.

Maybe you are looking for

  • Creating data in a many-to-many-relationship

    Hello, we really have problems in implementing a JClient dialog based on BC4J for creating data in a many to many relationship - especially with cascade delete on both sides. Simplified our tables look like: create table A_TABLE A_ID VARCHAR2(5) not

  • Window IE 7 and Wifi

    I am running windows 7 on my Mac Book Pro with bootcamp.  However, I think I need to be able to run IE in order to download the Microsoft Office that I purchased on-line.  I can't get IE to reconized my wifi network.  I had no problems with Safari an

  • TS4449 When i make call from iphone,loudspeaker is being enabled automatically and not able to  hear any sound ..

    When i make call from iphone,loudspeaker is being enabled automatically and not able to  hear any sound .. And some time it's worked...

  • SQL query....need help again

    Actor (Aname: varchar(40), Ano: varchar(6)) Ano is pk Movie (Mname: varchar(40),mno: varchar(8)) Mno is pk PlayIn (Ano, Mno, Pay: Integer) Ano and Mno are fk referencing Acotr and Movie respectively. Actor(Aname, Ano) A Bingo, A1 B Castro, A2 C Katie

  • Problem with STO from non-WM to WM-HU

    Hi, We have found out recently that we cannot move materials from non-WM to WM-HU storage locations with STO (313-315). When we are trying to post 313 from non-WM storage location, system gives error "ILN basis no. for plant XXXX, stor.locat. XXXX or