JMX over JMS

Any one has any experience in connecting MBean servers to Sun MQ. Specifically with Lingo framework...(http://lingo.codehaus.org/JMX+over+JMS).
Thanks,
-Uday.

My understanding is that MBean servers are the containers within the manageable application (eg MQ broker/server VM) that house the manageable resources (ie JMX MBeans) that is exposed to management applications. These MBeans are what defines what can be managed/configured. If an application does not have an MBean Server in it or specific MBeans to do management, than JMX management applications cannot monitor it.
As of MQ 4.1, the MQ broker has JMX support ie it has an MBean Server that contains a bunch of MBeans for management.
So, I'm not sure what you mean by "connecting MBean Servers to Sun MQ". An MBean Server already exists within the MQ broker VM.
Management applications (written in JMX), can connect to the MBean server in MQ brokers (and therefore access the MBeans) via various connection protocols, the default (and only supported one for MQ) being RMI.
Lingo allows you to plug in a different connection protocol - one based on JMS, which is also implemented by Lingo. It does not look like you can use Lingo plus any other JMS provider - you need to use Lingo's JMS support. This is my understanding from high level browsing of Lingo's website.
Since MQ (like Lingo) is also a JMS provider, I think it is worthwhile to ask (for clarification):
- what version of MQ are you using ? (are you using an older version that does not have JMX support ?)
- any reason why you cannot use the default RMI protocol ?
- are you asking if one can use Lingo plus MQ as the JMS provider ?
- are you asking if one can connect to (ie manage/monitor) the MQ broker using Lingo and it's own JMS provider ?
Sorry for long winded reply - unless I'm missing something (apologies if this is the case), it looks a bit awkward to monitor/manage a JMS provider (ie MQ) that has built in JMX management (unless you're using an older version of MQ) using yet another JMS based connection protocol (ie Lingo).
I haven't tried it but from looking at Lingo documentation, I don't think you can use Lingo to monitor/manage a MQ broker because a special Lingo connector needs to be setup from within the MQ broker's MBean Server.
Once again - apologies if I've misunderstood anything - please fill me in if this is the case.
regards,
-isa

Similar Messages

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

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

  • Two short Soap over JMS questions

    Hello everybody,
    ís it possible to call a SOAP Service over JMS with the Oracle BPEL Process Manager, when the SOAP Service uses a "non-Oracle" queue (e.g. Apache ActiveMQ)?
    Is the schema for the namespace "http://www.oracle.com/technology/oracleas/wsdl/jms" or documentation for the elements <jms:address> and <jms:propertyValue> available somewhere?
    Thank you for your time.

    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.

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

  • Sending and receiving SOAP over JMS in XI

    Hai All,
    I am working on a scenario in which I have to send a SOAP message over JMS adapter to XI and receive again the SOAP message over the JMS adapter.
    Here my questions are:
    1.How can I configure the JMS adapter to get the SOAP messages into XI.
    Thanks in Advance
    Srikanth

    Hi,
    1. Get the WSDL of the soap message and send it as a payload to the JMS adapter including the SOAP envelope.
    OR
    2. You can create the structer of teh SOAP body and while sending it and receiving it you can use either XSLT or JAVA or ABAP mapping to add and remove the SOAP envelope. So you can send/receive them as a payload to the JMS adapter
    Regards,
    Prakash

  • 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

  • Accessing SOAP over JMS webservice

    Hi,
    From Webdynpro can I access a webservice which is using SOAP over JMS.
    Is there any example on it.
    Thanks.
    MS.

    I have similar situation.
    R/3->XI->java message server
    XI and message server exchange SOAP envelope using JMS. (SOAP over JMS)
    XI posts SOAP message in queue & in inbound case would pickup SOAP message from JMS queue.
    My question: When using a SOAP adapter, it does work of stripping SOAP envelope/ header? Do we need to handle it in xslt when a message is picked up from external message queue(from message server)? In other words how to handle SOAP message in inbound case?
    Thanks,
    sachin
    PS: Points will be awarded for useful answer

  • SOAP over JMS binding

    Hi Experts,
    Is it possible to expose as a SOAP over JMS binding webservice from XI (from SAP platform)?
    Regards
    Sara

    I have similar situation.
    R/3->XI->java message server
    XI and message server exchange SOAP envelope using JMS. (SOAP over JMS)
    XI posts SOAP message in queue & in inbound case would pickup SOAP message from JMS queue.
    My question: When using a SOAP adapter, it does work of stripping SOAP envelope/ header? Do we need to handle it in xslt when a message is picked up from external message queue(from message server)? In other words how to handle SOAP message in inbound case?
    Thanks,
    sachin
    PS: Points will be awarded for useful answer

  • Why should I use Publish instead of Routing for SOAP messages over JMS?

    Hi,
    I currently read the book "The Definitive Guide to SOA - Oracle Service Bus" and found the following sentence in the chapter "Wrapping an Asynchronous Web Service with a Proxy Service" on page 131, which confuses me:
    When you send a SOAP message over a JMS queue, you need to use the Publish action, not the Routing action. <<Are there general restrictions, when to use Publish and when to use the Routing action in asynchronous communication? Is this special for SOAP messages over JMS?
    Thanks for your advices,
    Katja

    Here are a few reasons why. Enjoy!!
    A
    What Can Amazon Web Services Be Used For?
    Although Amazon Web Services is a cool technology, it also provides the very useful function of enabling business partners to interact with Web site through standard protocols. This interaction can lead to a deeper, more valuable relationship for parties involved. Here are a few of the ways that partners are benefiting from Web Services:
    Associates: Associates program enables Web sites to link to Amazon.com and earn referral fees for sales that they drive through their links. Many Associates are now using Web Services to build more effective links to our store, thus enhancing their sites and earning more money.
    Sellers and Vendors: Amazon.com has thousands of third-party sellers who offer their products on our Web site. Using Web Services, these sellers can more easily manage large quantities of inventory on our platform, and download the latest product information to make sure that their products are competitively priced.
    Developers: Among the thousands of developers who have signed up to our Web Services program, many are now creating solutions to help other people work with Amazon. These solutions are powered using our Web Services APIs.
    www.amazon.com/gp/aws/landing.html

Maybe you are looking for