Axis 2 Vs OSB

Hi All,
Is it possible to generate Webservices from Java classes as we do in Axis 2?
I know we could call webservices from OSB and host webservices in proxy services.But could we generate Webservices from Java classes as we do in Axis 2?
Thanks.

one sec:
- you can deploy a WebService in WebLogic, and expose it through a BusinessService in OSB.
- you can write a Proxy Service in OSB, and expose it as a Web Service
but you don't "deploy a Java Class as a WebService" inside OSB.
OSB can only run Proxy Services or Business Services. For WebService deployment just use the normal deployment process
of a .war in WebLogic.
I would suggest that you:
Phase 1:
- write a JAX-WS Java Class using JDeveloper (follow the link provided by Eric above)
- deploy this WebService in Weblogic
- test it
Phase 2:
- generate the WSDL and import it into OSB
- generate the Business Service from this WSDL
- generate a ProxyService to expose this Business Service
- test it
at this point you will have generated a "Proxy" Web Service for your original WebService - if this is what you need.
Otherwise forget OSB and just deploy and access your WebService in WebLogic.
I hope I haven't created too much confusion :o)

Similar Messages

Axis webservice through OSB

I have a web service which developed using axis and deployed in weblogic.
I have configured in OSB to access this web service through OSB.
My endpoint is OSB server URL which points axis webservice deployed in weblogic.
I have user id and [assword set through OSB.
*My Question:*
When i access this OSB end point from a Java Client Application, I need to give provide userid/password. How do I give?
I tried below and didnt work and got below error messages also.
             MyWebServiceStub stub = new MyWebServiceStub(endpoint);
            org.apache.axis2.client.ServiceClient sc = stub._getServiceClient();
            org.apache.axis2.client.Options options = sc.getOptions();
            options.setUserName(user);
            options.setPassword(password);
The above code gives me below error
INFO: Unable to sendViaPost to url[endpoint]
org.apache.axis2.AxisFault: Transport error: 404 Error: Not Found
     at org.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:296)
     at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:190)
Can anyone help me find out? How do we access?

Looks like the URL is wrong.. ( 404 error). Make sure the url is pointing to OSB managed server port and not to the admin server.. sbconsole runs on admin server but the port you specifiy in the URL used to access OSB from the webservice client should point to the osb managed servers...

How to handle multiRef responses in OSB 10.3???

We are using OSB 10.3 version.
I am getting difficulty to get the multiRef soap response in the Service Callout*:
When I check the SBConsole Invocation Trace the whole response body is appearing in business service but returning part of the response.
Its missing the multiRef as below:
<ns4:getProductServiceRequestForUserResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns4="abc:ProductManagementService">
<getProductServiceRequestForUserReturn href="#id0"/>
</ns4:getProductServiceRequestForUserResponse>
It should return
<soapenv:Body>
<ns4:getProductServiceRequestForUserResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns4="abc:ProductManagementService">
<getProductServiceRequestForUserReturn href="#id0"/>
</ns4:getProductServiceRequestForUserResponse>
<multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns5:ProductLinkRequest"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns5="http://ato.domain.services.abc.com">
<id xsi:type="xsd:long">3068</id>
<requestStatus href="#id1"/>
<modifiedDate xsi:type="xsd:dateTime">2009-06-23T01:22:02.000Z</modifiedDate>
<prd xsi:type="xsd:string">249249</prd>
<serviceNo href="#id2"/>
<statusReason xsi:type="xsd:string">Delivery completed</statusReason>
</multiRef>
</soapenv:Body>
After Service Callout, I have tried to assign the reponse to valriable but it returns missing multiRef
$body/multiRef
Any suggestions??
Thank you
Edited by: user11310683 on Sep 1, 2011 5:20 AM
Edited by: user11310683 on Sep 2, 2011 2:48 PM

