JMS--PI--WSDL

Experts,
JMS>PI>WSDL
JMS adapter sends a message,PI process it  and sends to WSDL  file ( Sync) thru SOAP adapter.  the WSDL response need to  dump thru file adapter.
Any good weblog  and your suggestions.
Thanks
Edward

JMS adapter sends a message,PI process it and sends to WSDL file ( Sync) thru SOAP adapter.
the WSDL response need to dump thru file adapter
Check this design Approach:
JMS -
> XI -
> WSDL ...............Flow is Async with the req message of wsdl in the MT of IN Async MI
WSDL -
> XI -
> FILE ...........Flow is async with the response msg of WSDL in the MT of OB Async
MI
both designs implemented under same Namespace in IR and same Configuration scenario of ID.
Regards,
Abhishek.
Edited by: abhishek salvi on Jun 2, 2009 9:24 AM

Similar Messages

  • How to define JMS-Adapter WSDL?

    Is there somewhere a short guide on how to define a WSDL für accessing
    a JMS queue through an JMS adapter?
    How do I have to define the XSD for the payload of a JMS message?
    Peter

    Srini,
    the URL format u need to give while creating webservice is ....
    <b>http://url:port/XISOAPAdapter/MessageServlet?channel=:service:channel</b>
    here
    service= <b>sender business ser</b>vice /<b>business system</b> whatever u have used.
    channel= sender communication channel
    for example
    <b>http://xyz.com:59600/XISOAPAdapter/MessageServlet?channel=:BS100:Sender_SOAP</b>
    BS100= sender business system
    SEnder_SOAP = sender communication channel
    hope u r clear now!!!!
    regrads
    biplab
    Use a Good Subject Line, One Question Per Posting - Award Points

  • Having multiple service operations in a single JMS adapter best practice

    Hi All,
    I am using JDeveloper and SOA Suite 11.1.1.6. I need to read from multiple JMS Topics and transform and enhance the messages through the Mediator and then persist into Database.
    My question is
    What is the best practice to consume from multiple topics, Should I configure separate JMS adapter for each of the Topic destination
    OR
    have a single JMS adapter with multiple operations by manually changing the JMS adapter wsdl and jca file?
    I find cannot have
    Please suggest.
    Thanks in advance
    Edited by: user5108636 on 15/05/2013 11:36

    Hi Vijay,
    did you actually test this? When I finish creating a DBAdapter, there is a operation present. Then when I click edit again on the DBAdapter, and I create another select, when I finish only the first operation is gone, and I can only see the one I've created via the last edit.
    I dont understand your reply. Can I have two operations, each one with select underneath, in the same adapter?
    Edited by: user13604541 on Jan 30, 2012 11:19 AM

  • Configuring JMS adapter

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

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

  • JMS  publsig problem

    Hi,
    I am trying to develope a BPEL process which publish jms topic to oc4j jms jms/demoTopic.there I am getting error over there. Below is the error msg
    file:/C:/OraBPELPM_1/integration/orabpel/domains/default/tmp/.bpel_JMSTest1_1.0.jar/JMSSrv.wsdl [ Produce_Message_ptt::Produce_Message(JMSTest1ProcessRequest) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: ERRJMS_MSGPROD_CONSTR_ERR. Unable to construct MessageProducer. ; nested exception is: ORABPEL-12164 ERRJMS_MSGPROD_CONSTR_ERR. Unable to construct MessageProducer. Please examine the log file to determine the problem.
    below is the log
    com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is 2e6d902e744f9cf2:2f48d2:108e104ba20:-7ffa. Please check the process instance for detail.
         at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:108)
         at IDeliveryBean_StatelessSessionBeanWrapper22.request(IDeliveryBean_StatelessSessionBeanWrapper22.java:288)
         at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:101)
         at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:65)
         at ngDoInitiate.jspService(_ngDoInitiate.java:255)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810)
         at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121)
         at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267)
         at displayProcess.jspService(_displayProcess.java:658)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322)
         at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:220)
         at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:138)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:649)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is 2e6d902e744f9cf2:2f48d2:108e104ba20:-7ffa. Please check the process instance for detail.
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:523)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:425)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:132)
         at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:93)
         ... 29 more
    oc4j-ra.xml entry is below
    <connector-factory location="eis/Jms/JmsPublishAdapter" connector-name="Jms Adapter">
              <config-property name="connectionFactoryLocation" value="jms/TopicConnectionFactory"/>
              <config-property name="factoryProperties" value=""/>
              <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
              <config-property name="isTopic" value="true"/>
              <config-property name="isTransacted" value="false"/>
              <config-property name="username" value="admin"/>
              <config-property name="password" value="welcome"/>
         </connector-factory>
    your help to find a soln will be higly appreciated.

    Hi,
    Below is the log you have requested for
    <2006-01-20 10:01:09,673> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> registered wsdl at
    http://TCS052539:9700/orabpel/default/JMSTest1/1.0/_JMSTest1.wsdl
    <2006-01-20 10:01:09,673> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> got wsdl at:
    http://TCS052539:9700/orabpel/default/JMSTest1/1.0/_JMSTest1.wsdl
    <2006-01-20 10:01:09,773> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> registered wsdl at
    C:\OraBPELPM_1\integration\orabpel\domains\default\tmp\.bpel_JMSTest1_1.0.jar\JMSTest1.wsdl
    <2006-01-20 10:01:09,773> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> got wsdl at:
    C:\OraBPELPM_1\integration\orabpel\domains\default\tmp\.bpel_JMSTest1_1.0.jar\JMSTest1.wsdl
    <2006-01-20 10:01:09,843> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> registered wsdl at
    C:\OraBPELPM_1\integration\orabpel\domains\default\tmp\.bpel_JMSTest1_1.0.jar\JMSSrv.wsdl
    <2006-01-20 10:01:09,843> <DEBUG> <default.collaxa.cube.ws> <WSDLManager::getWSDL> got wsdl at:
    C:\OraBPELPM_1\integration\orabpel\domains\default\tmp\.bpel_JMSTest1_1.0.jar\JMSSrv.wsdl
    <2006-01-20 10:01:15,491> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> operation: Produce_Message,
    partnerLink: <partnerLink name="JMSPartner"
    partnerLinkType="{http://xmlns.oracle.com/pcbpel/adapter/jms/JMSSrv/}Produce_Message_plt">
    <myRole name="null">
    <ServiceName>null</ServiceName>
    <PortType>null</PortType>
    <Address>null</Address>
    </myRole>
    <partnerRole
    name="Produce_Message_role">
    <ServiceName>null</ServiceName>
    <PortType>{http://xmlns.oracle.com/pcbpel/adapter/jms/JMSSrv/}Produce_Message_ptt</PortType>
    <Address>null</Address>
    </partnerRole>
    <conversationId>bpel://localhost/default/JMSTest1~1.0/801-BpInv0-BpSeq0.3-3</conversationId>
    <properties>{}</properties>
    </partnerLink>
    <2006-01-20 10:01:15,491> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> def is
    file:/C:/OraBPELPM_1/integration/orabpel/domains/default/tmp/.bpel_JMSTest1_1.0.jar/JMSSrv.wsdl
    <2006-01-20 10:01:15,501> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> opName=Produce_Message,
    parnterLink=<partnerLink name="JMSPartner"
    partnerLinkType="{http://xmlns.oracle.com/pcbpel/adapter/jms/JMSSrv/}Produce_Message_plt">
    <myRole name="null">
    <ServiceName>null</ServiceName>
    <PortType>null</PortType>
    <Address>null</Address>
    </myRole>
    <partnerRole
    name="Produce_Message_role">
    <ServiceName>{http://xmlns.oracle.com/pcbpel/adapter/jms/JMSSrv/}JMSSrv</ServiceName>
    <PortType>{http://xmlns.oracle.com/pcbpel/adapter/jms/JMSSrv/}Produce_Message_ptt</PortType>
    <Address>null</Address>
    </partnerRole>
    <conversationId>bpel://localhost/default/JMSTest1~1.0/801-BpInv0-BpSeq0.3-3</conversationId>
    <properties>{}</properties>
    </partnerLink>
    <2006-01-20 10:01:15,662> <INFO> <default.collaxa.cube.ws> <AdapterFramework::Outbound>
    file:/C:/OraBPELPM_1/integration/orabpel/domains/default/tmp/.bpel_JMSTest1_1.0.jar/JMSSrv.wsdl [
    Produce_Message_ptt::Produce_Message(JMSTest1ProcessRequest) ] - Using JCA Connection Pool - max size = <unbounded>
    <2006-01-20 10:01:15,672> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound>
    file:/C:/OraBPELPM_1/integration/orabpel/domains/default/tmp/.bpel_JMSTest1_1.0.jar/JMSSrv.wsdl [
    Produce_Message_ptt::Produce_Message(JMSTest1ProcessRequest) ] - Looking up Resource Adapter JDNI location
    'eis/Jms/JmsPublishAdapter'
    <2006-01-20 10:01:15,672> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound>
    JMSConnectionFactoryFactory_getConnectionFactory: looking up 'jms/TopicConnectionFactory'
    <2006-01-20 10:01:15,982> <INFO> <default.collaxa.cube.ws> <JMSAdapter::Outbound> Created new managed connection for JMS user
    admin
    <2006-01-20 10:01:15,982> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JmsSpiLocalTransactionImpl_<init>: Not
    transacted
    <2006-01-20 10:01:16,012> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Instantiating outbound JCA
    interactionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
    <2006-01-20 10:01:16,012> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Populating outbound JCA
    interactionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec with properties: {OpaqueSchema=false, TimeToLive=0,
    DeliveryMode=Non-Persistent, PayloadType=TextMessage, DestinationName=jms/demoQueue}
    <2006-01-20 10:01:16,082> <WARN> <default.collaxa.cube.ws> <AdapterFramework::Outbound>
    file:/C:/OraBPELPM_1/integration/orabpel/domains/default/tmp/.bpel_JMSTest1_1.0.jar/JMSSrv.wsdl [
    Produce_Message_ptt::Produce_Message(JMSTest1ProcessRequest) ] - The jca:header element
    oracle.tip.adapter.fw.wsif.jca.JCAHeader@27de24<jca:header message=null:OutboundHeader_msgoutboundHeader/> does not match the
    outbound headers provided in {}
    <2006-01-20 10:01:16,142> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JmsCciLocalTransactionImpl_<init>: Not
    transacted
    <2006-01-20 10:01:16,142> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound>
    file:/C:/OraBPELPM_1/integration/orabpel/domains/default/tmp/.bpel_JMSTest1_1.0.jar/JMSSrv.wsdl [
    Produce_Message_ptt::Produce_Message(JMSTest1ProcessRequest) ] - Starting JCA LocalTransaction
    <2006-01-20 10:01:16,142> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound>
    file:/C:/OraBPELPM_1/integration/orabpel/domains/default/tmp/.bpel_JMSTest1_1.0.jar/JMSSrv.wsdl [
    Produce_Message_ptt::Produce_Message(JMSTest1ProcessRequest) ] - Invoking JCA outbound Interaction
    <2006-01-20 10:01:16,152> <INFO> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JMSMessageProducer_ctor: Constructed
    MessageProducer for destination jms/demoQueue (payload = 1)
    <2006-01-20 10:01:16,152> <INFO> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JMSMessageProducer_init: Creating
    MessageProducer for destination jms/demoQueue (payload = 1)
    <2006-01-20 10:01:16,152> <ERROR> <default.collaxa.cube.ws> <JMSAdapter::Outbound> Nested Exception
    <2006-01-20 10:01:16,152> <ERROR> <default.collaxa.cube.ws> <JMSAdapter::Outbound>
    ORABPEL-12143
    ERRJMS_DEST_NOT_TOPIC.
    Destination "jms/demoQueue" is not a topic.
    Please examine the log file to determine the problem.
         at oracle.tip.adapter.jms.JMS.JMSDestination.getTopic(JMSDestination.java:99)
         at oracle.tip.adapter.jms.JMS.JMSConnection.createProducer(JMSConnection.java:344)
         at oracle.tip.adapter.jms.JMS.JMSConnection.createProducer(JMSConnection.java:328)
         at oracle.tip.adapter.jms.JMS.JMSMessageProducer.createProducer(JMSMessageProducer.java:157)
         at oracle.tip.adapter.jms.JMS.JMSMessageProducer.init(JMSMessageProducer.java:126)
         at oracle.tip.adapter.jms.outbound.JmsProducer.init(JmsProducer.java:94)
         at oracle.tip.adapter.jms.outbound.JmsProducerManager.getProducer(JmsProducerManager.java:64)
         at oracle.tip.adapter.jms.JmsInteraction.executeProduce(JmsInteraction.java:178)
         at oracle.tip.adapter.jms.JmsInteraction.execute(JmsInteraction.java:146)
         at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:463)
         at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:653)
         at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:439)
         at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:310)
         at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:184)
         at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601)
         at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:316)
         at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:179)
         at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3396)
         at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1905)
         at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:100)
         at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:185)
         at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5408)
         at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1300)
         at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:117)
         at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:146)
         at
    ICubeEngineLocalBean_StatelessSessionBeanWrapper0.syncCreateAndInvoke(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java:
    483)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:492)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:425)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:132)
         at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:93)
         at IDeliveryBean_StatelessSessionBeanWrapper22.request(IDeliveryBean_StatelessSessionBeanWrapper22.java:288)
         at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:101)
         at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:65)
         at ngDoInitiate.jspService(_ngDoInitiate.java:255)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810)
         at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121)
         at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267)
         at displayProcess.jspService(_displayProcess.java:658)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322)
         at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:220)
         at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:138)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:649)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
         at java.lang.Thread.run(Thread.java:534)
    <2006-01-20 10:01:16,162> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound>
    file:/C:/OraBPELPM_1/integration/orabpel/domains/default/tmp/.bpel_JMSTest1_1.0.jar/JMSSrv.wsdl [
    Produce_Message_ptt::Produce_Message(JMSTest1ProcessRequest) ] - Could not invoke operation 'Produce_Message' against the
    'JMSAdapter' due to:
    ORABPEL-12164
    ERRJMS_MSGPROD_CONSTR_ERR.
    Unable to construct MessageProducer.
    Please examine the log
    file to determine the problem.
         at oracle.tip.adapter.jms.JMS.JMSMessageProducer.init(JMSMessageProducer.java:132)
         at oracle.tip.adapter.jms.outbound.JmsProducer.init(JmsProducer.java:94)
         at oracle.tip.adapter.jms.outbound.JmsProducerManager.getProducer(JmsProducerManager.java:64)
         at oracle.tip.adapter.jms.JmsInteraction.executeProduce(JmsInteraction.java:178)
         at oracle.tip.adapter.jms.JmsInteraction.execute(JmsInteraction.java:146)
         at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:463)
         at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:653)
         at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:439)
         at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:310)
         at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:184)
         at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601)
         at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:316)
         at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:179)
         at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3396)
         at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1905)
         at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:100)
         at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:185)
         at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5408)
         at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1300)
         at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.createAndInvoke(CubeEngineBean.java:117)
         at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.syncCreateAndInvoke(CubeEngineBean.java:146)
         at
    ICubeEngineLocalBean_StatelessSessionBeanWrapper0.syncCreateAndInvoke(ICubeEngineLocalBean_StatelessSessionBeanWrapper0.java:
    483)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:492)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:425)
         at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:132)
         at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:93)
         at IDeliveryBean_StatelessSessionBeanWrapper22.request(IDeliveryBean_StatelessSessionBeanWrapper22.java:288)
         at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:101)
         at com.oracle.bpel.client.delivery.DeliveryService.request(DeliveryService.java:65)
         at ngDoInitiate.jspService(_ngDoInitiate.java:255)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810)
         at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121)
         at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267)
         at displayProcess.jspService(_displayProcess.java:658)
         at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
         at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347)
         at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
         at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322)
         at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:220)
         at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:138)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:649)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:270)
         at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: ORABPEL-12143
    ERRJMS_DEST_NOT_TOPIC.
    Destination "jms/demoQueue" is not a topic.
    Please examine the log file to
    determine the problem.
         at oracle.tip.adapter.jms.JMS.JMSDestination.getTopic(JMSDestination.java:99)
         at oracle.tip.adapter.jms.JMS.JMSConnection.createProducer(JMSConnection.java:344)
         at oracle.tip.adapter.jms.JMS.JMSConnection.createProducer(JMSConnection.java:328)
         at oracle.tip.adapter.jms.JMS.JMSMessageProducer.createProducer(JMSMessageProducer.java:157)
         at oracle.tip.adapter.jms.JMS.JMSMessageProducer.init(JMSMessageProducer.java:126)
         ... 55 more
    <2006-01-20 10:01:16,162> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound>
    file:/C:/OraBPELPM_1/integration/orabpel/domains/default/tmp/.bpel_JMSTest1_1.0.jar/JMSSrv.wsdl [
    Produce_Message_ptt::Produce_Message(JMSTest1ProcessRequest) ] - Rolling back JCA LocalTransaction
    <2006-01-20 10:01:16,162> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happened:
    file:/C:/OraBPELPM_1/integration/orabpel/domains/default/tmp/.bpel_JMSTest1_1.0.jar/JMSSrv.wsdl [
    Produce_Message_ptt::Produce_Message(JMSTest1ProcessRequest) ] - WSIF JCA Execute of operation 'Produce_Message' failed due
    to: ERRJMS_MSGPROD_CONSTR_ERR.
    Unable to construct MessageProducer.
    ; nested exception is:
         ORABPEL-12164
    ERRJMS_MSGPROD_CONSTR_ERR.
    Unable to construct MessageProducer.
    Please examine the log file to determine the problem.
    Below is the JMS Adapter wsdl(JMSSrv.wsdl)
    <definitions
    name="JMSSrv"
    targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/jms/JMSSrv/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/jms/JMSSrv/"
    xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"
    xmlns:imp1="http://xmlns.oracle.com/JMSTest1"
    xmlns:hdr="http://xmlns.oracle.com/pcbpel/adapter/jms/"
    >
    <import namespace="http://xmlns.oracle.com/JMSTest1" location="JMSTest1.wsdl"/>
    <import namespace="http://xmlns.oracle.com/pcbpel/adapter/jms/" location="jmsAdapterOutboundHeader.wsdl"/>
    <message name="JMSTest1ProcessRequest_msg">
    <part name="JMSTest1ProcessRequest" element="imp1:JMSTest1ProcessRequest"/>
    </message>
    <portType name="Produce_Message_ptt">
    <operation name="Produce_Message">
    <input message="tns:JMSTest1ProcessRequest_msg"/>
    </operation>
    </portType>
    <binding name="Produce_Message_binding" type="tns:Produce_Message_ptt">
    <jca:binding />
    <operation name="Produce_Message">
    <jca:operation
    InteractionSpec="oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec"
    DestinationName="jms/demoQueue"
    DeliveryMode="Non-Persistent"
    TimeToLive="0"
    PayloadType="TextMessage"
    OpaqueSchema="false" >
    </jca:operation>
    <input>
    <jca:header message="hdr:OutboundHeader_msg" part="outboundHeader"/>
    </input>
    </operation>
    </binding>
    <service name="JMSSrv">
    <port name="Produce_Message_pt" binding="tns:Produce_Message_binding">
    <jca:address location="eis/Jms/JmsPublishAdapter" />
    </port>
    </service>
    <plt:partnerLinkType name="Produce_Message_plt" >
    <plt:role name="Produce_Message_role" >
    <plt:portType name="tns:Produce_Message_ptt" />
    </plt:role>
    </plt:partnerLinkType>
    </definitions>
    Thaking youn for your cooperation.
    Regards
    Moni

  • Problem correlating separate JMS MQs

    Hi there - I am testing out a 10.1.2 BPEL process that correlates OK between Produce and Consume messages to the same test queue (IBM MQ) via the JMS Adapter.
    We're deploying to BPEL 10.1.2 deployed into WebSphere 5.x using MQ 5.3.
    This test uses a correlation set based on an Xpath query into a SOAP payload (client requirement is SOAP messages on Qs). Its working for our initial test as above.
    As soon as I introduce separate queues for the Produce and Consume messages (i.e produce to one Queue, a background process returns a reply message to a second Queue, which I want to then consume), the process no longer correlates, even though I'm using the same correlation set and I know the correlation data will be in the messages. All we did was change the DestinationName(s) in the JMS PartnerLink WSDL files and redeploy.
    Any ideas why this might be happening?
    Thanks in advance.
    Dennis

    Hi there - I am testing out a 10.1.2 BPEL process that correlates OK between Produce and Consume messages to the same test queue (IBM MQ) via the JMS Adapter.
    We're deploying to BPEL 10.1.2 deployed into WebSphere 5.x using MQ 5.3.
    This test uses a correlation set based on an Xpath query into a SOAP payload (client requirement is SOAP messages on Qs). Its working for our initial test as above.
    As soon as I introduce separate queues for the Produce and Consume messages (i.e produce to one Queue, a background process returns a reply message to a second Queue, which I want to then consume), the process no longer correlates, even though I'm using the same correlation set and I know the correlation data will be in the messages. All we did was change the DestinationName(s) in the JMS PartnerLink WSDL files and redeploy.
    Any ideas why this might be happening?
    Thanks in advance.
    Dennis

  • Corelation not getting compiled in BPEL

    Hi,
    I have a BPEL ( V 1.1, one-way ) that uses corelation.
    I have created the corelation,added property and then property alias and evrything is visble in structure window.
    But when i try to compile it gives the following error.
    [scac] error: in GDIPExaminationArchingProcess.bpel(129): correlation property "{http://xmlns.oracle.com/GDIP/GDIPExaminationArchingProcess/GDIPExaminationArchingProcess/correlationset}CorrelationSetYASEER_property" of correlationSet "CorrelationSetYASEER" is not defined
         [scac] error: in GDIPExaminationArchingProcess.bpel(180): correlation set "CorrelationSetYASEER" cannot be used in this <correlation>, because property "{http://xmlns.oracle.com/GDIP/GDIPExaminationArchingProcess/GDIPExaminationArchingProcess/correlationset}CorrelationSetYASEER_property  of this correlation set is not associated with the message "{http://xmlns.oracle.com/Biller_Yesser_Integration/BillLoadJMSProducer/BillLoadJMSProducer}BillLoadJMSProducerResponseMessage"
    Please let me know if someone has solution.
    Thanks,
    Lalit

    Looking at the error, I suppose, the correlation set is defined in the BPEL process and it is associated with the JMS adapter invoke/receive? Then, probably you may need to also import the namespace of the correlation set from the BPEL process wsdl to the JMS adapter wsdl (with the <import namespace="..." location="..."/> tag).

  • How to get contents of Soap Over JMS web service's wsdl file

    Hi,
    Is there a way to get the soap over jms webservice's wsdl file in browser? if yes please provide me the details how to get it.
    OR how can i get the contensts of WSDL file for soap over jms wsdl file.
    thanks in advance.

    I have the same question ("Assuming I can generate a wsdl file, can I recreate the SOAP request message from the WSDL file automatically (that matches the original request, which is hand build by me?)")
    Have you already found an answer to this?

  • 'Payload not Serializable' with custom WSDL data types in message-style web service

    I'm implementing a message-style web service which publishes to a JMS Queue.
    I had the web service built and deployed, but noticed that the "sendRequest" message's
    part was of type "xsd:anyType." This is not specific enough for our interface,
    since it is externally facing and needs to describe the object we're expecting
    on the back end.
    So I replaced xsd:anyType with mynamespace:MyType, which is defined as a complex
    type in the same WSDL document.
    My problem is that when I test the web service with the new WSDL (using the client.jar),
    I get a server-side exception from the DestinationSendAdapter.doPost() method.
    The exception reads:
    javax.servlet.ServletException: Payload not Serializable
    at weblogic.soap.server.servlet.DestinationSendAdapter.doPost(DestinationSendAdapter.java:129)
    The domain object ('classic' JavaBean) that it should map to on the server side
    extends a class that implements Serializable, so it should inherit the trait.
    So my questions are:
    1) Did I properly go about trying to restrict the object type that gets sent to
    my Destination?
    2) If no, what is the correct way? If yes, why am I receiving the Payload not
    Serializable error if the domain object implements Serializable?
    Thanks in advance.

    Resolved:
    Apparently this is the right approach, as it boiled down to a classpath issue
    on the client-side. Thanks anyway.

  • Error while reading wsdl file

    I created and deployed a BPEL process with a JMS adapter and DB adapter.
    I have tested this and it works fine.
    After a few days, I try to open the project and the BPEL process, and click on the DB
    adapter and it throws an exception on the designer :
    "Error while reading wsdl file ... (wsdl file name) NULL Exception"
    This is hard to debug as the exception does not provide any info, NULL.
    This has happened several times for my project. The next time the JMS adapter hit the
    same exception while opening on designer. This one I notice happened after I imported
    a new schema file (xsd) into the BPEL process.
    Only way around that I have for this currently is to delete and recreate the adapters, which as time
    consuming as I have to re-create and re-assign a lot of the activities.
    Has anyone encountered this and is there a way to fix this without deleting/recreating the adapters ?
    Thanks.

    I experienced the same issue and found the cause and a workaround;
    "Error while reading wsdl file …. Exception: null"
    http://www.petervannes.nl/files/b7c08911ce3cde3677e2182bbc5f032a-47.php
    Edited by: 944333 on Jul 3, 2012 10:24 PM

  • Error in using the JMS Adater using weblogic queue

    I am using weblogic queue in jms adapter to queue the data. i configured the server.xml
         <shared-library name="oracle.weblogic" version="10.1.3">
              <code-source path="D:\product\10.1.3.1\OracleAS_5\jdk\lib\weblogic.jar"/>
         </shared-library>
    I got the following error. Any Suggestions?
    file:/D:/product/10.1.3.1/OracleAS_5/bpel/domains/default/tmp/.bpel_OSM_OrderRequest_2.0_c68a29fd8af11327e1a8892e8de5a6bb.tmp/Sample.wsdl [ Produce_Message_ptt::Produce_Message(orderRequestMessage) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.; nested exception is:
         oracle.classloader.util.AnnotatedClassNotFoundException:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.; nested exception is:
         org.collaxa.thirdparty.apache.wsif.WSIFException: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.; nested exception is:
         oracle.classloader.util.AnnotatedClassNotFoundException:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.
    </summary>
    </part>
    -<part name="detail">
    <detail>
    org.collaxa.thirdparty.apache.wsif.WSIFException: Could not instantiate InteractionSpec oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec due to:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.; nested exception is:
         oracle.classloader.util.AnnotatedClassNotFoundException:
         Missing class: oracle.tip.adapter.jms.outbound.JmsProduceInteractionSpec
         Dependent class: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA
         Loader: oracle.bpel.common:10.1.3
         Code-Source: /D:/product/10.1.3.1/OracleAS_5/bpel/lib/orabpel.jar
         Configuration: <code-source> in /D:/product/10.1.3.1/OracleAS_5/j2ee/oc4j_soa/config/server.xml
    This load was initiated at orabpel.root:0.0.0 using the Class.forName() method.
    The missing class is not available from any code-source or loader in the system.

    I am able to fix this error by copying "JmsAdapter.jar" to "applib" directory of oc4j_soa.
    I was getting a new error.
    +"Missing class: oracle.tip.adapter.api.TranslationAware+
    +     Dependent class: oracle.tip.adapter.jms.JmsInteractionSpec+
    +     Loader: global.libraries:1.0+
    +     Code-Source: /D:/SOA1013/j2ee/oc4j_soa/applib/JmsAdapter.jar+
    +     Configuration: <code-source> in /D:/SOA1013/j2ee/oc4j_soa/config/server.xml+
    +The missing class is available from the following locations:+
    +     1. Code-Source: /D:/SOA1013/bpel/lib/orabpel.jar (from <code-source> in /D:/SOA1013/j2ee/oc4j_soa/config/server.xml)+
    +     This code-source is available in loader oracle.bpel.common:10.1.3."+
    But managed it to fix it by copying "orabpel.jar" to "applib" directory.
    We need to restart OC4J once we copy the JAR files.
    regards,
    S.Vasanth Kumar.

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

  • BPEL process failing in many instances due to JMS performance issue...

    Hi All,
    We are using a JMS adapter as partner link in a BPEL process to produce messages to JMS Queue.
    We are getting an error while producing a message to a JMS Queue.
    The error comes for 1 or 2 instances among 5 to10 intsances. (all these instances ran with in 1 or 2 seconds).
    We are using Oracle 10G SOA suite.
    This error is getting in the Production environment.
    The error is as follows (took error from server log).
    Failed to handle dispatch message ... exception ORABPEL-05002
    Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
    messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
    parts: {{summary=file:/sw/appaia/product/SOA/bpel/domains/default/tmp/.bpel_CurrencyExchangeListEbizJMSProducer_1.0_4ec528ec93a8a6ff0278fab9701dcc71.tmp/CurrencyExchangeListEbizJMSProducerV1.wsdl [ Produce_Message_ptt::Produce_Message(OutputParameters) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection.
    file:/sw/appaia/product/SOA/bpel/domains/default/tmp/.bpel_CurrencyExchangeListEbizJMSProducer_1.0_4ec528ec93a8a6ff0278fab9701dcc71.tmp/CurrencyExchangeListEbizJMSProducerV1.wsdl [ Produce_Message_ptt::Produce_Message(OutputParameters) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: oracle.j2ee.connector.proxy.ProxyInterceptException: javax.resource.ResourceException: RollbackException: Transaction has been marked for rollback: null [Caused by: RollbackException: Transaction has been marked for rollback: null]
    ; nested exception is:
    ORABPEL-12511
    Adapter Framework unable to create outbound JCA connection.
    I tried the below JMS tunings with differnt combination, but no improvem
    Please let me know if any other logs or any other information is required.
    Thanks,
    Pershad

    One of the values in the oc4j-ra.xml has the below values:
    <connector-factory location="OracleASjms/MyXAQCF" connector-name="OracleASjms">
              <config-property name="jndiLocation" value="jms/XAQueueConnectionFactory"/>
              <config-property name="autoCloseSession" value="false"/>
              <connection-pooling use="private">
                   <property name="waitTimeout" value="300" />
                   <property name="scheme" value="fixed_wait" />
                   <property name="maxConnections" value="50" />
                   <property name="minConnections" value="0" />
              </connection-pooling>
              <security-config use="principal-mapping-entries">
                   <principal-mapping-entries>
                        <principal-mapping-entry>
                             <initiating-user>servletuser</initiating-user>
                             <res-user>jmsuser</res-user>
                             <res-password>-&gt;jmsuser</res-password>
                        </principal-mapping-entry>
                   </principal-mapping-entries>
              </security-config>
              <connectionfactory-interface>javax.jms.XAQueueConnectionFactory</connectionfactory-interface>
         </connector-factory>
    Where do we need to change ?
    Please suggest .
    Thanks

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

  • How to configure the integration BPEL x JMS on oracle aplication server

    follwing the error
    <remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>null</code>
    </part><part name="summary"><summary>file:/u05/bpel/bpel/domains/default/tmp/.bpel_BPELxxBEA_1.0_fce047d117b03b6f174defa6316f81cd.tmp/jms.wsdl [ Produce_Message_ptt::Produce_Message(item) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection.
    file:/u05/bpel/bpel/domains/default/tmp/.bpel_BPELxxBEA_1.0_fce047d117b03b6f174defa6316f81cd.tmp/jms.wsdl [ Produce_Message_ptt::Produce_Message(item) ] - : 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 JMSConnectionTest neither through JNDI nor instantiate it as a Java class [Caused by: weblogic.jndi.WLInitialContextFactory]
    Please examine the log file to determine the problem.
    [Caused by: weblogic.jndi.WLInitialContextFactory]
    ; nested exception is:
         ORABPEL-12511
    Adapter Framework unable to create outbound JCA connection.
    file:/u05/bpel/bpel/domains/default/tmp/.bpel_BPELxxBEA_1.0_fce047d117b03b6f174defa6316f81cd.tmp/jms.wsdl [ Produce_Message_ptt::Produce_Message(item) ] - : 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 JMSConnectionTest neither through JNDI nor instantiate it as a Java class [Caused by: weblogic.jndi.WLInitialContextFactory]
    Please examine the log file to determine the problem.
    [Caused by: weblogic.jndi.WLInitialContextFactory]
    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>
    bpel cook book says on pag 143 for put this on my oc4j-ra.xml
    <connector-factory location="eis/wljms/Queue" connector-name="Jms Adapter">
         <config-property name="connectionFactoryLocation"
                             value="com.seebeyond.jms.client.STCTopicConnectionFactory"/>
         <config-property name="factoryProperties"
                             value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://acom06:8888;java.naming.security.principal=oc4jadmin;java.naming.security.credentials=welcome123"/>
         <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>
    <connector-factory location="eis/wljms/Topic" connector-name="Jms Adapter">
         <config-property name="connectionFactoryLocation"
                             value="com.seebeyond.jms.client.STCTopicConnectionFactory"/>
         <config-property name="factoryProperties"
                             value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://acom06:8888;java.naming.security.principal=oc4jadmin;java.naming.security.credentials=welcome123"/>
         <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
         <config-property name="isTopic" value="true"/>
         <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>
    where..
    acom06 = my server
    8888 = my port
    oc4jadmin = root user
    welcome123 = pass
    and put a weblogic.jar on
    /j2ee/acom06/connectors/JmsAdapter/JmsAdapter
    what else I have to do ???
    God bless all

    Hi, Swarup:
    Thanks for your reply.
    The reality here is that we could not get solid support from BSAIS team, we came to many situations that we have to search around and tell them how to do the job like this (They are all afraid of Java Stack
    I will keep search, if you have detailed information how to and where to configure those parameters, please let me know.
    Regards!
    Liang

Maybe you are looking for

  • Rendering to wrong drive- invisible?

    3:05PM I have all rendering, capture, etc going to my 300GB 2nd drive on my SATA bus (G5). Everytime I render, my boot drive gets smaller and smaller. THere are NO documents in the FCP Documents folder in my user folder (/user/Documents/Final Cut Pro

  • HTTP Status 401 error download sdk

    So I guess I'm missing the secret sauce here.   I log  into the portal and click the purple button to download the sdk but all I get is a HTTP Status 401 error: type Status report message description This request requires HTTP authentication (). Same

  • SetInterval and XML Load Problem

    Hello, I 'm having the simple problem of making sure the XML is loaded before beginning the Interval sequence. Therefore it is missing some of the XML data when loading. See example: http://alt.coxnewsweb.com/statesman/img/advertising/_jacob/Site1/pr

  • Import a user dump into Oracle 8i Database

    Please help, I tried to import a user dump file to Oracle 8i Database by command line (imp system/manager@instance). However, reture a message with" imported successful with warning". And I couldn't connect the database with the new user login. Any a

  • While playing movie screen frezes for few sec

    I created movie using VEDIORA & copied to 60gb Ipod. Some time it works perfectly , but some times after almost 1 min. screen frezes & after 4-5 sec resumes but then I can't hear audio & vedio continue to play without freezing. Then I press menu to g