Invoking RESTful service from OSB

Hi
I need to invoke Restful service from OSB11g in order to do that...
1. I have created Business service with the end point of the RESTful service.
2. Running the Business service and provided the XML as input in Transport Header--> query-string.. i got the response as bellow:
<serviceResponse returnCode="-1">
<statusMessage messageId="Exception" messageType="" severityCode="E">
<text>
Required input not supplied. Please revisit your input values and try again.
</text>
</statusMessage>
</serviceResponse>
Is this the correct way i am doing or am i missing something..???
Thanks
Vasu

Hi Vasu,
did you solve your issue ?
I have a similar scenario where I need to call a RESTful service from OSB.
The RESTful URL service is http://xxx.xxx.xxx.xxx/api/ordertracer and has been implemented in IIS.
The service accepts a xml string message as input and returns an HttpStatusCode.
So I started defining a business service (named OrderTracer):
Service Type: Any XML Service
Endpoint URI: http://xxx.xxx.xxx.xxx/api/ordertracer
HTTP Request Method:POST
I tested it from business service test console:
- in Transport
-> query-string I put my input xml
-> http-method: POST
-> Content-Type: text/xml
but on execute I got an error:
<con:metadata xmlns:con="http://www.bea.com/wli/sb/test/config">
<tran:headers xsi:type="http:HttpResponseHeaders" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<http:Connection>close</http:Connection>
<http:Content-Length>315</http:Content-Length>
<http:Content-Type>text/html; charset=us-ascii</http:Content-Type>
<http:Date>Wed, 03 Oct 2012 15:07:38 GMT</http:Date>
<http:Server>Microsoft-HTTPAPI/2.0</http:Server>
</tran:headers>
<tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">3</tran:response-code>
<tran:response-message xmlns:tran="http://www.bea.com/wli/sb/transports">Not Found</tran:response-message>
<tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">us-ascii</tran:encoding>
<http:http-response-code xmlns:http="http://www.bea.com/wli/sb/transports/http">404</http:http-response-code>
</con:metadata>
May I ask you to provide me any hints ?
Thanks in advance for any help
ferp

Similar Messages

[OSB1031] how to call a RESTful service from OSB with authentication

Hi all,
I called successfully a RESTful service from OSB.
We have a business service, named OrderTracer, that wraps the call to the RESTful service.
The RESTful service requires an authentication so we are trying to find out how the OSB business service should authenticate itself against the RESTful service.
In addition the RESTful service accepts username/password coded as base64.
So we defined a Service Account with static resource type and we added the reference to this service account in the business service.
But when the OSB business service calls the RESTful service, we got an error:
<fault>
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380000</con:errorCode>
<con:reason>Unauthorized</con:reason>
<con:location>
<con:node>RouteNode</con:node>
<con:path>response-pipeline</con:path>
</con:location>
</con:fault>
</fault>
Does anyone have any hint ?
Any clue would be of great help.
Thanks in advance
ferp

Hi,
There's a sample on JSON REST here...
http://java.net/projects/oraclesoasuite11g/downloads/download/OSB/osb-206-JSONREST.zip
For other samples, see this...
http://java.net/projects/oraclesoasuite11g/pages/OSB
Cheers,
Vlad

[OSB1031] how to call a RESTful service from OSB

Hi all,
I need to call a RESTful service from OSB.
The RESTful URL service is http://xxx.xxx.xxx.xxx/api/ordertracer and has been implemented in IIS.
The service accepts a xml string message as input and returns an HttpStatusCode.
So I started defining a business service (named OrderTracer):
Service Type: Any XML Service
Endpoint URI: http://xxx.xxx.xxx.xxx/api/ordertracer
HTTP Request Method:POST
Or should I define instead a business service (named OrderTracer2) as following ?
Service Type = Messaging Service
Request Message Type = None
Response Message Type = Text
Endpoint URI: http://xxx.xxx.xxx.xxx/api/ordertracer
HTTP Request Method:POST
When I try to test the business service (the first one named OrderTracer) from OSB test console I got an error:
<con:metadata xmlns:con="http://www.bea.com/wli/sb/test/config">
<tran:headers xsi:type="http:HttpResponseHeaders" xmlns:http="http://www.bea.com/wli/sb/transports/http" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<http:Connection>close</http:Connection>
<http:Content-Length>315</http:Content-Length>
<http:Content-Type>text/html; charset=us-ascii</http:Content-Type>
<http:Date>Wed, 03 Oct 2012 14:26:39 GMT</http:Date>
<http:Server>Microsoft-HTTPAPI/2.0</http:Server>
</tran:headers>
<tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">3</tran:response-code>
<tran:response-message xmlns:tran="http://www.bea.com/wli/sb/transports">Not Found</tran:response-message>
<tran:encoding xmlns:tran="http://www.bea.com/wli/sb/transports">us-ascii</tran:encoding>
<http:http-response-code xmlns:http="http://www.bea.com/wli/sb/transports/http">404</http:http-response-code>
</con:metadata>
Could I test that RESTful service from business service test console or should I test it from a service callout within a proxy service ?
Thanks in advance for any hints!
ferp

