ODSI to Invoke an A sync Web service

We have a 2-Tier application based on Oracle 11g db and PowerBuilder 10.
Does the follwoing practice can take place? :
1.call an ODSI Program (Wraped as a service) from Power Builder
2.ODSI will collect the data from the db and send it to a SOAP end point for further processing.
Also , would it be best practice to creat my SOA landscape usign this tool rather then developing
each outbound service using Jdeveloper for example on the application side.
Appriciate your insights.

I'm not sure I understand the post. The subject says "ODSI to (can?) invoke an A sync (async?) web service" (it cannot), but then goes on to ask something different.
1.call an ODSI Program (Wraped as a service) from Power Builder If PowerBuilder supports calling webservices, then yes, you can call ODSI from Powerbuilder.
Also , would it be best practice to creat my SOA landscape usign this tool
2.ODSI will collect the data from the db and send it to a SOAP end point for further processing.The strength of ODSI is that it can part or perhaps even all of the "further processing".
would it be best practice to creat my SOA landscape usign this tool ratherThat would be a good practice.

Similar Messages

Erorr calling long running sync web service

Hello
I have definied simple async process:
assign (from process input to ws invoke input)
sync ws invoke
assign (from ws invoke output to process output)
Sync Web Service is long running (few minutes). In order to avoid timeout I have accordingly set sync-max-wait-time property.
I have observed that after starting process instance I can't see it in BPEL Console (however I know it is working). Furthermore when invoke activity ends (so instance state must be saved in database) I can see following error on system console:
<BaseCubeSessionBean::logError> Error while invoking bean "delivery": Cannot ins
ert audit trail.
The process domain was unable to insert the current log entries for the instance
"2314" to the audit trail table. The exception reported is: RollbackException:
The transaction has been marked for rollback (timed out)
Please check that the machine hosting the datasource is physically connected to
the network. Otherwise, check that the datasource connection parameters (user/p
assword) is currently valid.
sql statement: INSERT INTO audit_trail ( cikey, domain_ref, count_id, log ) VALU
ES ( ?, ?, ?, ? )
<2005-01-06 13:14:10,268> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseSc
heduledWorker::process> Failed to handle dispatch message invoke instance messag
e 0c92305db480f36d:149b290:10147dc1b2e:-7fd6 ... exception Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.
engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: Transac
tion was rolled back: timed out; nested exception is: java.rmi.RemoteException:
No Exception - originate from:java.lang.Exception: No Exception - originate from
:; nested exception is:
java.lang.Exception: No Exception - originate from:
Best Regards

Hi,
There are 2 ways to work around the error that you are seeing.
Option #1: increase the JTA timeout of the underlying application server.
Option #2: in the bpel.xml of your process, add a "nonBlockingInvoke" property to the partnerLink representing the interaction with the long running service.
Option #2 should also address the fact that the instance is not visible in the bpel console.
Edwin

Invoking a scenario using web service

Hi Experts,
Could anyone pls suggest how to pass variables from SOAP to ODI 11g(11.1.1.6.3)
Here we are using wsdl utility to invoke a scenario using web service and trying to pass a variable like the below
The scenario is triggered successfully without passing a parameter.
But when i try to pass a variable like the below,am getting error
Variables name='PROJECT_CODE'
Variables value='JI-2015'
In ODI 11g, i have generated a scenario with a variable PROJECT_CODE as a declare variable and tried triggering from both the environments
From ODI 11g:
When I try to trigger the scenario from wsdl, in that variable step(in operator), I got error as ODI-17546: Specified variable not found in the Repository
But in the work repository SNP_VAR table I could still see the variable name under VAR_NAME column.
From ODI 10g:
When i try to do the same from odi 10g, the scenario execution is success.
But the variable had taken only NULL value instead of taking the value which i passed from wsdl.
Could you pls advise where am going wrong

