WebServices over JMS

Hello,
Is that possible to have WebServices working with JMS server behind the scene? I mean not using SOAP/HTTP, but SOAP/JMS so the SOAP message is posted to JMS queue directly by the stub without being sent via HTTP on server and then pushed to JMS queue.
From what I saw in the Sun technical articles, they offer next solution:
Stub->Generates SOAP message->Message is sent over HTTP on server->Servlet takes the message and pushes to JMS queue
What I'm looking for is:
Stub->Generates SOAP message->Message is pushed to the JMS server directly.
Can someone help me with this?
Thanks.

please check the below link it has some info
http://www-128.ibm.com/developerworks/webservices/library/ws-jms/

Similar Messages

Submit order using Webservice over JMS

Hi,
from the SDK samples(webservice sample) and from one of the reply from the forum:
The wlsmimehdrContent_Type JMS header must be set to the following value: text/xml; charset="UTF-8"
The URI JMS header must be set to the following value: /osm/wsapi
Want to test webservice over JMS using SOAP UI (that supports HermesJMS):
I have configured HermesJMS then configured SoapUI 4.0 by adding endpoint as JMS then selected webserive endpoint as JMS:osm_ws_request (long name) instead of "http://localhost:7001/osm/wsapi".
Now for JMS endpoint where to add webservice URI "/osm/wsapi" unable to figure out where to add URI (in SOAPUI or HermesJMS) which parameter need to set for webservice URI?
Regards,
Rutvej

Hi,
Above query is resolved..
Cheers,
Rutvej

Configure # of JMS consumers for WebServices over JMS Transport

I'm using WebLogic Server 9.2. My Web Services are using JMS Transport.
10,000 Web Services requests are submitted to the Web Services JMS queue at the same time. Processing time seems a little slow. In the Admin console, monitoring info of the JMS queue shows the Consumers is 4 and Consumers High is 6.
I want to scale Web Services processing by increasing the number of JMS consumers that transform JMS request messages into Web Services requests. Does anyone have an idea to configure it?

Hi,
I don't think the number of consumers for a service is configurable. There is a single consumer for each service. Well, there is another consumer for interop purposes, which is irrelevant to our discussion here.
You may be aware that multiple consumers reading from the same queue would result in requests being processed in parallel, which means the order that the requests are processed might be different from the order that they are put into the queue.
For applications where the order of processing the requests to the same web service is not important, it probably makes sense to have an option of configuring multiple consumers. But this is no such option right now.
Regards,
Dongbo, BEA

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.

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

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

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

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

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.

WebServices over SSL - 403 Forbidden error

Hello all,
I am able to successfully communicate with a SSL enabled .NET webservice using apache-axis in my java code. however, when i
try the same with weblogic based libs [%bea_home%\server\lib\webserviceclient+ssl.jar] - assume the other jars are ok, i get
the following exception stack trace:
Disabling strict checking on adapter weblogic.webservice.client.WLSSLAdapter@55a338
Set TrustManager to weblogic.webservice.client.BaseWLSSLAdapter$NullTrustManager@fdb00d
Set HostnameVerifier to weblogic.webservice.client.WLSSLAdapter$NullVerifier@131303f
Disabling strict checking on adapter weblogic.webservice.client.WLSSLAdapter@6b9c84
Set TrustManager to weblogic.webservice.client.BaseWLSSLAdapter$NullTrustManager@e1eea8
Set HostnameVerifier to weblogic.webservice.client.WLSSLAdapter$NullVerifier@131303f
Got new socketfactory javax.net.ssl.impl.SSLSocketFactoryImpl@18f51f
Connecting to:www.abc.com port:443
socket:Socket[addr=www.abc.com/12.345.67.89,port=443,localport=4802]com.certicom.tls.interfaceimpl.TLSConnectionImpl@e35bb7
Warning: cert chain incomplete
Warning: cert chain untrusted
Warning: subject (www.abc.com, OU=Terms of use at www.verisign.com/rpa (c)00, OU=ABC 1, O=ABC inc, L=abc, ST=abc, C=abc) does
not match server name (null)
<Jul 27, 2004 10:52:49 AM GMT+05:30> <Info> <WebService> <BEA-220025> <Handler weblogic.webservice.core.handler.ClientHandler
threw an exception from its handleResponse method. The exception was:
javax.xml.rpc.JAXRPCException: weblogic.webservice.util.AccessException: The server at
https://www.abc.com/abcdef/ABCWebService.asmx?WSDL returned a 403 error code (Forbidden). Please ensure that your URL is
correct and that the correct protocol is in use..>
A RemoteException has been thrown
java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: The server at
https://www.abc.com/abcdef/ABCWebService.asmx?WSDL returned a 403 error code (Forbidden). Please ensure that your URL is
correct and that the correct protocol is in use.
Detail:
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">
</bea_fault:stacktrace>weblogic.webservice.util.AccessException: The server at
https://www.abc.com/abcdef/ABCWebService.asmx?WSDL returned a 403 error code (Forbidden). Please ensure that your URL is
correct and that the correct protocol is in use.
     at weblogic.webservice.binding.soap.HttpClientBinding.handleErrorResponse(HttpClientBinding.java:371)
     at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:233)
     at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:63)
     at weblogic.webservice.core.HandlerChainImpl.handleResponse(HandlerChainImpl.java:230)
     at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:229)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:444)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:430)
     at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:270)
     at com.webservice.abc.client.proxy.ABCWebserviceSoap_Stub.getABC(ABCWebserviceSoap_Stub.java:113)
     at com.webservice.abc.client.ABC_WS_Client.main(ABC_WS_Client.java:158)