Hi,
There's a sample on JSON REST here...
http://java.net/projects/oraclesoasuite11g/downloads/download/OSB/osb-206-JSONREST.zip
For other samples, see this...
http://java.net/projects/oraclesoasuite11g/pages/OSB
Cheers,
Vlad

SOA Suite 11.1.1.4.0 - Unable to invoke REST service from BPEL

Hi all,
I am trying to invoke a REST service from BPEL.
I am supposed to call the following REST URL:
http://apolloiserdev.corp.webex.com/ExportComplianceWS/webresources/ECCheck/emailDomainCheck/[email protected]
In order to achieve this:
1. I created an empty composite
2. Added a HTTP Binding as external reference
     2.1 In the HTTP Binding wizard, I copied the above URL in 'Endpoint'
     2.2 Operation Name --> request-response
     2.3 Verb --> GET
     2.4 Created XSD for Req and resp and added those in 'Messages'
Now, when I deploy and test this process, I get the following error messages:
Unable to access the following endpoint(s): REPLACE_WITH_ACTUAL_URL
Unable to access the following endpoint(s): http://apolloiserdev.corp.webex.com/ExportComplianceWS/webresources/ECCheck/emailDomainCheck/[email protected]/ExportComplianceWS/webresources/ECCheck/emailDomainCheck/[email protected]
However, when I open the same URL using my web browser or test it using Mozilla REST client, I get a success response.
Am I missing out something in my BPEL process?
Regards,
Arindam

Not sure if this helps. But for rest based services we need to create a WSDL which has http protocol and get/post method like below
types>
<message name="HttpPostParamIn">
<part name="param1" type="xsd:string"/>
<part name="param2" type="xsd:string"/>
</message>
<message name="HttpPostParamOut">
<part name="Body" element="get:Request"/>
</message>
<portType name="HttpPostParamPortType">
<operation name="PostData">
<input message="tns:HttpPostParamIn"/>
<output message="tns:HttpPostParamOut"/>
</operation>
</portType>
<binding name="HttpPostParamBinding" type="tns:HttpPostParamPortType">
<http:binding verb="POST"/>
<operation name="PostData">
<http:operation location="/EchoApp/echo"/>
<input>
<mime:content type="application/x-www-form-urlencoded"/>
</input>
<output>
<mime:mimeXml part="Body"/>
</output>
</operation>
</binding>
<service name="PostParamService">
<port name="HttpPostParamPort" binding="tns:HttpPostParamBinding">
<http:address location="http://localhost:7001"/>
</port>
</service>
<plnk:partnerLinkType name="PostParamService">
<plnk:role name="PostParamServiceProvider">
<plnk:portType name="tns:HttpPostParamPortType"/>
</plnk:role>
</plnk:partnerLinkType>
definitions>
And then use this wsdl to invoke it from BPEL.like any other wsdl using partner link.

Getting "Origin is not allowed" When Trying to Invoke RESTful Service from Another Domain