variable should be passed in the soap message by adding variables elements. Refer to Note ID [1499852.1]
<Variables>
<Name>Project.Variable1</Name>
<Value>Variable1Value</Value>
</Variables>
<Variables>
<Name>Project.Variable2</Name>
<Value>Variable2Value</Value>
</Variables>
<Variables>
<Name>Project.Variable3</Name>
<Value>Variable3Value</Value>
</Variables>

Sync Web Service - BPM with 2 sync proxy calls error.

Hi.
Have a sync web service going into a BPM.
In the BPM there ar 2 sync calls towards a system making a credit check.
The answer is responded to the web service.
In our QA system the solution works perfect.
I transported the solution to production and when I test the web service call towards I get the following error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">PL_TIMEOUT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Timeout condition of pipeline reached</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Does anybody have an idea why I get the error.
When I check my config everything looks the same.
Looks like we never send the first sync call to the proxy when I check in SXMB_MONI and the BPM gets terminated.
We have just migrated the solution from XI 3.0 to PI 7.11.
BR
Kalle

Hi.
How will that help if we do not send the message.
When I check the graphics in SXMB_MONI the error occours befor we send the first message with proxy.
Also extend ASYNC timeout?
We are using sync communication.
BR
Kalle

"Cipher not initialized" when trying to invoke CRM On Demand web service