</detail>; nested exception is:
     javax.xml.rpc.soap.SOAPFaultException: The server at https://www.abc.com/abcdef/ABCWebService.asmx?WSDL returned a
403 error code (Forbidden). Please ensure that your URL is correct and that the correct protocol is in use.
     at com.webservice.abc.client.proxy.ABCWebserviceSoap_Stub.getABC(ABCWebserviceSoap_Stub.java:118)
     at com.webservice.abc.client.ABC_WS_Client.main(ABC_WS_Client.java:158)
Caused by: javax.xml.rpc.soap.SOAPFaultException: The server at https://www.abc.com/abcdef/ABCWebService.asmx?WSDL returned a
403 error code (Forbidden). Please ensure that your URL is correct and that the correct protocol is in use.
     at weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:285)
     at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:144)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:444)
     at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:430)END
     at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:270)
     at com.webservice.abc.client.proxy.ABCWebserviceSoap_Stub.getABC(ABCWebserviceSoap_Stub.java:113)
     ... 1 more

Hi All,
I am new to webservice programming. I am trying to consume webservice over https. I am using weblogic 8.1 sp2. I am getting http 403 forbidden error. from the log it seems that ssl handshaking is completing.
Algorithm: [MD2withRSA]
Signature:
0000: BB 4C 12 2B CF 2C 26 00 4F 14 13 DD A6 FB FC 0A .L.+.,&.O.......
0010: 11 84 8C F3 28 1C 67 92 2F 7C B6 C5 FA DF F0 E8 ....(.g./.......
0020: 95 BC 1D 8F 6C 2C A8 51 CC 73 D8 A4 C0 53 F0 4E ....l,.Q.s...S.N
0030: D6 26 C0 76 01 57 81 92 5E 21 F1 D1 B1 FF E7 D0 .&.v.W..^!......
0040: 21 58 CD 69 17 E3 44 1C 9C 19 44 39 89 5C DC 9C !X.i..D...D9.\..
0050: 00 0F 56 8D 02 99 ED A2 90 45 4C E4 BB 10 A4 3D ..V......EL....=
0060: F0 32 03 0E F1 CE F8 E8 C9 51 8C E6 62 9F E6 9F .2.......Q..b...
0070: C0 7D B7 72 9C C9 36 3A 6B 9F 4E A8 FF 64 0D 64 ...r..6:k.N..d.d
]>
<Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <SSLTrustValidator r
eturns: 0>
<Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <Trust status (0): N
ONE>
<Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: S
erverHelloDone>
<Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <write HANDSHAKE off
set = 0 length = 134>
<Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <write CHANGE_CIPHER
_SPEC offset = 0 length = 1>
<Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <write HANDSHAKE off
set = 0 length = 16>
<Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <SSLFilter.isActivat
ed: false>
<Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <isMuxerActivated: f
alse>
<Jan 30, 2006 11:39:29 AM GMT+05:30> <Debug> <TLS> <000000> <SSLFilter.isActivat
ed: false>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 readRecord(
)>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 SSL3/TLS MA
C>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 received CH
ANGE_CIPHER_SPEC>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <SSLFilter.isActivat
ed: false>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <isMuxerActivated: f
alse>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <SSLFilter.isActivat
ed: false>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 readRecord(
)>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 SSL3/TLS MA
C>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 received HA
NDSHAKE>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <HANDSHAKEMESSAGE: F
inished>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <write APPLICATION_D
ATA offset = 0 length = 304>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <write APPLICATION_D
ATA offset = 0 length = 558>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 read( offse
t: 0 length: 2048 )>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <SSLFilter.isActivat
ed: false>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <isMuxerActivated: f
alse>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <SSLFilter.isActivat
ed: false>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 readRecord(
)>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 SSL3/TLS MA
C>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 received AP
PLICATION_DATA>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 APPDATA dat
abufferLen 0>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 APPDATA con
tentLength 1907>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 read databu
fferLen 1907>
<Jan 30, 2006 11:39:30 AM GMT+05:30> <Debug> <TLS> <000000> <5564590 read A retu
rns 1907>
javax.xml.soap.SOAPException: Failed to send message: weblogic.webservice.util.A
ccessException: The server at https://www.3pv.net/3PVWebServices/3PVWebServices.
asmx?wsdl returned a 403 error code (Forbidden). Please ensure that your URL is
correct and that the correct protocol is in use.
at weblogic.webservice.core.soap.SOAPConnectionImpl.call(SOAPConnectionI
mpl.java:61)
at com.ceon.pencor.threepv.ThreePVUtils.sendOrderRequest(ThreePVUtils.ja
va:350)
at com.ceon.pencor.threepv.ThreePVAdapterImpl.sendThreePVRequest(ThreePV
AdapterImpl.java:119)
at com.ceon.pencor.threepv.ThreePVAdapterImpl_ydsnbq_EOImpl.sendThreePVR
equest(ThreePVAdapterImpl_ydsnbq_EOImpl.java:46)
at com.ceon.pencor.threepv.ThreePVAdapterImpl_ydsnbq_EOImpl_WLSkel.invok
e(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:108)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:353)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
144)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:415)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Caused by: weblogic.webservice.util.AccessException: The server at https://www.3
pv.net/3PVWebServices/3PVWebServices.asmx?wsdl returned a 403 error code (Forbid
den). Please ensure that your URL is correct and that the correct protocol is i
n use.
at weblogic.webservice.binding.http11.Http11ClientBinding.handleErrorRes
ponse(Http11ClientBinding.java:136)
at weblogic.webservice.binding.http11.Http11ClientBinding.receive(Http11
ClientBinding.java:220)
at weblogic.webservice.core.soap.SOAPConnectionImpl.call(SOAPConnectionI
mpl.java:57)
... 13 more
javax.xml.soap.SOAPException: Failed to send message: weblogic.webservice.util.A
ccessException: The server at https://www.3pv.net/3PVWebServices/3PVWebServices.
asmx?wsdl returned a 403 error code (Forbidden). Please ensure that your URL is
correct and that the correct protocol is in use.
at weblogic.webservice.core.soap.SOAPConnectionImpl.call(SOAPConnectionI
mpl.java:61)
at com.ceon.pencor.threepv.ThreePVUtils.sendOrderRequest(ThreePVUtils.ja
va:350)
at com.ceon.pencor.threepv.ThreePVAdapterImpl.sendThreePVRequest(ThreePV
AdapterImpl.java:119)
at com.ceon.pencor.threepv.ThreePVAdapterImpl_ydsnbq_EOImpl.sendThreePVR
equest(ThreePVAdapterImpl_ydsnbq_EOImpl.java:46)
at com.ceon.pencor.threepv.ThreePVAdapterImpl_ydsnbq_EOImpl_WLSkel.invok
e(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerR
ef.java:108)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:353)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
144)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
a:415)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Caused by: weblogic.webservice.util.AccessException: The server at https://www.3
pv.net/3PVWebServices/3PVWebServices.asmx?wsdl returned a 403 error code (Forbid
den). Please ensure that your URL is correct and that the correct protocol is i
n use.
at weblogic.webservice.binding.http11.Http11ClientBinding.handleErrorRes
ponse(Http11ClientBinding.java:136)
at weblogic.webservice.binding.http11.Http11ClientBinding.receive(Http11
ClientBinding.java:220)
at weblogic.webservice.core.soap.SOAPConnectionImpl.call(SOAPConnectionI
mpl.java:57)
... 13 more
ERROR : Exception is occurred during connecting url:https://www.3pv.net/3PVWebS
ervices/3PVWebServices.asmx?wsdl
Please help...
Cordially
Sandip

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.

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

WebServices over JMS

Similar Messages

Maybe you are looking for