I am having problems trying to invoke my RESTful web service from a different domain. I'm well aware of the normal restrictions of cross-site / cross-domain scripting but in Oracle documentation it says that all origins are allowed by default when creating a RESTful service without using authentication.
I have created a very simple service and am trying to invoke it using jQuery.Ajax calls from a different domain and I am getting XMLHttpRequest cannot load http://address_to_my_web_service. Origin http://calling_from_address is not allowed by Access-Control-Allow-Origin.
I understand that using JSONP instead of JSON is actually the best practice around cross-site scripting but it appears as though APEX does not support JSONP because with JSONP, there are URI parameters added to the base request (callback).
I am stuck and would greatly appreciate any help.
I'm starting to wonder if this could be a bug because Oracle documentation says all origins should be allowed when using a service that does not require authentication. I also tried to force the origin to be allowed by typing it in and also using the wildcard '*' and it still did not work.
Thanks,
Mark Williamson
EDIT: It is now working after adding a URI prefix to my web service module.

The SSL handshake works differently to a browser as it is making the connections automatically.
The browser asks every time if you want to trust an expired certificate, and it also recommends not to. Its impractical to manually check every service call to say do you trust the certificate so the functionality doesn't exist. I doubt any integration product does this. Therefore there isn't a option to ignore the certificate if it has expired.
This makes sence as the certificate is untrustworthy. The whole idea around SSL is trusting the site you are communicating with, all parties need to be trusted. This stops hackers from replicating their site and intercepting data.
If the administrator of the remote site is not willing to renew the certificate, are they really interested in SSL. I suggest they expose a non SSL service.
cheers
James

What is the best approach to invoke secured REST Services from SOA

Hi there,
I've a REST service which expects username and password to access it.
To Invoke it I'm passing the credentials as properties in composite.xml under <reference> section as shown below.
<property name="oracle.webservices.auth.username" type="xs:string"
many="false" override="may">USERNAME</property>
<property name="oracle.webservices.auth.password" type="xs:string"
many="false" override="may">PASSWORD</property>
Is there any way to use OWSM to achieve the same?
Please suggest if there is better approach. I'm Using SOA Suite PS6
Thanks
JGun

For external entities, the best practice is to access the rest service in OSB (as Business Service) and if needed, virtualize the access via an Proxy Service (can be used a Web Service transaction) and than consume the OSB in SOA Suite.

Error while calling a bpel service from OSB

Hi
I try to call a BPEL service from OSB 10.3 and use these bpel url's
ormi://<hostname>:<rmi port>/<domain name>/<process name>
opmn://<hostname>:<opmn port>/<oc4j instance name>/<domain name>/<process name>
and I create a static service account with ocj4admin
when I try to run the BusinessService then I got this error
WARNING: Exception returned by remote server: {0}
com.evermind.server.rmi.RMIConnectionException: Disconnected: javax.xml.namespace.QName; local class incompatible: stream classdesc serialVersionUID = -91204487
54896609940, local class serialVersionUID = -916876369326528164
at com.evermind.server.rmi.RmiCallQueue.notifyQueuedThreads(RmiCallQueue.java:70)
at com.evermind.server.rmi.RMIClientConnection.notifyQueuedThreads(RMIClientConnection.java:208)
at com.evermind.server.rmi.RMIClientConnection.resetState(RMIClientConnection.java:147)
at com.evermind.server.rmi.RMIConnection.receiveDisconnect(RMIConnection.java:236)
at com.evermind.server.rmi.RMIClientConnection.receiveDisconnect(RMIClientConnection.java:176)
at com.evermind.server.rmi.RMIConnection.handleOrmiCommand(RMIConnection.java:208)
Please help me out.I am using SOA Server 10.1.3.4 with jdk 1.4.
Regards
Ayush
Edited by: Ayush fujitsu on Apr 6, 2010 3:36 AM

Hi i have followed the following steps which is specified in this thread
You need to follow below steps...
add a java parameter to the OSB server. Go to domains\osb_domain\bin folder and edit the setDomainEnv file and add this line to this file. set JAVA_PROPERTIES=-Dplatform.home=%WL_HOME% -Dwls.home=%WLS_HOME% -Dweblogic.home=%WLS_HOME% -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0
Step 2 is to replace the bpel jars in the bpel transport ear. Go folder osb_10.3\lib\transports and open bpel10gtransport.ear and replace the following jar files orabpel.jar, orabpel-common.jar , xmlparserv2.jar and oc4jclient.jar with the ones you can find in the soa suite 10.1.3 home.
But still i am getting the error.
I am using WLS (10.0).Is it compatible with bpel-10g protocol, because i have already called a sync BPEL process with http protocol and it worked?This thread talks about WLS(9.2)
Regards
Ayush