Hi,
I'm try to invoke CRM On Demand web service for which there is a pre-req to get a session ID by making an https request. I've the below java embedded code which does that. It works fine if I run the below code in my desktop as a java program, but when I deploy it on SOA 11g I get "Caused by: java.lang.IllegalStateException: Cipher not initialized" error (find below the stack trace). Please let me know what's going wrong here?
String sessionString = "FAIL";
String wsLocation =
"https://secure-********.crmondemand.com/Services/Integration";
String headerName;
try {
// create an HTTPS connection to the OnDemand webservices
java.net.URL wsURL =
new java.net.URL(wsLocation + "?command=login");
java.net.HttpURLConnection wsConnection =
(java.net.HttpURLConnection)wsURL.openConnection();
// disable caching
wsConnection.setUseCaches(false);
// set some http headers to indicate the username and password we are using to logon
wsConnection.setRequestProperty("UserName",
wsConnection.setRequestProperty("Password", "***********");
wsConnection.setRequestMethod("GET");
// see if we got a successful response
if (wsConnection.getResponseCode() ==
java.net.HttpURLConnection.HTTP_OK) {
// get the session id from the cookie setting
for (int i = 0; ; i++) {
headerName = wsConnection.getHeaderFieldKey(i);
if (headerName != null &&
headerName.equals("Set-Cookie")) {
// found the Set-Cookie header (code assumes only one cookie is being set)
sessionString = wsConnection.getHeaderField(i);
if (sessionString != null ||
sessionString.startsWith("JSESSIONID")) {
break;
String formattedID =
sessionString.substring(sessionString.indexOf("=") + 1,
sessionString.indexOf(";"));
setVariableData("SessionID", formattedID);
//System.out.println("Session ID: " + sessionString);
} catch (Exception e) {
e.printStackTrace();
setVariableData("SessionID", e.getMessage());
System.out.println("Logon Exception generated :: " + e);
throw new RuntimeException(e);
Caused by: java.lang.IllegalStateException: Cipher not initialized
at javax.crypto.Cipher.c(DashoA13*..)
at javax.crypto.Cipher.update(DashoA13*..)
at com.certicom.tls.provider.Cipher.update(Unknown Source)
at com.certicom.tls.record.MessageEncryptor.compressEncryptSend(Unknown Source)
at com.certicom.tls.record.MessageEncryptor.compressEncryptSend(Unknown Source)
at com.certicom.tls.record.MessageFragmentor.write(Unknown Source)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:158)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:363)
at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
at weblogic.net.http.HttpURLConnection.getResponseCode(HttpURLConnection.java:952)
at orabpel.productquerybpelprocess.ExecLetBxExe0.execute(ExecLetBxExe0.java:93)
Thanks!

Same question...did you ever got this resolved...for me, even the simple java program, when run on JDev 11g is ALSO not working. I am getting this.
Using JDev 10g on the same machine (or for that matter SOA 10g) works perfectly.
Have posted this thread too - Getting SSLHandshakeException when trying to login to OCOD using Jdev 11g
Thanks,
Amit

Problem in invoking a secure weblogic web service from javaws client

Hi all,
the situation is this: there is a secure web service (Wssp1.2-2007-Wss1.1-X509-Basic256.xml policy) which is accessed by a stand-alone remote web service client (swing-enabled) which is initiated via java web start. You'll probably wondering why this is a special case. Let me elaborate...
The first step was to develop the service and the client. This wasn't much of a trouble, since the documentation was very good apart from creating a ClientBSTCredentialProvider object at the client side. The documentation should explicitly state that the sixth argument, that of the server certificate, is required! In any case, the first step was a success and the invocation was encrypted and signed at the message level.
The second step was to create a stand-alone remote client, without any local weblogic installation. That was a bit of a problem, since wlfullclient.jar or wseeclient.jar or weblogic.jar were not enough. I should note that the client was created via netbeans 7.0 and not with the help of weblogic clientgen. So, I had to make a verbose run from netbeans, in order to enumerate the jars which are accessed and gather them into the same directory. That was OK too. The standalone client works just fine.
The third step is to simply (not so simply...) make a java web start version of the client. Since the previous step was a success (having all necessary jars in the same directory) this one should not be a problem. Well... that turned out to be a huge issue. What I get back as the error message (shown in the java web start console) is this:
java.lang.InternalError: error initializing kernel caused by: java.lang.AssertionError: Duplicate initialization of WorkManager
     at weblogic.work.WorkManagerFactory.set(WorkManagerFactory.java:107)
     at weblogic.work.ExecuteQueueFactory.initialize(ExecuteQueueFactory.java:23)
     at weblogic.kernel.Kernel.initialize(Kernel.java:103)
     at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:64)
     at weblogic.rjvm.wls.WLSRJVMEnvironment.ensureInitialized(WLSRJVMEnvironment.java:50)
     at weblogic.protocol.ProtocolManager$DefaultAdminProtocolMaker.<clinit>(ProtocolManager.java:53)
     at weblogic.protocol.ProtocolManager.getDefaultAdminProtocol(ProtocolManager.java:218)
     at weblogic.protocol.ProtocolHandlerAdmin.<clinit>(ProtocolHandlerAdmin.java:23)
     at weblogic.rjvm.wls.WLSRJVMEnvironment.registerRJVMProtocols(WLSRJVMEnvironment.java:120)
     at weblogic.rjvm.RJVMManager.ensureInitialized(RJVMManager.java:87)
     at weblogic.rjvm.RJVMManager.<clinit>(RJVMManager.java:46)
     at weblogic.rjvm.LocalRJVM.<init>(LocalRJVM.java:97)
     at weblogic.rjvm.LocalRJVM.<init>(LocalRJVM.java:28)
     at weblogic.rjvm.LocalRJVM$LocalRJVMMaker.<clinit>(LocalRJVM.java:31)
     at weblogic.rjvm.LocalRJVM.getLocalRJVM(LocalRJVM.java:72)
     at weblogic.xml.crypto.utils.DOMUtils.generateId(DOMUtils.java:403)
     at weblogic.xml.crypto.utils.DOMUtils.generateId(DOMUtils.java:395)
     at weblogic.xml.crypto.utils.DOMUtils.assignId(DOMUtils.java:374)
     at weblogic.xml.crypto.wss.SecurityBuilderImpl.assignUri(SecurityBuilderImpl.java:148)
     at weblogic.wsee.security.policy.SigningReferencesFactory.getSigningReferences(SigningReferencesFactory.java:100)
     at weblogic.wsee.security.wss.policy.wssp.SigningPolicyBlueprintImpl.addSignatureNodeListToReference(SigningPolicyBlueprintImpl.java:446)
     at weblogic.wsee.security.wss.policy.wssp.SigningPolicyBlueprintImpl.addSignatureNodeListToReference(SigningPolicyBlueprintImpl.java:335)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.resolveSignatureList(SecurityMessageArchitect.java:574)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.resolveSignatureList(SecurityMessageArchitect.java:428)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.constructMessage(SecurityMessageArchitect.java:304)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.buildWssMessage(SecurityMessageArchitect.java:138)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.buildWssMessage(SecurityMessageArchitect.java:121)
     at weblogic.wsee.security.wss.SecurityPolicyArchitect.processOutbound(SecurityPolicyArchitect.java:225)
     at weblogic.wsee.security.wss.SecurityPolicyArchitect.processMessagePolicy(SecurityPolicyArchitect.java:123)
     at weblogic.wsee.security.wss.SecurityPolicyConductor.processRequestOutbound(SecurityPolicyConductor.java:119)
     at weblogic.wsee.security.wss.SecurityPolicyConductor.processRequestOutbound(SecurityPolicyConductor.java:91)
     at weblogic.wsee.security.wssp.handlers.WssClientHandler.processOutbound(WssClientHandler.java:117)
     at weblogic.wsee.security.wssp.handlers.WssClientHandler.processRequest(WssClientHandler.java:69)
     at weblogic.wsee.security.wssp.handlers.WssHandler.handleRequest(WssHandler.java:112)
     at weblogic.wsee.jaxws.framework.jaxrpc.TubeFactory$JAXRPCTube.processRequest(TubeFactory.java:222)
     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:866)
     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
     at com.sun.xml.ws.client.Stub.process(Stub.java:272)
     at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:153)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:115)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
     at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
     at $Proxy29.fetchCSD(Unknown Source)
     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 weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
     at $Proxy30.fetchCSD(Unknown Source)
     at exchangecsdclient.CSDExchangeClientImpl.fetchCSD(CSDExchangeClientImpl.java:151)
     at pdfutil.PDFUtilApp.initialize(PDFUtilApp.java:55)
     at org.jdesktop.application.Application$1.run(Application.java:170)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
     at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
     at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:66)
     at weblogic.rjvm.wls.WLSRJVMEnvironment.ensureInitialized(WLSRJVMEnvironment.java:50)
     at weblogic.protocol.ProtocolManager$DefaultAdminProtocolMaker.<clinit>(ProtocolManager.java:53)
     at weblogic.protocol.ProtocolManager.getDefaultAdminProtocol(ProtocolManager.java:218)
     at weblogic.protocol.ProtocolHandlerAdmin.<clinit>(ProtocolHandlerAdmin.java:23)
     at weblogic.rjvm.wls.WLSRJVMEnvironment.registerRJVMProtocols(WLSRJVMEnvironment.java:120)
     at weblogic.rjvm.RJVMManager.ensureInitialized(RJVMManager.java:87)
     at weblogic.rjvm.RJVMManager.<clinit>(RJVMManager.java:46)
     at weblogic.rjvm.LocalRJVM.<init>(LocalRJVM.java:97)
     at weblogic.rjvm.LocalRJVM.<init>(LocalRJVM.java:28)
     at weblogic.rjvm.LocalRJVM$LocalRJVMMaker.<clinit>(LocalRJVM.java:31)
     at weblogic.rjvm.LocalRJVM.getLocalRJVM(LocalRJVM.java:72)
     at weblogic.xml.crypto.utils.DOMUtils.generateId(DOMUtils.java:403)
     at weblogic.xml.crypto.utils.DOMUtils.generateId(DOMUtils.java:395)
     at weblogic.xml.crypto.utils.DOMUtils.assignId(DOMUtils.java:374)
     at weblogic.xml.crypto.wss.SecurityBuilderImpl.assignUri(SecurityBuilderImpl.java:148)
     at weblogic.wsee.security.policy.SigningReferencesFactory.getSigningReferences(SigningReferencesFactory.java:100)
     at weblogic.wsee.security.wss.policy.wssp.SigningPolicyBlueprintImpl.addSignatureNodeListToReference(SigningPolicyBlueprintImpl.java:446)
     at weblogic.wsee.security.wss.policy.wssp.SigningPolicyBlueprintImpl.addSignatureNodeListToReference(SigningPolicyBlueprintImpl.java:335)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.resolveSignatureList(SecurityMessageArchitect.java:574)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.resolveSignatureList(SecurityMessageArchitect.java:428)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.constructMessage(SecurityMessageArchitect.java:304)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.buildWssMessage(SecurityMessageArchitect.java:138)
     at weblogic.wsee.security.wss.plan.SecurityMessageArchitect.buildWssMessage(SecurityMessageArchitect.java:121)
     at weblogic.wsee.security.wss.SecurityPolicyArchitect.processOutbound(SecurityPolicyArchitect.java:225)
     at weblogic.wsee.security.wss.SecurityPolicyArchitect.processMessagePolicy(SecurityPolicyArchitect.java:123)
     at weblogic.wsee.security.wss.SecurityPolicyConductor.processRequestOutbound(SecurityPolicyConductor.java:119)
     at weblogic.wsee.security.wss.SecurityPolicyConductor.processRequestOutbound(SecurityPolicyConductor.java:91)
     at weblogic.wsee.security.wssp.handlers.WssClientHandler.processOutbound(WssClientHandler.java:117)
     at weblogic.wsee.security.wssp.handlers.WssClientHandler.processRequest(WssClientHandler.java:69)
     at weblogic.wsee.security.wssp.handlers.WssHandler.handleRequest(WssHandler.java:112)
     at weblogic.wsee.jaxws.framework.jaxrpc.TubeFactory$JAXRPCTube.processRequest(TubeFactory.java:222)
     at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:866)
     at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:815)
     at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:778)
     at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:680)
     at com.sun.xml.ws.client.Stub.process(Stub.java:272)
     at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:153)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:115)
     at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
     at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
     at $Proxy29.fetchCSD(Unknown Source)
     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 weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
     at $Proxy30.fetchCSD(Unknown Source)
     at exchangecsdclient.CSDExchangeClientImpl.fetchCSD(CSDExchangeClientImpl.java:151)
     at pdfutil.PDFUtilApp.initialize(PDFUtilApp.java:55)
     at org.jdesktop.application.Application$1.run(Application.java:170)
     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
     at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
