SOAP over MQ in WSDL

SOA Gurus,
We have a requirement to interact with target system as SOAP/MQ messages. My confusion is, Is there any MQ transpot SOAP binding available in wsdl or do we need to use the SOAP/JMS.
How will the wsdl binding look like for SOAP/MQ.
Thanks in advance.

This article may help...
http://www.ibm.com/developerworks/webservices/library/ws-soapojms/index.html
Cheers,
Vlad

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 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 ;)

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

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

Enabling SOAP over HTTPs on PI7.0

Hello
    We have a requirement to connect PI7.0 to PI7.1 with SOAP over HTTPS. Would you please let us know what all configuration need
       1. Setting required to be done on PI7.0 ( Communication Channels, Receiver and Sender agreements)
       2. Where to put private key and root certificate in Visual admin
       3. Port configuration for outbound and inbound traffic.
       4. Enabling of SSL on PI7.0.
       5. Any ICM related setting on PI7.0
Thanks & Regards

Hi Uttam,
Hi,
For using HTTPS protocol, you have to chose the option of HTTPS in the 'HTTP Security Level' parameter on SOAP sender communication channel.
For using HTTPS protocol, the SSL certificates need to be deployed on the server.
Below are the links for more information on SSL certificates:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/14/ef2940cbf2195de10000000a1550b0/frameset.htm
http://www.tldp.org/HOWTO/SSL-Certificates-HOWTO/
For choosing & installing steps of SSL, refer the below links:
/people/aniket.tare/blog/2005/03/22/ssl-certificate-installation-procedure-for-sap-j2ee-engine-630-150-steps-in-visual-administrator
http://info.ssl.com/article.aspx?id=10694
-Supriya.

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

Soap over SMTP.

Hi there,
We are planning some of our integration in terms of Web Services;
anyway, we feel sometimes http as transport can be troublish because we feel
some of the links between clients and servers are not much reliable. So we
are thinking about SMTP or MQ series/JMS as the transport... does anybody
have tried this?.
Any tip?. Any good resource/book/code examples?
Many thanks for your help. Best regards,

Hi Tom,
I don't think WLS 7.0 supports SOAP over SMTP, yet :-) You can check out the following
URLs for useful information on this topic:
http://www.pocketsoap.com/specs/smtpbinding/
http://xml.apache.org/soap/faq/faq_chawke_smtp.html
Regards,
Mike Wooten
"Tom Sayx" <[email protected]> wrote:
Hi there,
We are planning some of our integration in terms of Web Services;
anyway, we feel sometimes http as transport can be troublish because
we feel
some of the links between clients and servers are not much reliable.
So we
are thinking about SMTP or MQ series/JMS as the transport... does anybody
have tried this?.
Any tip?. Any good resource/book/code examples?
Many thanks for your help. Best regards,

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.

Soap over SMS

Im wondering if there is a way of using soap over SMS. Im currently using it over http/GPRS but I need a similar application in a place where there is no GPRS

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

SOAP over TCP/IP

Hi,
Has anyone implemented SOAP over TCP/IP sockets instead of using a web server? Does JWSDP support this?
Any information and pointers on how to implement this is highly appreciated.
Thanks in advance.
Amogh

WSIT, which is built on top of JAX-WS supports SOAP/TCP. You can get wsit from http://wsit.dev.java.net

SOAP over Messaging

I was curious to know the status of SOAP over messaging protocols. Is this standardized
yet? If not is the support for WebServices over JMS in WebLogic a proprietary
implementation?

Hello,
In pointing to this recent spec [1] the three authors have provided
their contact information; they would be a good source of information in
this area.
Regards,
Bruce
[1]
http://dev2dev.bea.com/technologies/webservices/WS-MessageData_Intro.jsp
Mohammad Naderi wrote:
>
I was curious to know the status of SOAP over messaging protocols. Is this standardized
yet? If not is the support for WebServices over JMS in WebLogic a proprietary
implementation?

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 MQ in WSDL

Similar Messages

Maybe you are looking for