Problem in calling a secured service from OSB

I am trying to call a CRMOD service which is secured (username token) from OSB.
Its giving me the below error
[WliSbTransports:381304]Exception in HttpOutboundMessageContext.RetrieveHttpResponseWork.run: java.net.SocketTimeoutException: Read timed out
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at weblogic.utils.io.ChunkedInputStream.read(ChunkedInputStream.java:159)
at java.io.InputStream.read(Unknown Source)
at com.certicom.tls.record.ReadHandler.readFragment(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at java.io.SequenceInputStream.read(Unknown Source)
at java.io.SequenceInputStream.read(Unknown Source)
at weblogic.net.http.MessageHeader.parseHeader(MessageHeader.java:151)
at weblogic.net.http.HttpClient.parseHTTP(HttpClient.java:468)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:377)
at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
at weblogic.net.http.HttpURLConnection.getResponseCode(HttpURLConnection.java:965)
at com.bea.wli.sb.transports.http.HttpOutboundMessageContext.getResponse(HttpOutboundMessageContext.java:668)
at com.bea.wli.sb.transports.http.wls.HttpOutboundMessageContextWls.access$100(HttpOutboundMessageContextWls.java:26)
at com.bea.wli.sb.transports.http.wls.HttpOutboundMessageContextWls$RetrieveHttpResponseWork.handleResponse(HttpOutboundMessageContextWls.java:96)
at weblogic.net.http.AsyncResponseHandler$MuxableSocketHTTPAsyncResponse$RunnableCallback.run(AsyncResponseHandler.java:531)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)It is working fine with older version of OSB : 11gR1 (11.1.1.3.0)
Just now we have upgraded our OSB to 11gR1 (11.1.1.4.0) .
My system configuration is Windows 7 Proff 64 bit.
For the same kind of issue i have found a solution in the below thread.
Read time out when accessing .NET Web service from OSB 10.3 proxy
But there He mentioned like this : I had installed the x64 version of JRockit, but had not installed all the 64 bit components for WebLogic 10.3g.I was able to find the 64 bit IO dlls, and once installed, the errors no longer occurred.I am not sure about the mentioned *64Bit IO dlls*.
Any one Please help me to resolve the issue.
thanks in advance,
chandra

You need to download the 64bit version of weblogic installer and use a 64 bit jdk when installing weblogic. This will make sure the 64 bit ddl's are generated for you..The generated native libraries will be in Oracle_HOME/wls_103/server/native/<OS> folder.. You can check this directory whether 64 bit ddl's are available after you fix the problem.

Invoking Web Service From PL SQL package