The two invocations (one using java and the other using javaws) should obviously have not differences at all since all resources (jars) are the same.
I have tried all client jar combinations (with wlfullclient.jar, wseeclient.jar, weblogic.jar) and the result is the same. One additional piece of information is that when removing all security parameters (message level encryption and signing) from the web service the java web start client works just fine!!!
This is not an issue of additional jars that somehow mess with weblogic jars, since the same error occurs even in the basic hello world web service.
I wonder if someone has faced the same problem. I would really really appreciate any help. Thank you in advance and keep up the good work.
Cheers,
Paul.
Edited by: PaulP on Jan 11, 2012 5:31 AM

Hi Kal,
since we're currently evaluating the software and haven't acquired a license, we cannot contact support.
I only need to know if this is a solved bug or not. Does it have to do with the classloading process (I cannot think of anything else)?
Thank you again very very much!
Cheers,
Paul.

Invoking Siebel CRM OnDemand Web Service via BPEL

I'm trying to invoke a Siebel CRM OnDemand Web Service via BPEL. Basically, the Siebel guide says to post to a url with user/pwd to get a session ID returned from a cookie. I did that using embedded java and have the session ID as a variable in my BPEL process. My problem is with now calling the Web Service to perform the action. I have a WSDL from Siebel, but the guide says to use an HTTP post with the session ID in the url and the XML in the body. How do I do that? Shouldn't the WSDL handle that when I create the Partner Link? Do I need to use more embedded Java for this or can I set up a Partner Link? I created a Partner Link and it shows the methods I want to use, but I get the following error when I try to call it because I don't know where to add the session ID:
<ErrorCode xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">SBL-ODU-01006</ErrorCode>
<ErrorMessage xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">Internal Error: Session is not available. Aborting.</ErrorMessage>
Any help would be GREATLY appreciated. Please let me know if you need more information.
THANKS!