Getting difficulty to use Java Callout.
I have written my java class to call webservice and kept all necessary jars in the lib with MANIFEST file.
I kept all my jars in project/Resources/JAR/*.jar and included all dependency jar to my generated jar.
But the Java Callout is thowing java.lang.NoClassDefFoundError: javax/wsdl/OperationType
at org.apache.axis.description.OperationDesc.<clinit>(OperationDesc.java:59)
Its working fine when I copied all jars in user_project/domains/proj_domain/lib.
But I don't want to put all my jars at user_project/domains/proj_domain/lib.

OSB WSDL invocation from java /jsp client!

Hi ,
I did a sample work on invoking osb wsdl(based on DB adapter) from a java/jsp application.It worked fine!
Its a simple select query wth parameter that was configured in my DB adapter.
Below are the steps I follow -
a.Created a DB adapter for collective response
b.created BS out of jca
c.Generated PS based on above BS.
d.Performed some xquery tranformation in PS message flow response piepeline.
e.Exported WSDL and tested it in SOAP UI ,getting the transformed response as required.
When we generate Java client out of above WSDL in Eclipse ,it generates client for DB data,transformed data fields are not seen -How to obtain transformed data too through Java client?will this work ?
Is it gud practice to generate java client directly n Eclipse (OEPE) or do we have any other alternative ways to generate Java client out of OSB WSDL?
Please assist.
Thanks,
Ani

Hi Anuj-
My proxy was generated out of business ,i get 2 wsdl like master-child .Master wsdl holds referecnce to child wsdl.I hope wsdl generation is fine.
When i invoke the proxy wsdl url from Java client ,i get below error -
Exception in thread "main" AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Invalid element in com.oracle.xmlns.pcbpel.adapter.db.PhysicalTampered_Meter.PhysicalTampered_MeterOutput - PhysicalTampered
faultActor:
faultNode:
faultDetail:
     {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException: Invalid element in com.oracle.xmlns.pcbpel.adapter.db.PhysicalTampered_Meter.PhysicalTampered_MeterOutput - PhysicalTampered
     at org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.java:258)
     at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
     at org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:165)
     at org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:1141)
     at org.apache.axis.message.RPCElement.deserialize(RPCElement.java:236)
     at org.apache.axis.message.RPCElement.getParams(RPCElement.java:384)
     at org.apache.axis.client.Call.invoke(Call.java:2467)
     at org.apache.axis.client.Call.invoke(Call.java:2366)
     at org.apache.axis.client.Call.invoke(Call.java:1812)
     at com.oracle.xmlns.pcbpel.adapter.db.CoreAnalytics.PhysicalTampered_Meter.PhysicalTampered_Meter.PhysicalTampered_Meter_pttBindingStub.physicalTampered_Meter(PhysicalTampered_Meter_pttBindingStub.java:175)
     at Client.JavaClient.main(JavaClient.java:25)
     {http://xml.apache.org/axis/}hostname:B7B-3F-149-4HJV

OSB How access data "userException" from proxy

Hi all,
Although I have read on this forum some similar post, the proposed solution does not work for me.
We have: Proxy created from the Business ---> from WSDL Business ---> Web-Service
I have a test SOAP message passes a parameter wrong, If I make a test:
1) SoapUi -> Web-Service:
Occurs the error:
<faultcode> soapenv: Server.userException </ faultcode>
<faultstring> java.rmi.RemoteException: Application XNFI is not authorized. </ faultstring>
2) SoapUi -> Proxy -> Business -> Web-Service: Error
Occurs the error:
<faultcode> soapenv: Server </ faultcode>
<faultstring> BEA-380001: Internal Server Error </ faultstring>
As I read in the forum, the solution maybe to capture $fault in Route Error handler, but in my case, this variable contains:
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-380001</con:errorCode>
<con:reason>Internal Server Error</con:reason>
<con:location>
<con:node>RouteTo_ServicioSMSMenTes</con:node>
<con:path>response-pipeline</con:path>
</con:location>
</con:fault>>
I made report of all variables (head, body, inbound, outbound, fault, attachment) but I can´t see “userException”.
However, when trace OSB, in log file, I can see the information that I need: (see Payload)
Service Ref = MENT_OSB / private / definicion_servicios / ServicioSMSMenTes_BS
URI = http://icmaplides01:7778/mentes_ws/services/ServicioSMSMenTes
Error code = BEA-380001
Error Message = Internal Server Error
Message-ID = 4703094898779781414 779b49a0.12ea6706e31.-7ee4
Response metadata =
<xml-fragment>
<Tran: headers xsi: type = "http:HttpResponseHeaders" xmlns: http = "http://www.bea.com/wli/sb/transports/http" xmlns: trans = "http://www.bea.com / wli / sb / transports "xmlns: xsi =" http://www.w3.org /2001/XMLSchema-instance ">
name="Set-cookie" <tran:user-header value="HTTPSession=algo.d017778"/>
<http:Cache-Control> private </ http:Cache-Control>
<http:Connection> close </ http:Connection>
<http:Content-Type> text / xml; charset = utf-8 </ http:Content-Type>
<http:Date> Wed, 16 Mar 2011 12:01:12 GMT </ http:Date>
Oracle-Application-Server-10g/9.0.4.2.0 <http:Server> Oracle-HTTP-Server </ http:Server>
<http:Transfer-Encoding> chunked </ http:Transfer-Encoding>
</ Tran: headers>
<tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports"> 2 </ tran: response-code>
xmlns:tran="http://www.bea.com/wli/sb/transports"> <tran:response-message Internal Server Error </ tran: response-message>
xmlns:tran="http://www.bea.com/wli/sb/transports"> <tran:encoding utf-8 </ tran: encoding>
xmlns:http="http://www.bea.com/wli/sb/transports/http"> <http:http- response-code 500 </ http:http-response-code>
</ Xml-fragment>
Payload =
<? Xml version = "1.0" encoding = "utf-8"?> <Soapenv: Envelope xmlns: soapenv = "http://schemas.xmlsoap.org/soap/envelope/" xmlns: xsd = "http:// www.w3.org/2001/XMLSchema "xmlns: xsi =" http://www.w3.org/2001/XMLSchema-instance "> <soapenv:Body> <soapenv:Fault> <faultcode> soapenv: Server.userException </ faultcode> <faultstring> java.rmi.RemoteException: Application XNFI is not authorized. </ faultstring> <detail> <ns1: hostname xmlns: ns1 = "http://xml.apache org / axis / "> icmaplides01.icm.es </ ns1: hostname> </ detail> </ soapenv: Fault> </ soapenv: Body> </ soapenv: Envelope>
How I can access Payload to catch the user error?
Thank you very much,
Victor Muñoz

Hi Anuj,
The variable $body of errror handle hasn´t data, it´s empty.
However i tested another web-service, and the message error is into $body. Therefore, it seems to be a problem of web-service. We will seek what is the cause, it will be util to detect the same problem with other web-service.
Thanks,
Regards,
Victor.

Service Bus(OSB) not harvesting Endpoint to Enterprise Repository(OER)

Hi,
I am harvesting a WSDL-based HTTP Proxy Service from Oracle Service Bus (OSB) to Oracle Enterprise Repository (OER) but the Endpoint is not harvested. The other artifacts are harvested successfully.
Can someone please help
Thanks,
Umar

Hi Anuj,
Here is the info you requested:
*1. Exactly which version of OSB and OER are you using?*
OSB version: Oracle Service Bus 11.1 Sun Dec 18 03:49:34 PST 2011 1447174
OER version: Oracle® Enterprise Repository 11.1.1.6.0 (v11.1.1.6.0-111103_0001-1437995)
*2. What type of proxy services are you publishing?*
Proxy Type: Web Service - SOAP 1.1 (WSDL:OSB_PR_POC/OpenAccount, port="OpenAccountServicePort")
My proxy service routes to business service.
*3. If it is a WSDL based proxy then are you able to see enpoint URL in exported WSDL from proxy?*
OSB shows the Endpoint information(Endpoint URI /OSB_PR_POC/PS_OpenAccount)
I don't exactly understand what you mean by 'exported WSDL'
*4. Did you harvested the configuration from OSB machine itself?*
The OSB and OER are on the same machine. Used the OSB command line harvester to harvest the project. So, Yes, harvested the configuration from OSB machine.
*5. Can you provide the harvesting log?*
Please find below the logs:
E:\Oracle\Middleware\Oracle_OSB1\harvester>"C:\PROGRA~1\Java\JDK17~1.0_0\bin\java" -Dweblogic.home="E:\Oracle\MIDDLE~1\WLSERV~1.3" -Dosb.home="E:\
Oracle\MIDDLE~1\ORACLE~2" com.oracle.oer.sync.framework.Introspector -harvester_home "E:\Oracle\MIDDLE~1\ORACLE~2\harvester"
log4j:WARN No appenders could be found for logger (org.apache.axis.i18n.ProjectResourceBundle).
log4j:WARN Please initialize the log4j system properly.
+0 [main] INFO com.oracle.oer.sync.framework.MetadataManager - Oracle Enterprise_Repository_Harvester version: v11.1.1.6.0-111020_0001-1434818+
+250 [main] INFO com.bea.alsb.harvester.container.OSBInstance - OSB Harvester created a temporary directory (C:\Users\c74945\AppData\Local\Temp\3\OS+
B11gConfig) for the configuration framework data. This directory will not be automatically deleted.
+<Aug 29, 2012 12:03:21 PM AST> <Info> <OSB Offline> <BEA-000000> <Initialing ALSB in offline mode. Install dir: E:\Oracle\MIDDLE~1\ORACLE~2 config dir+
+: C:\Users\c74945\AppData\Local\Temp\3\OSB11gConfig>+
+<Aug 29, 2012 12:03:23 PM AST> <Alert> <OSB Security> <BEA-387042> <There is no user password credential mapper provider configured in your security r+
ealm. Oracle Service Bus service account management will be disabled. Configure a user password credential mapper provider if you need OSB service acc
ount support.>
+<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "Resource SDK".>+
+<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "Resource SDK" initialized.>+
+<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "Custom Resource SDK".>+
+<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "Custom Resource SDK" initialized.>+
+<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "XSLT Resource".>+
+<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "XSLT Resource" initialized.>+
+<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "XML Schema Resource".>+
+<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "XML Schema Resource" initialized.>+
+<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "MFL Resource".>+
+<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "MFL Resource" initialized.>+
+<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "WS-Policy Resource".>+
+<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "WS-Policy Resource" initialized.>+
+<Aug 29, 2012 12:03:25 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "WSDL Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "WSDL Resource" initialized.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "XQuery Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "XQuery Resource" initialized.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "JCA Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "JCA Resource" initialized.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "XML Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "XML Resource" initialized.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "Archive Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "Archive Resource" initialized.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "JNDI Provider Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "JNDI Provider Resource" initialized.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "SMTP Server Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "SMTP Server Resource" initialized.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "Proxy Server Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "Proxy Server Resource" initialized.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "Global Settings Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "Global Settings Resource" initialized.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "UDDI Registry Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "UDDI Registry Resource" initialized.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397037> <Initializing Proxy Service Repository>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397038> <Proxy Service Repository Intialized>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397039> <Initializing Business Service Repository>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397040> <Business Service Repository Intialized>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397001> <Initializing type definitions for module "FLOW Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397002> <Type definitions for module "FLOW Resource" initialized.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "Resource SDK".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "Resource SDK" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "Custom Resource SDK".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "Custom Resource SDK" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "XSLT Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "XSLT Resource" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "XML Schema Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "XML Schema Resource" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "MFL Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "MFL Resource" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "WS-Policy Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "WS-Policy Resource" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "WSDL Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "WSDL Resource" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "XQuery Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "XQuery Resource" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "JCA Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "JCA Resource" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "XML Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "XML Resource" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "Archive Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "Archive Resource" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "JNDI Provider Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "JNDI Provider Resource" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "SMTP Server Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "SMTP Server Resource" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "Proxy Server Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "Proxy Server Resource" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "Global Settings Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "Global Settings Resource" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "UDDI Registry Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "UDDI Registry Resource" started.>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <Monitoring> <BEA-000000> <New Metadata version is 0>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397003> <Starting services for module "FLOW Resource".>+
+<Aug 29, 2012 12:03:26 PM AST> <Info> <ALSB Kernel> <BEA-397004> <Services for module "FLOW Resource" started.>+
+<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390020> <Config Service is initializing for the first time>+
+<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Project System>+
+<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Project _static>+
+<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Project default>+
+<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Folder System/JNDI Providers>+
+<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Folder System/Operator Settings>+
+<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Folder System/Proxy Servers>+
+<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Folder System/SMTP Servers>+
+<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390021> <Creating out-of-the-box location: Folder System/UDDI>+
+<Aug 29, 2012 12:03:28 PM AST> <Info> <ConfigFwk> <BEA-390022> <Creating out-of-the-box resource: Operations System/Operator Settings/GlobalOperationa+
lSettings>
+8393 [main] INFO com.bea.alsb.harvester.plugin.reader.OSBReader - OSB Config Jar Import / Validation starting.+
+10452 [main] INFO com.bea.alsb.harvester.plugin.reader.OSBReader - OSB Config Jar Import / Validation complete.+
+61402 [main] INFO com.oracle.oer.sync.framework.MetadataManager - Successfully completed the harvest+
Starting OERWriter Shutdown and Clean up...
Let me know if you need anymore info.
Thanks.

OSB: Proxy Service and Dispatch Policy

Hi all,
I'm trying to use OSB (10.3) proxy service with dispatch policy set to WebLogic (10.3) work manager to limit maximum number of threads allocated for request to this proxy service.
It seems to me that whole dispatch policy setting is ignored in OSB. The situation is like this: I have simple Axis based web service with wait method that just waits for few seconds (based on request parameter). I use this service for testing (hm, so far just for trying to understand) OSB dispatch policy function.
Using soapUI I created a simple load test which uses 10 threads to call wait(10) - it means "wait for 10 seconds". Time limit for the whole load test is set to 20 seconds. It is clear that the total execution count is 2 x 10 = 20. So far, so good.
Then I created simple proxy service in OSB that just routes request to business service representing my Axis service with wait method. I set a dispatch policy for the proxy service to WorkManager-2threads (see below) and I expected that running the same load test with endpoint set to OSB would result in significant lower total execution count. I expected that because WebLogic should allocate 2 threads at most for all requests to this proxy service. However, that's not the case as the result is the same as in the first (Axis only) test. Just as there was no dispatch policy settings at all ...
Where is the problem?
This is the relevant part of my WebLogic configuration regarding work manager:
<max-threads-constraint>
<name>MaxThreadsConstraint-2</name>
<target>AdminServer</target>
<count>2</count>
<connection-pool-name></connection-pool-name>
</max-threads-constraint>
<work-manager>
<name>WorkManager-2threads</name>
<target>AdminServer</target>
<max-threads-constraint>MaxThreadsConstraint-2</max-threads-constraint>
<capacity xsi:nil="true"></capacity>
<ignore-stuck-threads>false</ignore-stuck-threads>
</work-manager>

It's same problem to me. I do pressure test by loadrunner,I deployed two separate proxy service,under same concurrent user,I get same TPS from the two proxy service.but when I add low priority concurrent user,low priority TPS up.
I set the Route option as you say,but weblogic hanged immediately,and can't be accessed by the console.

[OSB and OWSM] - External Web service stacks and frameworks

Hi everyone ! I'm starting to read about OSB and OWSM and I'm having some doubts. I've some developments of Web services with external Stacks like CXF, JBossWS, Metro and I'd like to ask some questions:
1- Will I be able to productively leverage all features of OSB and OWSM like creating a proxy service to add WS-* standards policies and features (WS-Security, for instance) even with these web services implemented in different stacks other than Weblogic's ?
2- If it is possible, do these web services need to be deployed at the Weblogic server to enable the OWSM and OSB to work effectively ?
3- Even if it is possible to use the OSB and OWSM nicely with webservices developed at external stacks and deployed at other application servers is there any reason to quit using these external web service stacks in favor of Weblogic's (like features only enabled on OSB/OWSM when the services use the Weblogic stack) ?
I suppose that if I ignore the JAX-WS stack from Weblogic and use an external framework (like CXF) I'll lose most of the application server administration capabilities since the Weblogic server won't be able to recognize the CXF stack as it does with its own.But, the main doubt I'm in is, since OSB and OWSM might be used with external providers I probably won't need to develop my web services using the Weblogic implementation (which my team does not yet know) since there will be no features of the OSB and OWSM which can only be used with the Weblogic's stack. I would like, please, to know your oppinions about these considerations. Sorry about the long post and possible errors (I just started learning).
Thank you!

Hi Lupan,
I can speak mostly to OWSM as my experience with OSB is small thus far.
+1- Will I be able to productively leverage all features of OSB and OWSM like creating a proxy service to add WS-* standards policies and features (WS-Security, for instance) even with these web services implemented in different stacks other than Weblogic's ?+
OWSM (10gR3) has two types of policy enforcement point (PEP) -- Gateway and Agent. The Gateway acts as a remote proxy and is neutral to the service implementation technology as long as it adheres to SOAP 1.1. In this regard you can use OWSM freely with CXF, MS implementations, etc. Agents run in-process with the service and thus have far greater restrictions on what service implementation frameworks and containers that are supported. There is some certification for AXIS 1.x running in OAS and Tomcat; but practically speaking, my recommendation for Agents is to only use within OAS 10gR3 where it is built in (and using OC4J Web Services through JAX-RPC).
OWSM 11gR1 initially supports only agent-style (in process) PEP and is built-in to Fusion Middleware and WLS. It is only for Fusion and WLS Web Service implementations.
OWSM is quite full-featured for WS-*.
+2- If it is possible, do these web services need to be deployed at the Weblogic server to enable the OWSM and OSB to work effectively ?+
"No" if using OWSM Gateway PEP. A qualified "Yes" if using OWSM Agent PEP.
+3- Even if it is possible to use the OSB and OWSM nicely with webservices developed at external stacks and deployed at other application servers is there any reason to quit using these external web service stacks in favor of Weblogic's (like features only enabled on OSB/OWSM when the services use the Weblogic stack) ?+
There is the manageability that you mention, but also there is the identity propagation scenario and tight security integration. Both OAS and WLS hosted services in the native stacks (JAX-RPC and JAX-WS) allow sophisticated and secure passing of identity in the request -- for instance, via SAML Assertions in the WS-Sec header -- and built-in capabilities to map the passed identity into the running service's Subject (i.e. enabling JAAS security etc.).
In my experience this type of identity propagation functionality has either been absent or less complete in other typical implementation frameworks not closely aligned with the container security mechanisms.
Hope this helps,
Todd

JDeveloper WS Security Client Proxy - Axis WS

Hi everybody
i'm using JDeveloper 10.1.3.3.0.
I'm trying to connect to a webservice developed by a external provider. The external provider used axis (i dont know what is its version nor nothing about its configuration) to create the ws. When i test the ws client proxy, the ws developed in axis returns the following fault:
javax.xml.rpc.soap.SOAPFaultException: WSDoAllReceiver: security processing failed (actions mismatch)
     at oracle.j2ee.ws.client.StreamingSender._raiseFault(StreamingSender.java:555)
     at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:396)
     at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
Reading the axis documentation, i found that the problem could be the order and the quantity of the ws security header elements. In my case, i'm trying with only the Signature and Timestamp elements (In that order). The external provider told me that those are the actions expected by them. So, the logical alternative than probably solve this problem is to switch the order of the ws security header elementes (Firts Timestamp, then Signature).
I created the ws proxy using the jdeveloper wizard. Then, i modified the xxxSoapBinding_Stub.xml like this:
<oracle-webservice-clients xmlns:....
<runtime enabled="security">
<security>
<key-store name="myks" path="c:/temp/cert/myks.jks" store-pass="password"/>
<signature-key alias="test" key-pass="password"/>
<encryption-key alias="test" key-pass="password"/>
<inbound/>
<outbound>
<signature>
<signature-method>RSA-SHA1</signature-method>
<tbs-elements>
<tbs-element local-part="Body" name-space="http://schemas.xmlsoap.org/soap/envelope/"/>
</tbs-elements>
<add-timestamp created="true" expiry="28800" />
</signature>
</outbound>
</security>
</runtime>
<operations>
<operation name="queryDeclarations">
</operation>
</operations>
</port-info>
</webservice-client>
</oracle-webservice-clients>
This is the ws security header generated by my proxy client in this moment:
<wsse:Security
     xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
     xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
     xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
     env:mustUnderstand="1">
     <wsse:BinarySecurityToken
          xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
          xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
          ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"
          EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"
          wsu:Id="_6F60NR6IXB2dYJCgIYy9JA22"
          xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
          MIIGLzCCBRegAwIBAg...
     </wsse:BinarySecurityToken>
     <dsig:Signature xmlns="http://www.w3.org/2000/09/xmldsig#"
          xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
          <dsig:SignedInfo>
               <dsig:CanonicalizationMethod
                    Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
               <dsig:SignatureMethod
                    Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />
               <dsig:Reference URI="#MOmq8nF2iGaNEXc4TEN0ew22">
                    <dsig:Transforms>
                         <dsig:Transform
                              Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                    </dsig:Transforms>
                    <dsig:DigestMethod
                         Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                    <dsig:DigestValue>
                         ExIbc9ws2rIxB4j8DD64y3kjSoA=
                    </dsig:DigestValue>
               </dsig:Reference>
          </dsig:SignedInfo>
          <dsig:SignatureValue>
               ieZtnbn2ytnmyE8fL9lO10nwzYARHu...
          </dsig:SignatureValue>
          <dsig:KeyInfo>
               <wsse:SecurityTokenReference
                    xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
                    xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
                    <wsse:Reference
                         xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
                         xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
                         URI="#_6F60NR6IXB2dYJCgIYy9JA22"
                         ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" />
               </wsse:SecurityTokenReference>
          </dsig:KeyInfo>
     </dsig:Signature>
     <wsu:Timestamp
          xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
          xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
          <wsu:Created>2010-04-29T23:17:38Z</wsu:Created>
          <wsu:Expires>2010-04-30T07:17:38Z</wsu:Expires>
     </wsu:Timestamp>
</wsse:Security>
is there any way to switch the ws security header elements using jdeveloper or does exist some diferent thing that i can do?
I try using Handlers to capture the SOAPMessage object with the request before it were send. But, on that moment the ws security headers are not present yet in the request. It seems that the request is proceced later behind the scenes :(.... maybe far away from my develpment workspace scope :).
Anyone has tried to do something like i trying to do??
any suggestion?
Thanks in advance
Javier Murcia

I thought you were getting that exception when accessing the proxy.
No. Authentification works fine. Proxy body works fine. But at the end of proxy appears the exception.
Sorry for my english - I tried to show this situation on image: http://imglink.ru/show-image.php?id=9c0e0c1719f00289faf11696c6703bc3
Are you getting this exception when routing to a business service which is configured for WS-Security ??
I don't use business service in this test project - only simple proxy service with all logic inside.
PS transformation in replace action is very simple too:
(:: pragma bea:global-element-parameter parameter="$newOperation1" element="ns0:NewOperation" location="WSSecurityService.wsdl" ::)
(:: pragma bea:global-element-return element="ns0:NewOperationResponse" location="WSSecurityService.wsdl" ::)
declare namespace ns0 = "http://www.troika.ru/Enterprise/WSSecurityService/";
declare namespace xf = "http://tempuri.org/OSB%20Project%20WS-Security/Hello/";
declare function xf:Hello($newOperation1 as element(ns0:NewOperation))
as element(ns0:NewOperationResponse) {
<ns0:NewOperationResponse>
<out>Hello, { data($newOperation1/in) }!</out>
</ns0:NewOperationResponse>
declare variable $newOperation1 as element(ns0:NewOperation) external;
xf:Hello($newOperation1)
Edited by: Andrey L. on Jun 10, 2010 12:21 PM

Deployer:149150 Getting OSB deployment error

Hi All,
When we deploy a java webservice in OSB server it work fine but after that OSB deployment stop and we are not able to deploy any osb application. we get the below error.
*java.rmi.RemoteException: [Deployer:149150]An IOException occurred while reading input. : with response code '500' : with response message 'Internal Server Error'*
Our java webservice have few dependent jar like axis library which we put in domain lib folder.
Thought we remove all the custom jar from OSB domain lib folder but still we are getting a same error. please let me know how to deal with such error. we dont want to recreate a domain again.

Check the OSB server log to find out any errors during the deployment. Also let us know the exact version of OSB and weblogic, you are working with.
Regards,
Anuj

OSB - Handling multiRef responses?

I have to connect to an Axis webservice which forces multiRef.
Does anyone have suggestions for working with the response? Is there any Oracle tools which will help here so I can properly use XPath?
(I've also noticed behavior difference between Service Callout and Route, shown below)
*Here is what OSB gets in the body coming back from Proxy Service Route to the business service:*
<ns1:getHeaderResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://bd.ews.xxxxx.com" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<getHeaderReturn href="#id0"/>
</ns1:getHeaderResponse>
*Yet here is the SOAP response when I test the Business Service directly or call it via Proxy Service Service Callout*:
     <soapenv:Body>
     <ns1:getHeaderResponse      soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://bd.ews.xxxxx.com">
     <getHeaderReturn      href="#id0"/>
     </ns1:getHeaderResponse>
     <multiRef      id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:DealHeader" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:ews-structs">
     <agent_deal_fl      xsi:type="xsd:string">N</agent_deal_fl>
     <attach_fl      xsi:type="xsd:string">N</attach_fl>
     <bd_id      xsi:type="xsd:string">5449DDF</bd_id>
     <bd_version_nr      xsi:type="xsd:int">1</bd_version_nr>
     <beg_dt      xsi:type="xsd:string">16-Jul-2010 00:00</beg_dt>
     <end_dt      xsi:type="xsd:string">30-Sep-2011 00:00</end_dt>

</multiRef>
</soapenv:Body>
I also found this thread stating SOA/BPEL team does not support it -- hoping Aqualogic did provide some type of support...
About multiRef

Anuj Dwivedi wrote:
I could successfully get the value of bd_version_nr using below expression -
Assign [ $body/multiRef/bd_version_nr/text() ] to [ var1 ]The limitation and problem here is if I had multiple multiRef responses. I don't want to hard-code id0 as its dynamic. See below for example. It would be easiest if OSB would sort out appropriate multiRef structures since it knows the schema already.
example:
+<soapenv:Body>+
+<ns1:getHeaderResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://bd.ews.xxxxx.com">+
*+<getHeaderReturn href="#id0"/>+*
*+<getHeaderExtensions href="#id1"/>+*
+</ns1:getHeaderResponse>+
+<*multiRef id="id0"* soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:DealHeader" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:ews-structs">+
+<agent_deal_fl xsi:type="xsd:string">N</agent_deal_fl>+
+<attach_fl xsi:type="xsd:string">N</attach_fl>+
+<bd_id xsi:type="xsd:string">5449DDF</bd_id>+
*+<bd_version_nr xsi:type="xsd:int">1</bd_version_nr>+*
+<beg_dt xsi:type="xsd:string">16-Jul-2010 00:00</beg_dt>+
+<end_dt xsi:type="xsd:string">30-Sep-2011 00:00</end_dt>+
++
+<*multiRef id="id1"* soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:DealHeader" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:ews-structs">+
*+<bd_version_nr xsi:type="xsd:int">1</bd_version_nr>+*
+<extra elements />+
++
+</multiRef>+
+</soapenv:Body>+
Anuj Dwivedi wrote:
As far as I know, you can convert the multiref xml to normal structure using XSLT or similar conversion technologies but I have never tried this. It's an interesting use case and I would at least try it once at my end.I will try it when I get time. Are you saying that you are also going to try it yourself?
Edited by: jjhowey on Oct 7, 2010 10:25 AM
Edited by: jjhowey on Oct 7, 2010 10:28 AM
Edited by: jjhowey on Oct 7, 2010 10:29 AM

OSB harverting to OER

Hi,
I have made changes in harvesting.xml file found on machine where OSB is installed and i have encryted passwords also as it was mention in document.
also i have imported 11.1.1.5.0-OER-Harvester-Solution-Pack to OER console.But,while executing **./osb11g-harvest.sh**
i get error mention below
[main] ERROR com.oracle.oer.sync.plugin.writer.oer.ALERConnectionCache - Failed to get authToken due to: [{http://schemas.xmlsoap.org/soap/envelope/}Server.userException] [Error [1,000]: Error authenticating user.
] [Error [1,000]: Error authenticating user.
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: Error [1,000]: Error authenticating user.
faultActor:
faultNode:
faultDetail:
     {}com.flashline.framework.exception.OpenAPIException:<messageArguments soapenc:arrayType="xsd:string[0]" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="soapenc:Array"/><serverErrorCode xsi:type="xsd:int">1000</serverErrorCode><serverMessage xsi:type="xsd:string">Error [1,000]: Error authenticating user.</serverMessage><serverStackTrace xsi:type="xsd:string"/><severity xsi:type="xsd:string">SEVERE</severity>
     {http://xml.apache.org/axis/}hostname:usstuorf13
Error [1,000]: Error authenticating user.
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     at java.lang.Class.newInstance0(Class.java:355)
     at java.lang.Class.newInstance(Class.java:308)
     at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:104)
     at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:90)
     at com.flashline.registry.openapi.base.OpenAPIException.getDeserializer(OpenAPIException.java:258)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:154)
     at org.apache.axis.encoding.ser.BaseDeserializerFactory.getDeserializerAs(BaseDeserializerFactory.java:84)
     at org.apache.axis.encoding.DeserializationContext.getDeserializer(DeserializationContext.java:464)
     at org.apache.axis.encoding.DeserializationContext.getDeserializerForType(DeserializationContext.java:547)
     at org.apache.axis.message.SOAPFaultDetailsBuilder.onStartChild(SOAPFaultDetailsBuilder.java:157)
     at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
     at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501)
     at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:400)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2756)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
     at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
     at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
     at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
     at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
     at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:133)
     at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:173)
     at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
     at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
     at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
     at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
     at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:796)
     at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
     at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
     at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
     at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
     at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
     at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
     at org.apache.axis.client.Call.invoke(Call.java:2748)
     at org.apache.axis.client.Call.invoke(Call.java:2424)
     at org.apache.axis.client.Call.invoke(Call.java:2347)
     at org.apache.axis.client.Call.invoke(Call.java:1804)
     at com.flashline.registry.openapi.service.v300.FlashlineRegistryTrSoapBindingStub.authTokenCreateWithLicense(FlashlineRegistryTrSoapBindingStub.java:7450)
Thanks in advance
     at com.oracle.oer.sync.plugin.writer.oer.ALERConnectionCache.getAuthToken(ALERConnectionCache.java:136)
     at com.oracle.oer.sync.plugin.writer.oer.ALERAssetQueries.getToken(ALERAssetQueries.java:82)
     at com.oracle.oer.sync.plugin.writer.oer.ALERAssetQueries.assetTypeQueryByUUID(ALERAssetQueries.java:159)
     at com.oracle.oer.sync.framework.MetadataManager.putAssetType(MetadataManager.java:206)
     at com.oracle.oer.sync.framework.impl.DefaultPluginManager.processIntrospector(DefaultPluginManager.java:104)
     at com.oracle.oer.sync.framework.impl.DefaultPluginManager.<init>(DefaultPluginManager.java:73)
     at com.oracle.oer.sync.framework.MetadataManager.init(MetadataManager.java:308)
     at com.oracle.oer.sync.framework.Introspector.<init>(Introspector.java:201)
     at com.oracle.oer.sync.framework.Introspector.main(Introspector.java:428)
3 [main] ERROR com.oracle.oer.sync.plugin.writer.oer.ALERConnectionCache - Failed to get authToken due to: [{http://schemas.xmlsoap.org/soap/envelope/}Server.userException] [Error [1,000]: Error authenticating user.

Were you ever able to get this issue resolved? We are having the same issue with OER 11.1.1.4.
Cannot connect using the harvester or the api. (Everything else works fine.)

Validate in OSB

I want to validate my XML response in a proxy service before sending this back to the client. I want to know how can I do this and what should be the values in settings?
My XML (SOAP body for response) look like this:
<fcs:responses      xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:g="http://dps.state.tx.us/niem/txgang/extension/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:fbi="http://niem.gov/niem/fbi/xsd/2.0" xmlns:usps="http://niem.gov/niem/usps_states/xsd/2.0" xmlns:str="http://exslt.org/strings" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:fcs="http://ws.workflow.fc.services.dps.texas.gov/FCServices" xmlns:dpsg="http://ws.workflow.fc.services.dps.texas.gov/DPSGlobal" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:tol="http://dl.txdps.com/axis/services/TxOnline" xmlns:s="http://niem.gov/niem/structures/2.0">
     <fcs:response>
     <fcs:data>
     <nc:DocumentIdentification>
     <nc:IdentificationID>341162234</nc:IdentificationID>
     <nc:IdentificationCategoryDescriptionText>TXDPS0000</nc:IdentificationCategoryDescriptionText>
     </nc:DocumentIdentification>
     <dpsg:Person      s:id="ID_Person_733">
     <nc:PersonName>
     <nc:PersonSurName>Name1</nc:PersonSurName>
     <nc:PersonGivenName>Ame12</nc:PersonGivenName>
     <nc:PersonMiddleName>Test</nc:PersonMiddleName>
     <nc:PersonFullName>Test,name </nc:PersonFullName>
     </nc:PersonName>
     <nc:PersonBirthDate>
     <nc:Date>1974-11-09</nc:Date>
     </nc:PersonBirthDate>
     <nc:PersonSSNIdentification>
     <nc:IdentificationID>456353614</nc:IdentificationID>
     </nc:PersonSSNIdentification>
     </dpsg:Person>
     </fcs:data>
     <fcs:dataSrc>
     <fcs:dataSrcCd>TXGANG</fcs:dataSrcCd>
     </fcs:dataSrc>
     </fcs:response>
     </fcs:responses>
And I want to validate against one element (named responses) in my xsd. What should be the values for validate in OSB:
XPath : .
In Variable : body
Against Resource : I should select the xsdl element (named responses).
My validation is getting failed all the time. I am wondering that my validation is failing because I am not getting the correct content from the soap body.
I will really appreciate quick response.

XPath should be ./* (dot-slaash-*)
Regards,
Anuj

Force MTOM/XOP response on OSB

hello,
How can I force a MOTOM Response although it is not neccessary because I have no binary data in the response.
The reason is follow. I have a foreign test client that sends the request with MTOM enabled and expected that the response is also using MTOM (I think this is a little bit stupid). The client is using AXIS.
In the request the client sends binary data using MTOM but in my response no binary data is available and so OSB won't enable the Mtom Feature for the response. The result is that the client don't accept my response...
Is there a workaround to force that MTOM is being enabled?

Sorry for the delay response. This is a known issue that MTOM is enabled only the binary data is at the top level in WLS 10.1.
But it has already support complex type MTOM encoded in WLS 10.3. Please download at [url http://commerce.bea.com/products/weblogicplatform/weblogic_prod_fam.jsp]here
Edited by jliao at 11/14/2007 5:46 AM

Test OSB fault with SoapUI return soapenv:Header and soapenv:Body empty

Hello,
We have two different projects (pass-thru): PS --> BS, the characteristics of both proxies are:
-     The call to Business is with “Route to” stage
-     There are RouteNode Error Handler that finally do “Reply” With Failure
When we test the project thru SoapUi with the case of use that produces the response: HTTP-500 and Soap Fault, the response is different:
-     Project 1:
+<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">+
+<soapenv:Header/>+
+<soapenv:Body xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">+
+<soapenv:Fault>+
+<faultcode>soapenv:Server.userException</faultcode>+
+<faultstring>java.rmi.RemoteException: 02 ERROR NO EXISTE ABONADO</faultstring>+
+<detail>+
+<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">icmaplicv23.madrid.org</ns1:hostname>+
+</detail>+
+</soapenv:Fault>+
+</soapenv:Body>+
+</soapenv:Envelope>+
-     Project 2:
+<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">+
+<soapenv:Header/>+
+<soapenv:Body/>+
+</soapenv:Envelope>+
I don´t understand why the behavior is different.
We read many OTN-Post, even had to upgrade OSB to version 11.1.1.6 that solve patch 8186945.
Please could you help me understand why the soapenv is empty in the project2?
Thanks in advance,
Victor

I found the answer.
http://docs.oracle.com/cd/E13159_01/osb/docs10gr3/consolehelp/proxyactions.html#wp1306518
I change the "Selected Service Type" on BS to "XML". And now is working!
Regards,
Martín
Edited by: 876766 on Jan 12, 2013 9:09 AM

Axis 2 Vs OSB

Similar Messages

Maybe you are looking for