Below is the sample code to invoke web service from pl/sql package using UTL_HTTP:
Declare
http_req UTL_HTTP.req;
http_resp UTL_HTTP.resp;
Begin
http_req :=
UTL_HTTP.begin_request
'http://'
|| lv_hosturl
-- || '.net/soa-infra/services/finance_rt/Payments/paymentsprocess_client_ep',
--new url
|| '.net/soa-infra/services/finance_rt/PaymentsReq/paymentsprocess_client_ep?WSDL',
'POST',
'HTTP/1.1'
UTL_HTTP.set_header (http_req, 'Content-Type', 'text/xml');
-- since we are dealing with plain text in XML documents
UTL_HTTP.set_header (http_req,
'Content-Length',
LENGTH (lv_soap_request)
UTL_HTTP.set_header (http_req, 'SOAPAction', '');
-- required to specify this is a SOAP communication
UTL_HTTP.write_text (http_req, lv_soap_request);
http_resp := UTL_HTTP.get_response (http_req);
UTL_HTTP.read_text (http_resp, lv_soap_respond);
UTL_HTTP.end_response (http_resp);
resp := XMLTYPE.createxml (lv_soap_respond);
End;

Hi,
there are a lot of option to make plsql web services .
First you can stay with jdev 10.1.3
Use the xmldb servlets
use jdev 11g tp4 to create plsql ws and upgrade to jdev 11g production
And I think in the next release of jdev it will be back , there are more options which disappeared like the adf bc sdo ws or jmx datacontrol etc.
thanks Edwin

Invoking web service from OBIEE11g failed socket timeout

Hi,
I encountered an error when I invoke web service from OBIEE 11g. The web serivce resides on Websphere running on other machine.
An error says that "Invoking web service failed due to socket timeout." and it seems that it stopped in just 40 secs.
Is there any settings of WebLogic server to avoid this? This web service normally runs for more than 60 sec.
I have checked several parameters in WebLogic admin console and changed those values, but I still receive the same error.
Invoking the same web service from SOAPUI sustains for more than 60 secs.
Regards,
Fujio Sonehara

Don't be too surprised. Sun figured this bug out in short order. I got the same error message when trying to do the same thing, just for the heck of it. Reference this article for details.
http://java.sun.com/webservices/docs/ea2/jaxrpc/ReleaseNotes.html
It contains information about bugs fixed in the WSDP EA2. So in answer to your question, download the newer pack from
http://java.sun.com/webservices/downloads/webservicespack.html
and your bug will go away. Happy Coding.
Legal Problems?
Legal Solutions, for a lot less than you might think.
[email protected]
http://www.prepaidlegal.com/go/pritchard45

Proxy restful services via osb

Hi,
I would like to proxy my rest services via OSB for monitoring purpose. I did configure a simple GET call to use OSB proxy, I did it by creating a business service and point the URI to use the absolute URL of the rest Services (i.e. http://localhost:port/myRestMethod) and then created a proxy service pointing to my business service. Is this the correct way of doing it? Also I have the following questions:
1. is there a way to make the URI for the rest service dynamic?
2. How should I configure a post?
I would appreciate any kind of help or if you can point me to some kind of documentation or example. I am very new to OSB and don't have much knowledge about it.
Thanks
Regards
M.

You can set the headers of the request quit similar to the ones you use for the get and delete parts. If you want to POST or PUT JSON/Xml/Text to your rest service you have to fill the $body variable with the contents of the request you want to send. When you use a proxy service I would suggest adding a route to block at the end of the PS. The route block contains a route to the business service you want to call.
When you send the $body in the request pipeline to the business service the $body variable gets updated when the business services receives a response.
What I usually do is add reporting blocks to your request and response pipelines that contain the $body and $header vars. That way it's easy to see what requests you are sending and what kind of responses you are retrieving.
Good luck!

Calling a RestFUL service from a SOA composite

Hi,
I had thought a simple google search would have bought up the answer to this question but it dosn’t seem to have done so.
I have to create a composite in 11.1.1.5 which has to call a restful sercice. Can anyone point me in the direction of a tutorial which describes how to do this.
Thanks
Robert

That article looks intresting but:
1. The pictures don't seem to be loading for me. Since they show a few of the steps this is quite important
2. It talks about the httpbinding adapter which was removed when the article was written. This seems to be back now
3. It uses tonnes and tonnes of Java.
Can I conclude from this that it is not possible to call restful services from SOA without writing Java code?

Error while invoking web services from Proxy services in OSB

I have a Proxy Service of message type in Oracel Service Bus 10gR3 and it passes the incoming messages from a JMS Queue to Business Service of Web Services type. This Web Service is hosted in Glass Fish v3 and it's binding style is RPC. The JRE used in both the servers are 1.6.0_20. The JMS message is of Text type. The Web Services at the Glass Fish throws MessageCreationException for any content of the JMS message. However, it works fine if Business Service's test client is invoked from the OSB'S Admin Console. However, the same will not work if Proxy Service's test client is called.
The detailed exception stack is given below :
Thanks for the help.
- Raj
com.sun.xml.ws.protocol.soap.MessageCreationException: Couldn't create SOAP message due to exception: XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
     at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:359)
     at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:318)
     at com.sun.xml.ws.transport.http.HttpAdapter.access$500(HttpAdapter.java:92)
     at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:501)
     at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:285)
     at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:143)
     at org.glassfish.webservices.Ejb3MessageDispatcher.handlePost(Ejb3MessageDispatcher.java:116)
     at org.glassfish.webservices.Ejb3MessageDispatcher.invoke(Ejb3MessageDispatcher.java:87)
     at org.glassfish.webservices.EjbWebServiceServlet.dispatchToEjbEndpoint(EjbWebServiceServlet.java:196)
     at org.glassfish.webservices.EjbWebServiceServlet.service(EjbWebServiceServlet.java:127)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
     at com.sun.grizzly.http.servlet.FilterChainImpl.doFilter(FilterChainImpl.java:195)
     at com.sun.grizzly.http.servlet.FilterChainImpl.invokeFilterChain(FilterChainImpl.java:139)
     at com.sun.grizzly.http.servlet.ServletAdapter.doService(ServletAdapter.java:376)
     at com.sun.grizzly.http.servlet.ServletAdapter.service(ServletAdapter.java:329)
     at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166)
     at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100)
     at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:245)
     at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791)
     at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693)
     at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954)
     at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170)
     at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135)
     at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
     at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
     at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
     at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
     at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
     at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
     at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330)
     at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309)
     at java.lang.Thread.run(Thread.java:619)