The Siebel OnDemand web services can accept the siebel session token in the URL. Append ';jessionid={%sessionIdFromCookie%}' to the end point. Obviously this has to be done dynamically. Refer to the article called 'Making BPEL Processes Dynamic' (http://www.oracle.com/technology/pub/articles/bpel_cookbook/carey.html) pay particular attention to the 'Eliminating address dependency at run time' section.
Peter

Async system - XI BPM Sync - Web service - SOAP response

Dear Experts:
I have the following scenario:
Async Proxy to XI to web service. I use BPM to make this a sync call to the web service. It works fine!
I have a XSLT mapping for the response message from the web service. I use XSLT because the structure of the positive and fault responses are different. Anyway, I could get the positive response post ok back in the XI system.
But the fault response does not get mapped and I get a APPLICATION_ERROR of category UNKNOWN in the SXMB_MONI. I also configured exception handling in the BPM. But it does not catch this error.
Can anyone suggest how to handle the fault response from the web service?
Thank you.

I just had the same problem and solved it like this: I modified the WSDL slightly by removing the prefix from the reference to the element of the response message, as well as the "targetNamespace" in the xsd:schema segment of the WSDL. Like this, SAP is able to parse the response.
Philippe

WebServiceException When invoking secured ADF-BC web services on WebSphere

We built web services using ADF 11.1.1.7 RC1, and deployed to WebSphere ND 7.0.0.23
The web services are secured using OWSM policy:
@SecurityPolicy( { "oracle/wss11_saml_or_username_token_with_message_protection_service_policy" })
And we have a client java program which invokes the web services as follows:
MTOMFeature mtom = new MTOMFeature();
SecurityPolicyFeature sec_policy = new SecurityPolicyFeature("oracle/wss11_saml_token_with_message_protection_client_policy");
if (lCMAMService == null) {
generateFCMWebserviceUrl();
URL url = new URL(fcmUrl);
LCMAMService_Service lCMAMService_Service = null;
try {
lCMAMService_Service = new LCMAMService_Service(url);
} catch (WebServiceException wse) {
generateFCMWebserviceUrl(true);
URL physicalURL = new URL(fcmUrl);
lCMAMService_Service = new LCMAMService_Service(physicalURL);
lCMAMService = lCMAMService_Service.getLCMAMServiceSoapHttpPort(mtom, sec_policy);
Everything works fine in WebLogic. However, when running on WebSphere ND 7.0.0.23, the following exception were thrown:
javax.xml.ws.WebServiceException: Invalid or unsupported WebServiceFeature feature http://www.w3.org/ns/ws-policy
     at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:173)
     at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:70)
     at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:118)
     at org.apache.axis2.jaxws.feature.ClientFramework.addFeature(ClientFramework.java:56)
     at org.apache.axis2.jaxws.binding.BindingImpl.setFeatures(BindingImpl.java:138)
     at org.apache.axis2.jaxws.BindingProvider.initialize(BindingProvider.java:167)
     at org.apache.axis2.jaxws.BindingProvider.<init>(BindingProvider.java:73)
     at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.<init>(JAXWSProxyHandler.java:123)
     at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.<init>(JAXWSProxyHandler.java:114)
     at org.apache.axis2.jaxws.spi.ServiceDelegate.getPort(ServiceDelegate.java:615)
     at javax.xml.ws.Service.getPort(Service.java:133)
     at oracle.apps.epm.fcc.lcm.proxy.LCMAMService_Service.getLCMAMServiceSoapHttpPort(LCMAMService_Service.java:59)
     at oracle.apps.epm.fcc.lcm.common.FCMExportImportHandler.instantiateFCMService(FCMExportImportHandler.java:703)
