SOAP using JMS

Hello,
We are in the process of experimenting SOAP using JMS using Weblogic Server 10.3.
1) Is there a way in Weblogic 10.3 during deployment(NOT during development) we can switch the transport to JMS instead of http. We want to do this during the deployment phase because the product that we are building will ship to an end customer. We want the customer to pick the transport layer for the webservices that he/she is going to deploy.
2) Is there a standard way of doing SOAP using JMS instead of using proprietary annotations, for example in Weblogic we use the following to change the transport layer to JMS.
@WLJmsTransport(contextPath = "transports", serviceUri = "JMSTransport", queue = "JMSTransportQueue", portName = "JMSTransportServicePort")
Any pointers in this direction will be greatly appreciated.
Thanks.

Hi, thanks for your reply.
I'm familiar with the links provided. I believe everything is configured as it should be, but since I get error I would like to have my configuration confirmed. Neither the weblog (or SAP guide) are detailed enough to convince me 100% that my configuration is correct. Surely the problem could be on the MQ side, but before going into that, I want to be sure that its not on XI-side.
So I really would like confirmation on the steps/question that I wrote:-)
Best Regards,
Daniel

Similar Messages

  • How to use SOAP over JMS with Glassfish

    Hi
    Is it possible to use JMS with JAX-WS2.0 ?
    Any answer welcome
    Andre

    I want to secure the message between my web service and a Automated activity in SAP Netweaver BPM (Process
    development). I think in this case the usage of of SOAP adapter may not be useful.
    Security parameters (settings) can be defined for Sender SOAP Adapter (as in your case it is)......to know more check this help section: http://help.sap.com/saphelp_nwpi71/helpdata/EN/fc/5ad93f130f9215e10000000a155106/content.htm
    Check the section: Define Security Parameters.
    Regards,
    Abhishek.

  • SOAP to JMS using Sync/Async bridge - configuration confirmation needed

    Hi group,
    Since I'm experincing error in a scenario using sync/async bridge in jms adapter I really would like a confirmation on my configuration.
    For a simple SOAP to JMS scenario is it then correct that all I need is;
    1) 2 synchronous message interfaces, 1 inbound and 1 outbound
    2) 1 Receiver determination
    3) 1 Interface determination
    4) 1 Receiver agreement (JMS adapter with module configuration)
    5) 2 Sender agreements (in my case 1 soap and 1 JMS adapter - the later with module configuration).
    6) The sender and receiver JMS adapters point to different MQ queues (request and response queues)
    7) The sender agreement for the JMS adapter uses my synchronous, inbound message interface (isn't this really just a "dummy" to actually fetch data from response queue - meaning that the actual utilized business system/service, MI and namespace are unimportant, since the module will make the adapter notify the listening module in the receiver JMS adapter?)
    Best Regards,
    Daniel

    Hi, thanks for your reply.
    I'm familiar with the links provided. I believe everything is configured as it should be, but since I get error I would like to have my configuration confirmed. Neither the weblog (or SAP guide) are detailed enough to convince me 100% that my configuration is correct. Surely the problem could be on the MQ side, but before going into that, I want to be sure that its not on XI-side.
    So I really would like confirmation on the steps/question that I wrote:-)
    Best Regards,
    Daniel

  • SOAP - Why not use JMS as the transport layer?

    I have been looking at the SOAP standard and can't understand
    why something hasn't been done. I wondered if someone could help.
    With the current Apache SOAP implementation there is a SOAP
    Transport interface which is implemented for SMTP and HTTP. The
    format of the messages never changes. Although it is not a
    protocol it seems eminently sensible to me that there should be
    a JMS implementation. Then infrastructure bridging cold be used
    to give a universal message queueing standard.
    Being as the current standard supports asynchronous messaging
    over SMTP. It seems to be a trivial matter to add to the SOAP
    implementation that Oracle supply. Does anyone have any good
    reason why it shouldn't be done and is there any reason Oracle
    and other standards body members couldn't have implemented it
    and agreed it in the standard?

    Am I missing something? I wasn't thinking of embedding JMS
    messages over HTTP, but using JMS itself. This would provide an
    industry standard for message queueing message formats, and
    would allow interaction with any message queueing product
    through bridges (i.e. OMB, with no real work). Aren't you
    talking about something different?

  • C/C++ using SOAP as JMS Client ?

    Did any body tried C/C++ using SOAP as JMS Client?

    You can register any compliant JMS provider as a foreign jms provider in weblogic and then can access the JMS administered objects (destination and connection factory) from the local weblogic JNDI tree.
    This blog shows how to configure AQJMS as a foreign JMS provider and then configure JMS adapter to access the jms objects.
    http://biemond.blogspot.com/2009/07/using-aq-jms-text-message-in-wls-1031.html
    You can use the above link as a reference on how to setup. You will have to modify the Initial Context Factory, Provider URL, JNDI Properties, foregin connection factories and foreign detsinations section to suit activeMQ.
    Note: Weblogic does not come inbuild with the required jars to connect to ActiveMQ unlike AQJMS, so you need to ensure that the active mq jms client jars are available in the weblogic's classpath.

  • How to get the incoming file name using JMS adapter and SOAP adapter

    Hi Everybody,
       In one of my interface i need to get the file name of incoming flat file using JMS adapter at sender side. and then i am using xslt to convert it to IDOC and then posting to  SAP IDOC.
    my incoming filname are in this form price<DateTimestamp>.txt. when i do the tranformation this incoming file name should be part of one element in the IDOC which i am posting.
    EX:
    <IDOC
    <REF>price<DateTimestamp>.txt</REF>
    </IDOC>
    Hope it is clear to everybody. I need your suggestion how i can capture this incoming file name and send it as part of IDOC.
    Thanks
    raj

    If they are passing it in message id or correlation id,
    you can access it using
    <xsl:variable name="dynamic-conf" 
            select="map:get($inputparam, 'DynamicConfiguration')" />
        <xsl:variable name="dynamic-key"  
            select="key:create('http://sap.com/xi/XI/System/JMS', 'DCJMSMessageID/ DCJMSCorrelationID')" />
        <xsl:variable name="dynamic-value"
            select="dyn:get($dynamic-conf, $dynamic-key)" />
    Check this:
    http://help.sap.com/saphelp_nw70/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
    Thanks,
    Beena.

  • SOAP over JMS Sender Communication Channel - How to?

    Hello folks,
    I have an async. scenario in which a SOAP message is posted to a JMS queue, then SAP PI picks up the SOAP message, extracts the payload and maps it into an IDOC to SAP.
    Couple of questions...
    1. Does the JMS adapter supports SOAP over JMS?
    2. Can I get the entire SOAP envelope in SAP PI (just like the "do no use SOAP envelope" function works in the SOAP adapter) ?
    3. Is the above scenario possible? Given the fact that my scenario (i.e. ccBPM, mappings, etc..) is expecting a SOAP envelope as input?
    Thanks,
    Rob

    Ok, then I think I am on the right track, but still I cannot get this scenario to work.
    JMS (SOAP)-> SAP PI(ccBPM) --> IDOC
    I put SOAP messages on the sender queue, those messages dissapear from that queue, so I would expect that I can see them back in PI, but no trace is left behind in the monitoring area... It is like they've never been read from the input queue.
    What is happenning with those messages? The definition of the SOAP envelope has been uploaded as an external definition and linked to a message interface in the repository.
    JMS Communication channel checked but it is also fine.
    Any clues where to look?
    Thanks.

  • SOAP to JMS synch scenario issue

    Dear Experts,
    I am working on SOAP to JMS (Websphere MQ) synch scenario.In the ESR i created 2 synch service interfaces(1 Inbound & 1 outbound).
    I created my 1 SOAP communication channel with QOS as "Best Effort"  2 JMS comm channel( 1 Receiver & 1 Sender).
    I am getting " no message received error in JMS receiver channel and no correlation id found error in JMS sender channel. I am attaching my channel config,error log.
    I am using PI message ID as correlation id for JMS sender and receiver channels.
    Thanks,
    Pavan T,
    +91 9901742424

    I think you should use the notify response bean on the sender channel
    Configuring the Sync/Async Bridge Using the JMS Adapter -  Adding Modules to the Module Processor - SAP Library
    Sync/Async communication in JMS adapter without BPM (SP19)

  • SOAP over JMS Problem

    I'm trying to call a SOAP over JMS Service form the BPEL process manager. For a simple example I use the Apache CXF example with Active MQ. The service has the following WSDL:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:jms="http://cxf.apache.org/transports/jms" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://cxf.apache.org/jms_greeter" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:x1="http://cxf.apache.org/jms_greeter/types" name="JMSGreeterService" targetNamespace="http://cxf.apache.org/jms_greeter">
         <wsdl:types>
              <schema targetNamespace="http://cxf.apache.org/jms_greeter/types" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
                   <element name="sayHi">
                        <complexType/>
                   </element>
                   <element name="sayHiResponse">
                        <complexType>
                             <sequence>
                                  <element name="responseType" type="xsd:string"/>
                             </sequence>
                        </complexType>
                   </element>
                   <element name="greetMe">
                        <complexType>
                             <sequence>
                                  <element name="requestType" type="xsd:string"/>
                             </sequence>
                        </complexType>
                   </element>
                   <element name="greetMeResponse">
                        <complexType>
                             <sequence>
                                  <element name="responseType" type="xsd:string"/>
                             </sequence>
                        </complexType>
                   </element>
                   <element name="greetMeOneWay">
                        <complexType>
                             <sequence>
                                  <element name="requestType" type="xsd:string"/>
                             </sequence>
                        </complexType>
                   </element>
              </schema>
         </wsdl:types>
         <wsdl:message name="sayHiRequest">
              <wsdl:part name="in" element="x1:sayHi"/>
         </wsdl:message>
         <wsdl:message name="sayHiResponse">
              <wsdl:part name="out" element="x1:sayHiResponse"/>
         </wsdl:message>
         <wsdl:message name="greetMeRequest">
              <wsdl:part name="in" element="x1:greetMe"/>
         </wsdl:message>
         <wsdl:message name="greetMeResponse">
              <wsdl:part name="out" element="x1:greetMeResponse"/>
         </wsdl:message>
         <wsdl:message name="greetMeOneWayRequest">
              <wsdl:part name="in" element="x1:greetMeOneWay"/>
         </wsdl:message>
         <wsdl:portType name="JMSGreeterPortType">
              <wsdl:operation name="sayHi">
                   <wsdl:input name="sayHiRequest" message="tns:sayHiRequest"/>
                   <wsdl:output name="sayHiResponse" message="tns:sayHiResponse"/>
              </wsdl:operation>
              <wsdl:operation name="greetMe">
                   <wsdl:input name="greetMeRequest" message="tns:greetMeRequest"/>
                   <wsdl:output name="greetMeResponse" message="tns:greetMeResponse"/>
              </wsdl:operation>
              <wsdl:operation name="greetMeOneWay">
                   <wsdl:input name="greetMeOneWayRequest" message="tns:greetMeOneWayRequest"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:binding name="JMSGreeterPortBinding" type="tns:JMSGreeterPortType">
              <soap:binding style="document" transport="http://cxf.apache.org/transports/jms"/>
              <wsdl:operation name="greetMe">
                   <soap:operation soapAction="" style="document"/>
                   <wsdl:input name="greetMeRequest">
                        <soap:body use="literal"/>
                   </wsdl:input>
                   <wsdl:output name="greetMeResponse">
                        <soap:body use="literal"/>
                   </wsdl:output>
              </wsdl:operation>
              <wsdl:operation name="sayHi">
                   <soap:operation soapAction="" style="document"/>
                   <wsdl:input name="sayHiRequest">
                        <soap:body use="literal"/>
                   </wsdl:input>
                   <wsdl:output name="sayHiResponse">
                        <soap:body use="literal"/>
                   </wsdl:output>
              </wsdl:operation>
              <wsdl:operation name="greetMeOneWay">
                   <soap:operation style="document" soapaction=""/>
                   <wsdl:input name="greetMeOneWayRequest">
                        <soap:body use="literal"/>
                   </wsdl:input>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:service name="JMSGreeterService">
              <wsdl:port name="GreeterPort" binding="tns:JMSGreeterPortBinding">
                   <jms:address destinationStyle="queue" jndiConnectionFactoryName="ConnectionFactory" jndiDestinationName="dynamicQueues/test.cxf.jmstransport.queue">
                        <jms:JMSNamingProperty name="java.naming.factory.initial" value="org.apache.activemq.jndi.ActiveMQInitialContextFactory"/>
                        <jms:JMSNamingProperty name="java.naming.provider.url" value="tcp://localhost:61616"/>
                   </jms:address>
                   <jms:clientConfig useConduitIdSelector="false"/>
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>
    When trying to call the service i get the follwing errror:
    <messages>
    <input>
    <Invoke_2_greetMeOneWay_InputVariable>
    <part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="in">
    <greetMeOneWay xmlns="http://cxf.apache.org/jms_greeter/types">
    <requestType>
    sdfsdf!
    </requestType>
    </greetMeOneWay>
    </part>
    </Invoke_2_greetMeOneWay_InputVariable>
    </input>
    <fault>
    <bindingFault xmlns="http://schemas.oracle.com/bpel/extension">
    <part name="summary">
    <summary>
    Unable to find an available port
    </summary>
    </part>
    </bindingFault>
    </fault>
    </messages>
    When using a JMS Adapter Service i can access the queue without any problems.
    Any ideas? Thanks!

    Above all, really thank you for your precious help.
    I thought about resolving the problem with JMS because it was studied to resolve asynchronous message delivery, which is what I'm trying to achieve.
    So, I think I'll try the second solution you indicated. Let's see if I understood:
    1- my customer decides to send some messages he wants to send [to better understand, I'll call them SMS] through the interface I developed
    2- a new JMS Message is created
    3- a MDB wake up and performs the initial steps to connect throught native calls
    4- new MDB wake up and, using the connection, send created SMS
    5- another process use the connection to read the StatusInd and create a new JMS Message to describe the message status
    My implementation doubt is that I must send a lot of SMS (around 4000 SMS in one action), so, in pass 4, should I create 4000 MDB instances? It should be a clean implementation, maybe this way I could use also correlation id/replyto headers in passage 5, but I would it waste many resources?
    And, also, how can I implement the "native calls"? Is there a way to create a class that support this proprietary protocol?
    And what about creating the connections with the server? Should I use java.net.socket?
    Really thank you,
    Andrea
    P.S.
    I'll look for implementing it using Arjuna+JBoss ;)

  • SOAP Over JMS, Add parameters

    Hi,
    I am working on JMS scenario in PI.I was able to push and pull message from IBM MQ message Queue.
    I need a solution on :-
    1. When i push a message in JMS queue can i add additional parameters like Interface ID or unique ID to the
    message?
    2. Using JMS sender when i pull a message i need to pick from queue based on an ID and once an id is picked i donot pick up the same message from the queue again.
    Do we have a adapter based seeting for the same? IS soap over JMS a work around on this?
    Please suggest.
    Anirban

    This link gives a good start for this - http://darwin-it.blogspot.com/2008/06/soap-over-jms.html

  • Error Generating WebService for SOAP over JMS

    Hi,
    I've been tring to create an addition web service thta takes two input and returns the sum. I was able to generate the WSDL using JDevelopers GUI tool for generating WSDL, but I notices that there was no transport layer, in thebinding that suppoerted SOAP, and the "create web service from WSDL" wizard also gave and error message:
    oracle.jdeveloper.webservices.model.WebServiceException: The chosen WSDL contains no SOAP 1.1 bindings and is therefore unsuitable for generation of a JAX-RPC web service for WLS. Only SOAP 1.1 bindings are supported for generation of JAX-RPC web services for deployment to WLS.
    This is the WSDL I created:
    <?xml version="1.0" encoding="UTF-8" ?>
    <definitions targetNamespace="http://www.example.org/addition"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://www.example.org/addition"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:jms="http://schemas.xmlsoap.org/wsdl/jms/"
    xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/">
    <types>
    <xsd:schema targetNamespace="http://www.example.org/addition/types"
    elementFormDefault="qualified"/>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:add="http://www.example.org/addition"
    targetNamespace="http://www.example.org/addition"
    elementFormDefault="qualified">
    <xsd:element name="additionInput">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="a" type="xsd:int"/>
    <xsd:element name="b" type="xsd:int"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="additionOutput">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="sum" type="xsd:int"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    </types>
    <message name="AdditionInputMessage">
    <part name="payload" element="tns:additionInput"/>
    </message>
    <message name="AdditionOutputMessage">
    <part name="payload" element="tns:additionOutput"/>
    </message>
    <portType name="AdditionPortType">
    <operation name="addition">
    <input message="tns:AdditionInputMessage"/>
    <output message="tns:AdditionOutputMessage"/>
    </operation>
    </portType>
    <binding name="AdditionPortTypeJMSBinding" type="tns:AdditionPortType">
    <jms:binding type="ObjectMessage"/>
    <format:typeMapping encoding="Java" style="Java">
    <format:typeMap typeName="tns:additionInput" formatType=""/>
    <format:typeMap typeName="tns:additionOutput" formatType=""/>
    </format:typeMapping>
    <operation name="addition">
    <input>
    <jms:input parts="payload"/>
    <jms:property name="payloadProperty" part="payload"/>
    </input>
    <output>
    <jms:output parts="payload"/>
    <jms:property name="payloadProperty" part="payload"/>
    </output>
    </operation>
    </binding>
    <service name="AdditionPortType">
    <port name="AdditionPortTypePort" binding="tns:AdditionPortTypeJMSBinding"/>
    </service>
    </definitions>
    Could someone please help me out? I've been struggling with this problem for two weeks and can't make any headway. It's really driving me nuts. I've looked all over the web, and while everyone agrees that SOAP over JMS is possible, no one sems to have a working solution. One example I was able to get hold of used ant for deployment, but the deploy task failed when I ran it. Please, please help me.

    Hi,
    I've been tring to create an addition web service thta takes two input and returns the sum. I was able to generate the WSDL using JDevelopers GUI tool for generating WSDL, but I notices that there was no transport layer, in thebinding that suppoerted SOAP, and the "create web service from WSDL" wizard also gave and error message:
    oracle.jdeveloper.webservices.model.WebServiceException: The chosen WSDL contains no SOAP 1.1 bindings and is therefore unsuitable for generation of a JAX-RPC web service for WLS. Only SOAP 1.1 bindings are supported for generation of JAX-RPC web services for deployment to WLS.
    This is the WSDL I created:
    <?xml version="1.0" encoding="UTF-8" ?>
    <definitions targetNamespace="http://www.example.org/addition"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://www.example.org/addition"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:jms="http://schemas.xmlsoap.org/wsdl/jms/"
    xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/">
    <types>
    <xsd:schema targetNamespace="http://www.example.org/addition/types"
    elementFormDefault="qualified"/>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:add="http://www.example.org/addition"
    targetNamespace="http://www.example.org/addition"
    elementFormDefault="qualified">
    <xsd:element name="additionInput">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="a" type="xsd:int"/>
    <xsd:element name="b" type="xsd:int"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="additionOutput">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="sum" type="xsd:int"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    </types>
    <message name="AdditionInputMessage">
    <part name="payload" element="tns:additionInput"/>
    </message>
    <message name="AdditionOutputMessage">
    <part name="payload" element="tns:additionOutput"/>
    </message>
    <portType name="AdditionPortType">
    <operation name="addition">
    <input message="tns:AdditionInputMessage"/>
    <output message="tns:AdditionOutputMessage"/>
    </operation>
    </portType>
    <binding name="AdditionPortTypeJMSBinding" type="tns:AdditionPortType">
    <jms:binding type="ObjectMessage"/>
    <format:typeMapping encoding="Java" style="Java">
    <format:typeMap typeName="tns:additionInput" formatType=""/>
    <format:typeMap typeName="tns:additionOutput" formatType=""/>
    </format:typeMapping>
    <operation name="addition">
    <input>
    <jms:input parts="payload"/>
    <jms:property name="payloadProperty" part="payload"/>
    </input>
    <output>
    <jms:output parts="payload"/>
    <jms:property name="payloadProperty" part="payload"/>
    </output>
    </operation>
    </binding>
    <service name="AdditionPortType">
    <port name="AdditionPortTypePort" binding="tns:AdditionPortTypeJMSBinding"/>
    </service>
    </definitions>
    Could someone please help me out? I've been struggling with this problem for two weeks and can't make any headway. It's really driving me nuts. I've looked all over the web, and while everyone agrees that SOAP over JMS is possible, no one sems to have a working solution. One example I was able to get hold of used ant for deployment, but the deploy task failed when I ran it. Please, please help me.

  • SOAP over JMS

    Hi All,
    I have been researching sending SOAP messages over JMS (instead of HTTP) and know all about the pro's and contra's.
    For those interested, her eare some excellent links on the topic:
    http://blogs.ittoolbox.com/eai/business/archives/web-services-http-vs-jms-19110
    http://dev2dev.bea.com/blog/pdone/archive/2007/03/using_soap_over.html
    http://www.webservices.org/categories/development/java/asynchronous_web_services_and_the_enterprise_service_bus/(go)/Articles
    http://webservices.sys-con.com/read/114115.htm
    I am aware that this hasn't been standardised and vendors implement their own prprietary way. IBM Websphere and BEA, for example, have done this. I don't think JCAPS has done this.
    BUT, is there a way to get it working using JCAPS anyway?
    Thanks for any feedbakck/insights/help...
    Kind regards,
    Stijn.

    Hi Stijn,
    it's pretty definitive this is going to be in JCAPS 5.2.0, and maybe will be introduced back into 5.1.3 in a rollup ESR.
    For intermediate solutions, you can just sent messages over JMS and handle the SOAP message format via importing the SOAP XSD and generating an OTD from that so the JCD handles the SOAP Envelope serialization actions. ( http://dev.w3.org/cvsweb/2002/ws/desc/wsdl12/wsdl12-soap.xsd?rev=1.10&content-type=text/x-cvsweb-markup ) .
    For the sending / receiving clients, please look at https://jmsjca.dev.java.net/ which provides the JMS Resource Adapters for STCMS.
    A commonly used pattern for scalable Web Services, is to forward them to a JMS Queue at receipt. If it's a synchronous call you can use JMS Request Reply.
    Hope this helps
    Paul

  • SOAP over JMS with Oracle tool chain

    Hi,
    is there an easy way to create a webservice with SOAP over JMS for Oracle Application Servers?
    Are there any tutorials, docus or examples?
    Any hint is appreciated....

    I found a first step...:
    In JDeveloper i created a "new..."-> "Webservice->JMS Adapter"
    This created a complete wsdl:
    <definitions
    name="MySOAPoverJMS"
    targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/jms/MySOAPoverJMS/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/jms/MySOAPoverJMS/"
    xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"
    xmlns:pc="http://xmlns.oracle.com/pcbpel/" xmlns:imp1="http://xmlns.oracle.com/pcbpel/adapter/db/DBAPP/ADDEMPLOYEES/"
    xmlns:hdr="http://xmlns.oracle.com/pcbpel/adapter/jms/"
    >
    <import namespace="http://xmlns.oracle.com/pcbpel/adapter/jms/" location="jmsAdapterInboundHeader.wsdl"/>
    <types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema" >
    <import namespace="http://xmlns.oracle.com/pcbpel/adapter/db/DBAPP/ADDEMPLOYEES/" schemaLocation="ADDEMPLOYEES.xsd" />
    </schema>
    </types>
    <message name="InputParameters_msg">
    <part name="InputParameters" element="imp1:InputParameters"/>
    </message>
    <portType name="Consume_Message_ptt">
    <operation name="Consume_Message">
    <input message="tns:InputParameters_msg"/>
    </operation>
    </portType>
    <binding name="Consume_Message_binding" type="tns:Consume_Message_ptt">
    <pc:inbound_binding />
    <operation name="Consume_Message">
    <jca:operation
    ActivationSpec="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec" DestinationName="java:comp/resource/OEMS/Topics/JMSUSER.JMSDEMO_TOPIC"
    UseMessageListener="false"
    PayloadType="TextMessage"
    OpaqueSchema="false" >
    </jca:operation>
    <input>
    <jca:header message="hdr:InboundHeader_msg" part="inboundHeader"/>
    </input>
    </operation>
    </binding>
    <service name="MySOAPoverJMS">
    <port name="Consume_Message_pt" binding="tns:Consume_Message_binding">
    <!--Your runtime connection is declared in
    J2EE_HOME/application-deployments/default/JMSAdapter/oc4j-ra.xml
    These mcf properties here are from your design time connection and
    save you from having to edit that file and restart the application server
    if eis/Jms/OEMS is missing.
    These mcf properties are safe to remove.-->
    <jca:address location="eis/Jms/OEMS" UIConnectionName="OEMS" ManagedConnectionFactory="oracle.tip.adapter.jms.JmsManagedConnectionFactory" mcf.ConnectionFactoryLocation="java:comp/resource/OEMS/TopicConnectionFactories/TCF"
    mcf.IsTopic="true"
    mcf.IsTransacted="true"
    mcf.FactoryProperties=""
    mcf.Username="jmsuser"
    mcf.Password="BE49B84750434652C21A27623F0F412D"
    UIJmsProvider="OJMS" />
    </port>
    </service>
    <plt:partnerLinkType name="Consume_Message_plt" >
    <plt:role name="Consume_Message_role" >
    <plt:portType name="tns:Consume_Message_ptt" />
    </plt:role>
    </plt:partnerLinkType>
    </definitions>
    But this contains no SOAP definition, so that i cannot use this with "new..."->"Webservice->Java Web Service from WSDL" to create the java code...
    Any ideas?

  • SOAP over JMS in OSB

    Hello!
    I've successfully created the following:
    (1) A Soap over JMS Endpoint using OSB.
    (2) A standalone Java Client to the above endpoint (using the weblogic.wsee.tools.anttasks.ClientGenTask tool).
    My first question is, am I limited to using the ClientGenTask tool for generating the Java Client? I tried using CXF but had problems running the generated code. Does anyone out there have experience of using other tools for generating the clients for these specific types of endpoints (Soap over JMS on OSB)?
    My second question is whether Soap over JMS is whether or not Soap over JMS will ever support JAX-WS on the OSB platform?
    Thanks for any help you chaps can give me!
    Mark.

    Hi Tirthankar
    I faced the same problem you'r describing in your post and found it while googling over the net.
    Could you share please what was your solution for this problem?
    Grealty thanx in advance for any inputs
    Sincerely
    Jabb.

  • Asynchronous SOAP over JMS

    Is it possible to expose an operation type of "Process Notification" using SOAP over JMS? When you select the Process Web Service option on the process it only allows you to define SOAP over HTTP web services. It's possible to invoke one-way SOAP over JMS web services but I cannot find a way of exposing a BPM process (or process notification) as a one-way SOAP over JMS web service.
    Thanks in advance

    There is not a way to use JMS instead of HTTP to expose the process notifications. You would need to create a JMS listener, parse the soap message, and then notify the instance (using correlations probably) from within the global.
    Creating JMS listeners is not hard to do. Let me know if you need help with that.
    HTH,
    Mark

Maybe you are looking for

  • Reorder Point Planning

    Hi all, Business Process is: 1. I am having 6 plants assigned to a single company code. 2. I had created material "A" and assinged to all 6 plants with different manual reorder points, selected MRP type VB,. Plants:                    1000      1010 

  • After Creation of PO Release strategy is missing

    Hi Experts, We have a problem that we have created a PO but we found after that release strategy is getting missed out. What could be the possible causes for this? Note: We have checked in CL20N everything seems to be in place. Cheers,Kumar.S///

  • Question: How to convert dvd to mp4

    I have tried multiple products at this point to convert files and I'm tired of spending money. Most recent download is the Xilsoft Converter. I guess I just thought I would have one file when all the conversion was over. I do not of course. (Heck, al

  • LOADING x12 834 data into database and 999 generation for received x12 file

    Hi All, I'm New to BizTalk, Im using BizTalk 2010 developer edition....I need to load the x12 834 enrollment data (few details) into database. I want to know the step by step procedure to do this. kindly help me. Also i need to know the 999 ackknowle

  • Can't receive events with a custom component

    I am using the MDIPanel created by Christophe Coenraets in the Sales Builder demo code in Flex 2. However, this custom component (MDIPanel) doesn't seem to receive regular events other than the custom events. The MDI Panel source code is included as