Caused by: com.sun.xml.ws.streaming.XMLStreamReaderException: XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col {unknown-source}]: [1,0]
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.wrapException(XMLStreamReaderUtil.java:267)
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.next(XMLStreamReaderUtil.java:95)
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextContent(XMLStreamReaderUtil.java:110)
     at com.sun.xml.ws.streaming.XMLStreamReaderUtil.nextElementContent(XMLStreamReaderUtil.java:100)
     at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:175)
     at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:303)
     at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:129)
     at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:354)

Let me explain what I am trying to achieve. Our application receives data from multiple sources - from mainframe using FTP, JMS Queue and BPM application using Web Services. The data from all these sources are sending to a Web Service running in GlassFish V3. To handle this I have created three Proxy Services and one Business Service on OSB. The Business Service is of type Web Service using the same WSDL from the target Web Service.
The Proxy Services are configured as follows:
Proxy 1 (type - Messaging service) listens to the JMS Queue and receives JMS Text Message -> Business Service(B1) (Web Service).
Proxy 2 (type - Messaging service Polls files from the FTP Server -> Business Service(B1) (Web Service).
Proxy 3 (type - Web service) is invoked by the BPM application and sends a String -> Business Service(B1) (Web Service).
All the Proxies route to the same Business Service - B1 which calls the Web Service in GlassFish. The only Proxy that works fine is Proxy 3 which is created using the same WSDL of the Web Service. In the other two proxies it thows the same exception in GlassFish as I mentioned before.
com.sun.xml.ws.protocol.soap.MessageCreationException: Couldn't create SOAP message due to exception: XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog at [row,col {unknown-source}]: [1,0] at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:359)
Is this configuration correct to achieve my requirements?
Once again thanks for the help.
- Raj

Invoking HTTP Restful services using OSB

Hi,
We have a reuirement to invoke below three URL's from OSB in sequence .
like
1.http://<IP Address:Port>/login
2.http://<IP Address:Port>/getlist
3.http://<IP Address:Port>/logout
I have used three service callouts to invoke the same.
Login service callout is giving the success response but the 2nd service is throwing the error as "Unauthorized"
Three url's should be invoked in the same session i.e 2nd service should be invoked in the same session as of login service or else it will give error.
I have enabled the "Transaction Required" flag and also set the QoS to "Exactly Once" but still giving the error.
Can anybody please let me know if there is any another way to maintain the session.
Thanks in advance.

401 Unauthorized most likely means you have lost a cookie.
On your first call to login the server sets HTTP header Set-Cookie; you get it back as User Headers. In response flow of the login call you need to get the value of the Set-Cookie and save it into a variable.
On the second and third call you'll have to set Custom Header "Cookie" to the value you get from Set-Cookie.
This is purely HTTP mechanism, transactions or QoS have nothing to do with it.

Invoking service from OSB throws Request Entity Too Large fault

Invoking .net service with large(>1M) base64Binary field from OSB returns "BEA-380000:Request Entity Too Large" error.
How to enlagre the maximum message size?

You have to slightly adjust WebLogic configuration:
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/config_wls/web_server.html#wp1059784

Invoking RESTful service from OSB

Similar Messages

Maybe you are looking for