It seems that in WebSphere, the security policy are not supported. Any idea what needs to be changed for the client code to work in WebSphere?
Thanks.

Hi,
as you are from Oracle, can you reach out to internal forums and mailing lists? JDeveloper 11.1.1.7 RC1 is not available outside of Oracle and therefore should not have questions posted on this public forum.
Frank

Issue of invoke wf_engine function from web service client.

hi,
I want to update work flow item attribute from web service client through soa gateway. but got the below exception:
Error Description Error occured while service was processing.
Error Details oracle.apps.fnd.soa.util.SOAException: ServiceProcessingError: Exception returned from JCA Service Runtime. file:/pim/oracle/DEV/inst/apps/DEV_pimenv/soa/PLSQL/1318/SETITEMATTRTEXT.wsdl [ SETITEMATTRTEXT_ptt::SETITEMATTRTEXT(InputParameters) ] - WSIF JCA Execute of operation 'SETITEMATTRTEXT' failed due to: Error while processing an API interaction execution. An error occurred while processing the interaction for invoking the WF_ENGINE.SETITEMATTRTEXT API. Cause: oracle.tip.adapter.apps.AppsContextValidationException: Cannot set Context ; nested exception is: ORABPEL-11812 Error while processing an API interaction execution. An error occurred while processing the interaction for invoking the WF_ENGINE.SETITEMATTRTEXT API. Cause: oracle.tip.adapter.apps.AppsContextValidationException: Cannot set Context Check to ensure that the XML containing parameter data matches the parameter definitions in the XSD. Contact oracle support if error is not fixable. at oracle.apps.fnd.soa.provider.services.jca.JCAHandler.invoke(JCAHandler.java:173) at oracle.apps.fnd.soa.provider.services.jca.JCAHandler.handleRequest(JCAHandler.java:120)
it indicate " cannot set context". but there is no method of wf_engine api to set it.
Thanks,
Rock

Hi, Buddy,
Did you fix your issue?
Now, I have the same issue, EBS version is 12.1.3. Using Soapui invoking PL/SQL, then go back to SOA monitor to check the error message.
Could you please give me some advises?
Thanks,
Jackie

Invoke sql 2005 native web services

Dear all,
I am trying to invoke from sap ecc 6.0 a native web services written in sql 2005.
For instance the web service path is something like http://10.1.0.197:8080/EmployeeXml?wsdl .
The web method is GetEmployeesXml
If I try to consume via custom .net application, it works but when I try to do the same in sap
following this guide
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/802edea6-274e-2e10-fd95-e5e1a8bc0892?QuickLink=index&overridelayout=true
I get the error http not supported.
The differnce between an asp.net web services (where everythings works) and this one is regarding the autentication.
For the first one it is possible to specify anonymous login for second it is necessary to specify the username and password.
I kindly ask you to give any help to solve this issue, or is there a manual for sm59?
Thank you very much

Try with the following:
<xsd:complexType name="SqlResultStream">
   <xsd:sequence>
      <xsd:element name="SqlRowSet" type="sqlsoaptypes:SqlRowSet" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="SqlXml" type="sqlsoaptypes:SqlXml" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="SqlMessage" type="sqlmessage:SqlMessage" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="SqlRowCount" type="sqlrowcount:SqlRowCount" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="SqlResultCode" type="sqlsoaptypes:SqlResultCode" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="SqlTransaction" type="sqltransaction:SqlTransaction" minOccurs="0" maxOccurs="unbounded"/>
   </xsd:sequence>
</xsd:complexType>
You also have to know that this is not a perfect equivalent, as no tag can replace the xsd:choice. The xsd:choice means that only one of the elements can occur, while in xsd:sequence any of the elements can occur. But you should be able to achieve the same with a properly built mapping: create only one of the fields, and leave the rest empty - this is possible thanks to minOccurs="0".
Hope this helps,
Greg

Invoking BAPI_MATERIAL_SAVEDATA as a web service from CAF

I am new to BAPI world. Currently, we are building a composite application - a part of the application interacts with SAP R3 for creating materials and then getting a list of all created materials. We are using the following BAPIs: BAPI_MATERIAL_SAVEDATA, BAPI_MATERIAL_GETLIST, BAPI_MATERIAL_GETDETAIL. All these BAPIs are exposed as web services. I have created an external service using wsdl file that corresponds to BAPI_MATERIAL_SAVEDATA. I would like to create a new material by passing minimum possible parameters. I am setting the values in HEADDATA and MATERIALDESCRIPTION only. I am giving Y to basic_view and N to all other views in HEADDATA. The call succeeds apparently but when I try to retrieve it using BAPI_MATERIAL_GETLIST/GETDETAIL it fails to retrieve. My questions:
1. What is the best way to create a new material (basic view) by passing minimum parameters?
2. How to verify if the material is successfully created?
3. How does CLIENTDATA and CLIENTDATAX differ? There are similar 'X' appends in other places as well. Can anyone please provide any pointer/link about some more basic information on the following BAPIs: BAPI_MATERIAL_SAVEDATA, BAPI_MATERIAL_GETDETAIL, BAPI_MATERIAL_GETLIST.
Thanks.

Hi,
   3. To get more information about a BAPI, you can look at the function module documentation. Login to the R/3 system, start transaction SE37 and type in the name of the BAPI and select "Display". Once you see the source code, you'll see a button called "Function module document". Clicking on that will open up the help document for that BAPI.
   For eg., quoting from the docs for BAPI_MATERIAL_SAVEDATA, CLIENTDATA structure is used to transfer the general basic data on a material. CLIENTDATA X structure determines which fields in the assigned user data structure (CLIENTDATA) contain change-relevant information.
   2. When the BAPI_MATERIAL_SAVEDATA is executed, it should ideally contain the material number in the structure HEADDATA. Check if you are getting that. If you have it, then it should've been created. You can double check by starting transaction SE11 and display table MARA. Type in the material number that you received.
1. All the parameters except HEADDATA is optional for the BAPI_MATERIAL_SAVEDATA. So you can just choose to pass some of the fields of this structure and that should do it.
Regards,
Satyajit.

Invoking wli process as web service

Hello,
I've developed a WLI process which I want to access as web service.
I'm using conversation as explained in
"How Do I: Tell Developers of Non-WebLogic Workshop Clients How to Participate in Conversations?"
http://e-docs.bea.com/workshop/docs81/doc/en/core/index.html
But I don't know how to access this web service and to set the conversationID in the SOAP header.
Thanks a lot.
Victor.

I dont think what is the issue that you have here. Now there are multiple ways to expose a WLI process as a webservice.
1. The WLI workshop allows you to direcly expose a .jpd file (process file) as a WSDL.
2. In case you want you Web service to have multiple methods for different processes, create a process control from the .jpd file and then create a Weblogic Webservice using these controls.
Hope this helps.

Newbie | Invoking a Dot Net Web Service

Hey,
I need to call a web service built in .net in one of my java files. How can I do this?
I think HttpUrlConnection class is used for this. Can someone please share some sample code?
Anticipating,
Nick

I'll give you a tip in stead. See that textbox to the left of this page? It has a label "search forums". Using it you can search this forum! I myself have already posted the example code to use URLConnection many times, and I'm not the only one who did.
Another tip: never bluntly ask for example code. People here like to help you with a problem, but they hate having to do the work for you.

Posting large amount of data via sync web service

Hi,
I'm trying to posting a large data via sync soap adapter and receiver as abap proxy. I'm getting log version status in SXMB_MONI when ever i try to post data >5k. Any idea how to trace it? If got timeout should there be an error message in SXMB_moni instead of log version? Thanks.

Hi,
This message occurs when process on receiving system somehow is locked and does not return a response.
your receiving system is an ABAP system, goto sm66 ,sm12 in th abap system. In sm66 look for transactions which are running for very long and inside sm12 look for locks that interfere in processing of message on the abap system.
also maybe the response system was locked when time request was send and therfore no response was received.
also chk this blog :-
/people/michal.krawczyk2/blog/2005/05/10/xi-i-cannot-see-some-of-my-messages-in-the-sxmbmoni
hope it helps.
Regards,
Rohit

ODSI to Invoke an A sync Web service

Similar Messages

Maybe you are looking for