Invoke NTLM Authentication Based WebService from BPEL

Hi All,
I am working with SOA Suite 11.1.1.6 version deployed on Weblogic Server (Linux Based OP).
I have a requirement where i need to invoke a webservice which exposes a NTLM Based Authentication. Since this particular webservice doesn't even get loaded if we dont pass the credentials. For example :- If i hit the WSDL URL on browser, it first ask for the credentials and on success , it loads the WSDL File.
First i have tried using this WS using SOAP UI and were able to invoke it successfully , because SOAP UI can handle the NTLM Authentication Properly. And it gives us the wizard to put the credentials when we load the WSDL in SOAP UI.
But the problem comes when i use that WS using our SOA Composite. The WSDL Doesn't get loaded only , since it requires the credentials first. I am not sure how should i go ahead and invoke this. I have checked lot of blogs but none of them were useful for me.
Did anybody face this issue/ task to invoke a WS which doesn't get loaded without passing the credentials and also to invoke it through BPEL composites deployed on the weblogic server (based on Linux OP).
Please suggest!!!
Regards,
Shah

Hi,
I am in a similar situation.
I am able to successfully invoke the webservice via soapUI when I pass the username, password and the domain.
If I do not pass the domain name in the SOAPUI or even in SOA, I get HTTP 401, Unauthorized error. 
However, I am able to set only the
oracle.webservices.auth.username a
oracle.webservices.auth.password properties when I configure it in SOA 11g.
I tried passing the domain name in the oracle.webservices.auth.username property as domainname\username. But no luck
The composite is deployed on a linux server. Please suggest/advice any pointers to resolve this NTLM authentication issue.

Similar Messages

  • Invoke the secured webservice from BPEL in Solaris environment

    Hi All,
    Can any one tell me how to invoke the secured webservice from BPEL in Solaris environment as i am able to invoke the secured web service from BPEL in windows platform(soa suite 10.1.3.4).
    we have applied 10.1.3.4 patch on solaris environment but we are not able to invoke the same.
    Thanks in advance
    Regards,
    Nagaraju .D

    Hi Nagaraju,
    Read your post.We've somewhat the similar problem as yours as we are facing some error while invoking a WS-Security secured web service from our BPEL Process on the windows platform(SOA 10.1.3.3.0).
    For the BPEL process we are following the same steps as given in an AMIS blog : - [http://technology.amis.nl/blog/1607/how-to-call-a-ws-security-secured-web-service-from-oracle-bpel]
    but sttill,after deploying it and passing values in it,we are getting the following error on the console :-
    “Header [http://schemas.xmlsoap.org/ws/2004/08/addressing:Action] for ultimate recipient is required but not present in the message”
    As you have wriiten that you've already called a secured web service in windows platform ,so if you can please help me out in this issue.
    I've opened a separate thread for this to avoid confusion. :-
    Error while invoking a WS-Security secured web service from Oracle BPEL..
    Thanks,
    Saurabh

  • 10g: Invoking a web service asynchronously from BPEL

    Hello,
    I am trying to figure out a good, generic method for making a previously synchronous web service asynchronous and changing the way in which it is invoked from BPEL. I am using SOA Suite 10g (10.1.3.5)
    As I understand, one possible method to achieve this is to use IDeliveryService.post() to deliver the web service's response to the BPEL process. For this route, the standard practice of correlation seems to be to supply a correlation Id when invoking the web service and returning the same correlation id as a part of the web service's response message. However, I want to avoid this since it would mean that all response messages from the web service (10+) would have to be modified to include a correlationId, which is problematic in the special case of this web service. Including a correlationId in the request message is possible, however.
    I have tried the approach of using the conversation Id directly instead of the correlation Id, by reading the value of ora:getConversationId(), passing this to the web service and setting the property CONVERSATION_ID of the response NormalizedMessage to the same value when returning. However, I cannot seem to get this approach right. Is this possible at all?
    An alternative might be to use WS-Addressing, but I do not know if I can make the web service support this - it is written using the EJB WebService-Annotations feature and runs on OC4J as well.
    Do you have any suggestions on how this problem could be resolved?
    Edited by: 901765 on 12.12.2011 06:01

    I have found the following tutorial that implements something similiar to what I am trying to do: http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/10g/10135/odiscenario_bpelcallback/odiscenario_bpelcallback.htm#t3
    Because of this, I am now confident that the conversation IDs can be used to achieve correlation. I have implemented the pattern by performing
    an invoke activity on the web service, passing the result of ora:getConversationId() as part of the message. The conversation Id returned is of UUID-Form.
    After the invoke activity, I have added a pick activity to receive the response message supplied by the web service through IDeliveryService.post(...). I can see that the message is received correctly by loooking at the contents of DLV_MESSAGE. However, the pick activity times out every time (after 10m). Looking at DLV_SUBSCRIPTION reveals that the conversation_id for the pick/receive activity is set to a value of the form bpel://localhost/default/MyBpelProcessName~1.0/7610001-BpInv0-BpSeq2.7-2. As far as I know, this should instead be set to the UUID that ora:getConversationId() returned before performing the invoke activity. What is going wrong here?
    Thanks for your help!

  • How To : Call External Webservice from BPEL and pass SOAP Message to the WS

    Hello All-
    Greetings to all BPEL gurus. I am currently facing difficulties in calling an External Webservice from my BPEL Process and passing SOAP Message to it. The details are below:
    <strong>1. The BPEL process, using database polling feature of DB Adapter, will get the records from the database.</strong>
    <strong>2. Transform the message</strong>
    <strong>3. Call the External Webservice and pass the transformed message as the input to it. However the Webservice expects the BPEL process to send SOAP headers in the input message.</strong>
    I am struggling on how to put the transformed message within a SOAP envelope in the BPEL process.
    If anyone had similar requirements and have successfully been able to send SOAP messages from BPEL process to an external webservice, kindly let me know.
    Also if there is some kind of documentation or any link in the forum that I can refer, please let me know that as well.
    I am new to Webservice integration using BPEL and would really appreciate your help.
    Thanks In Advance
    Regards,
    Dibya

    Hi Dharmendra,
    I am trying to send a SOAP message from my BPEL process to a web service. I have a complete SOAP message in a complex variable defined in the wsdl for the partnerlink (web service). My problem is that when I invoke the partnerlink it fails even though the content shown in the BPEL console looks valid.
    I have set up obtunnel to see what I am actually sending out from BPEL. You mention that BPEL creates the SOAP envelope automatically.
    I think that my problem is a result of this automatic SOAP envelope that BPEL is creating. Do you know if there is a way to turn it off?
    This is what I see in the TCP monitor, please note the double SOAP env:Body:
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <env:Body> <RCMR_IN000002NR01 xmlns="urn:hl7-org:v3" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
    <env:Header>
    <wsa:To xmlns:wsa="http://www.w3.org/2005/08/addressing">http://testhost/CCS/Service_Endpoint</wsa:To>
    <wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
    <wsa:Address>http://localhost/CCS/Service_Endpoint</wsa:Address>
    <wsa:Metadata>
    <device xmlns:hl7="urn:hl7-org:v3">
    </device>
    </wsa:Metadata>
    </env:Header>
    <env:Body>
    <RCMR_IN000002NR01>
    </RCMR_IN000002NR01>
    </env:Body>
    </RCMR_IN000002NR01>
    </env:Body>
    </env:Envelope>
    Any help is appreciated.
    Regards,
    Aagaard
    Edited by: Aagaard on Oct 30, 2008 8:59 PM
    Should have mentioned. I am using BPEL 10.1.3.4
    Edited by: Aagaard on Oct 31, 2008 8:43 AM
    I have opened a new thread for this question so as to not confuse the issue more than necessary.
    How many SOAP envelopes do you really need?

  • Authenticator not being invoked - NTLM authentication against IIS 6.0 !!

    Hi Folks,
    I am trying to access Microsoft Reporting Service running on IIS 6.0 through a Web Proxy (a simple application running in an App Server) using the NTLM authentication. This is what i am doing
    Authenticator.setDefault(new ReportAuthenticator());
    HttpURLConnection urlConnection = (HttpURLConnection) url.openConnection();.
    As i understand, the authentication is to magically work with the IIS Server requesting my web proxy for the credentials on connect whcih should involke the Authenticaor class.
    Howver this is not happening at the moment. The authenticator object never gets invoked and even then my web proxy is being able to chat to IIS. The Sun app server hosting my web proxy is somehow passing my windows credentials to IIS and since my account has sufficient previliges on IIS, i am able to get through the initial connection.
    When i debug the urlConnection object, i can see that the connection recognises that this is an NTLM authentication but is obviously not using the Authenticator credentials.
    Is the Authenticator object meant to be invoked automatically or do i need to set some header information in the urlConnection??
    Any help is greatly appreciated.
    P.S: I am using JDK 1.5, IIS 6.0, Sun App Server 9.0 (platform edition)
    best regards
    Dushy

    Hi,
    we had the same problem, but we got support
    from readme.txt
    Bug#: 6789020
    Agent type: All Agents
    Description: In CDSSO mode non enforced POST requests cannot be accessed
    Bug#: 6736820
    Agent type: IIS 6 Agent
    Description: IIS 6 agent doesn't work properly with ASP pages in CDSSO mode
    Both bugs should be fixed in this version:
    Sun Java System Web Agents 2.2-02 hotpatch2

  • Consume a third party REST Based Webservice from PeopleSoft

    We are in tools 8.49.33
    Using 'Consume Web Service' component we can only consume a WSDL based webservice I guess. But we have a requirement to consume to a third party webservice, for which we just have to invoke a URL with query string via HTTP GET and receive an XML response. Has anyone done this before?

    Three things to check:
    #1: Check your errorLog.html file in the PSIGW web app of your PeopleSoft server
    #2: Does your app server have to go through a proxy to connect to the internet? If so, did you configure integrationGateway.properties to use a proxy server? You can test this by trying to use ConnectorRequestURL for a plain old HTTP web site. If you get the same error, then it is likely a proxy issue.
    #3: If #2 passed, then it might have to do with certificates and you will need to review PeopleBooks for importing certificates for integration broker. I haven't had to do this before, but am pointing it out in case.

  • Rest based webservices from plsql procedures/packages

    Guyz.
    Please let me know How to create Rest based webservices in jdeveloper tool from plsql procedures/packages.
    Im very much in need
    Thanks,

    Hi User ,
    Welcome to OTN !!
    You can refer to these links and figure out -
    http://docs.oracle.com/cd/E16162_01/user.1112/e17455/dev_web_services.htm#CHDJIFAE
    http://theblasfrompas.blogspot.com/2011/03/developing-restful-web-services-from.html
    Also for calling pl/sql packages from Java , use soemthing like this - http://www.coderanch.com/t/302171/JDBC/databases/execute-PL-SQL-program-Java

  • Calling Webservice from BPEL - Urgent

    Hi,
    Appreciate if anyone can let me know steps or point to some documentation on how to call an external web service from BPEL. I have this URL ( http:// testinstance/ Connect/ Customer.asmx) to use as WSDL and the two Request and Response XSD files.
    I created an Asynchronous BPEL Process which created the 'client' PartnerLink and the 'recieveinput' and 'callbackClient' activities. Next I tried to create another partner link and I'm stuck here as I do not know where and how to associate the above URL as the WSDL file location.
    Please help,
    Thanks
    -Prapoorna

    You need to 'model' a little bit of processflow for this.
    At the moment you created the partnerlink.
    In the process you need to 'invoke' this partnerlink to call the method in the service which will check if the customer exists.
    When creating the invoke in the process it will give you the option to create the input/output-variables (or input when async).
    This inputvariable needs to get 'assigned' in your process. So this variable will get the value of the customerid for who you want to check if he exists.
    The services comes back with some result in the outputvariable, and this variable you can use to model the rest of the process.
    for example with a 'switch' which is some sort of if-then-else-construction.
    or did i missunderstood you :)

  • Calling HTTPS webservice from BPEL

    Hi All,
    We have enable SSL on soa 11g and its working fine.
    We have developed and deployed a process on same soa server, Now we are trying to invoke this service (process) in another BPEL process.
    While developing the second BPEL process in jdev we are not getting any error but while deploying (on the same server) its throwing error.
    The second process gets deployed without any error if we dont call the HTTPS webservice(first BPEL process).
    Please help.
    Error desc:
    Error during deployment: Deployment Failed: Unable to find a WSDL that has a definition for service {http://oracle.com/sca/soapservice/TSystemOrderProcessing/TSystemOrderProcessing/receivePO}receivePO and port execute_pt. Please make sure that the port attribute for the binding defined in the composite file is correct by checking the namespace, service name, and port name. In addition, check that the WSDL associated with the binding namespace is imported and currently reachable (check the import nodes at the top of the composite file). Finally, validate the HTTP proxy settings for the server..
    [05:30:06 PM] Check server log for more details.
    Regards,
    Surendra

    Hi Surendra,
    It seems that WSDL for service receivePO is not available at the deployment time.
    Below threads should help you out -
    Partner Link in 11g
    SOA 11g FOD Demo Deploy Issue
    Regards,
    Anuj

  • Getting error  connection timed out while invoking webservice from bpel.

    Hi,
    I am trying to call a secure webservice developed in .Net having extension .svc from the bpel service and in response i am getting error
    com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}remoteFault}
    messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
    parts: {{summary=<summary>exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection timed out: connect</summary>
    I am able to call this web service from the java programme using HTTPClient by setting the username/password and soapaction in http Header but not from the BPEL process. This .Net service is synchronous in nature. I also set the proxy in opmn.xml but didn't got any success.
    Please reply me ASAP. Need urgent help.
    Thanks.

    Are you working on 11g ? if this is 11g
    How are you invoking the webservice ...does it have any authentication..
    If the webservice which you are invoking has basic http authentication...
    1. In the composite.xml file, right click on the reference and configure WS policies. In security tab, add a security policy named"oracle/wss_http_token_client_policy"
    2. Add two binding properties for the reference
    (i) oracle.webservices.auth.username
    (ii) oracle.webservices.auth.password
    and provide the username and password for those two properties...
    Just try this out...
    Thanks,
    N

  • Binding Fault invoking an axis2 webService from BPEL

    Hi,
    I have deployed axis2 on the OC4J application server. And then I have deployed a web service to axis2. I can access the wsdl and create the partner link in the jdeveloper. The problem appears in execution time.
    When I run the BPEL process the following error appears:
    <2008-08-27 14:41:20,906> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> invoke failed
    org.collaxa.thirdparty.apache.wsif.WSIFException: [email protected]2 : Could not find binding output for operation insertOrUpdate at com.collaxa.cube.ws.wsif.providers.http.WSIFOperation_HTTP.getOutputMIMEXmlPart(WSIFOperation_HTTP.java:205) at com.collaxa.cube.ws.wsif.providers.http.WSIFOperation_HTTP.executeRequestResponseOperation(WSIFOperation_HTTP.java:308)
         at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:435)
    From .NET application we can invoke the web service so I think the web service is ok. Does anybody know how to solve this issue? I have been searching for a solution and I have only found questions about this..
    Any help would be appreciated.
    Thanks in advance,
    Zaloa

    Hi,
    Just in case someone runs into the same problem, I live here my solution:
    In may case the problem was the wsdl definition. I developed the web service in java and generated the wsdl with Maven. Automatically it generates the wsdl like this (I just copy the last section):
    <wsdl:service name="tso-ws">
    <wsdl:port name="tso-wsHttpSoap11Endpoint" binding="ns:tso-wsSoap11Binding">
    <soap:address location="http://localhost:8080/axis2/services/tso-ws"/>
    </wsdl:port>
    <wsdl:port name="tso-wsHttpSoap12Endpoint" binding="ns:tso-wsSoap12Binding">
    <soap12:address location="http://localhost:8080/axis2/services/tso-ws"/>
    </wsdl:port>
    <wsdl:port name="tso-wsHttpEndpoint" binding="ns:tso-wsHttpBinding">
    <http:address location="http://localhost:8080/axis2/services/tso-ws"/>
    </wsdl:port>
    </wsdl:service>
    The problem was the <wsdl:service name="tso-ws"> section. There were 3 port definitions with 3 different bindings but all of them have the same service location. So In the BPEL process I created the partner link using the service location.
    I guess BPEL was using the http binding, so I deleted two of the por definitions and just left this in the <wsdl:service name="tso-ws"> section of the wsdl
    <wsdl:service name="tso-ws">
    <wsdl:port name="tso-wsHttpSoap12Endpoint" binding="ns:tso-wsSoap12Binding">
    <soap12:address location="http://localhost:8080/axis2/services/tso-ws"/>
    </wsdl:port>
    By doing this, it works. I read in some forums that BPEL doesn't work with the http_post protocol so that's why I deleted that definition. And someone told me that it uses soap12 so that's why I deleted that definition also.
    That's the way I solved it. Hope this helps.
    Regards,
    Zaloa

  • New problem calling PL/SQL based WS from BPEL process

    I have created a webservice based on a PL/SQL package based function with JDeveloper and deployed the web service on the BPEL OC4J server.
    Calling the web service endpoint directly from internet explorer works fine.
    I have also created and deployed a BPEL process to call this web service. When i run the process it completes normally but returns an Oracle error in the out-variable: "Ora-06502 Numerical value error".
    Through my PL/SQL logging i can see that the input-variable to the PL/SQL function is empty (so when i try to use this value it gives me the Ora-06502 error).
    When i check the audit trail of the BPEL process instance i find that the assignment of the input variable is ok. This input variable is used in the invokation of the web service (and at this point still has the proper value).
    What can be wrong? (the only part i cannot trace is the working of the Java stub created by JDeveloper).
    Any ideas?
    thanks, Bart

    This is the complete stack trace:
    <2004-12-01 10:48:52,012> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> operation: CataLog
    <2004-12-01 10:48:52,012> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> inputContainer: {InputParameters=<CATLOG xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/EBILLING/CATALOG/"><ID_AZIENDA>134</ID_AZIENDA><ID_PROGETTO>134</ID_PROGETTO><CAPTURE_DATETIME>1959</CAPTURE_DATETIME><FULLNAME>lkjh</FULLNAME><PATHNAME>kjsf</PATHNAME><FILENAME>kjsf</FILENAME><DESTINATION_PATH>kjsf</DESTINATION_PATH><MOVE_DATETIME>1959</MOVE_DATETIME><SIZE_BYTES>134</SIZE_BYTES><LAST_WRITE>1959</LAST_WRITE><ID_THOR>2345234</ID_THOR><SNAPSHOT_PATH>kjsf</SNAPSHOT_PATH></CATLOG>}
    <2004-12-01 10:48:52,013> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> callProps: {is-initial-call=true, parentId=5602, process-id=StoredProcedure, rootId=5602, conversationId=bpel://localhost/default/StoredProcedure~1.0/5602-BpInv0-BpSeq0.3-3, location=null, priority=0, work-item-key=5602-BpInv0-BpSeq0.3-3, domain-id=default, revision-tag=1.0}
    <2004-12-01 10:48:52,013> <DEBUG> <default.collaxa.cube.ws> <WSInvocationManager::invoke> def is http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl
    <2004-12-01 10:48:52,014> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> opName=CataLogportTypeQn={http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog_pttserviceQn={http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog
    <2004-12-01 10:48:52,015> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[{http://xmlns.oracle.com/pcbpel/adapter/db/test/CataLog/}CataLog_ptt]: Locating jndiAdapterInstance eis/CatapultDBLog
    <2004-12-01 10:48:52,015> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Instantiating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec
    <2004-12-01 10:48:52,016> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Populating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec with properties: {ProcedureName=CATALOG, SchemaName=EBILLING}
    <2004-12-01 10:48:52,234> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Instantiating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec
    <2004-12-01 10:48:52,235> <DEBUG> <default.collaxa.cube.ws> <AdapterFramework::Outbound> Populating outbound JCA interactionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec with properties: {ProcedureName=CATALOG, SchemaName=EBILLING}
    <2004-12-01 10:48:52,294> <INFO> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] Invoking JCA outbound Interaction
    <2004-12-01 10:48:52,296> <DEBUG> <default.collaxa.cube.ws> <Database Adapter::Outbound> <oracle.tip.adapter.db.TopLinkLogger log> client acquired
    <2004-12-01 10:48:52,297> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound> http://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] Could not invoke 'CataLog' due to: Encountered an unexpected exception while trying to execute the interaction.
    An unexpected exception occurred while trying to execute the interaction for invoking the API.
    Analyze and correct the error if possible. Contact oracle support if error is not fixable.
    <2004-12-01 10:48:52,299> <ERROR> <default.collaxa.cube.ws> <AdapterFramework::Outbound> ORABPEL-11813
    Encountered an unexpected exception while trying to execute the interaction.
    An unexpected exception occurred while trying to execute the interaction for invoking the API.
    Analyze and correct the error if possible. Contact oracle support if error is not fixable.
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
    at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
    at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
    at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
    at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
    at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
    at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
    at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
    at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
    at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
    at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
    at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
    at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
    at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
    at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
    at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: java.lang.NumberFormatException: null
    at java.lang.Integer.parseInt(Integer.java:436)
    at java.lang.Integer.<init>(Integer.java:609)
    at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
    at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
    ... 27 more
    java.lang.NumberFormatException: null
    at java.lang.Integer.parseInt(Integer.java:436)
    at java.lang.Integer.<init>(Integer.java:609)
    at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
    at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
    at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
    at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
    at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
    at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
    at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
    at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
    at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
    at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
    at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
    at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
    at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
    at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
    at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
    at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
    at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
    at java.lang.Thread.run(Thread.java:534)
    <2004-12-01 10:48:52,300> <DEBUG> <default.collaxa.cube.ws> <WSIFInvocationHandler::invoke> Fault happenned
    ORABPEL-11813
    Encountered an unexpected exception while trying to execute the interaction.
    An unexpected exception occurred while trying to execute the interaction for invoking the API.
    Analyze and correct the error if possible. Contact oracle support if error is not fixable.
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
    at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
    at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
    at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
    at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
    at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
    at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
    at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
    at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
    at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
    at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
    at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
    at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
    at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
    at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
    at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: java.lang.NumberFormatException: null
    at java.lang.Integer.parseInt(Integer.java:436)
    at java.lang.Integer.<init>(Integer.java:609)
    at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
    at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
    ... 27 more
    <2004-12-01 10:48:52,302> <DEBUG> <default.collaxa.cube.ws> <BPELInvokeWMP::__invoke> Caught RemoteException
    orabpel.apache.wsif.WSIFException: oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA@788a7bhttp://orcldemo.localdomain:9700/orabpel/default/StoredProcedure/StoredProcedureOutbound.wsdl[CataLog_ptt::CataLog(null)] : Could not invoke 'CataLog' due to: Encountered an unexpected exception while trying to execute the interaction.
    An unexpected exception occurred while trying to execute the interaction for invoking the API.
    Analyze and correct the error if possible. Contact oracle support if error is not fixable.
    ; nested exception is:
    ORABPEL-11813
    Encountered an unexpected exception while trying to execute the interaction.
    An unexpected exception occurred while trying to execute the interaction for invoking the API.
    Analyze and correct the error if possible. Contact oracle support if error is not fixable.
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:464)
    at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:356)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:288)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:134)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:541)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:284)
    at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:178)
    at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3438)
    at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1818)
    at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:85)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:138)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5522)
    at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1221)
    at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
    at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
    at IDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(IDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1791)
    at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:36)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:62)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
    at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
    at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
    at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:745)
    at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:917)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: ORABPEL-11813
    Encountered an unexpected exception while trying to execute the interaction.
    An unexpected exception occurred while trying to execute the interaction for invoking the API.
    Analyze and correct the error if possible. Contact oracle support if error is not fixable.
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:429)
    at oracle.tip.adapter.db.DBInteraction.execute(DBInteraction.java:140)
    at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:395)
    ... 25 more
    Caused by: java.lang.NumberFormatException: null
    at java.lang.Integer.parseInt(Integer.java:436)
    at java.lang.Integer.<init>(Integer.java:609)
    at oracle.tip.adapter.db.sp.XSDParser.parseParameters(XSDParser.java:221)
    at oracle.tip.adapter.db.sp.SPInteraction.executeStoredProcedure(SPInteraction.java:69)
    at oracle.tip.adapter.db.DBInteraction.executeStoredProcedure(DBInteraction.java:421)
    ... 27 more

  • Unable to invoke Java WSIF Binding wsdl from BPEL

    Hi,
    I am using BPEL 10.1.3.1 version.
    - I created Greeting.java, then from JDev generate WebService for class but did not publish or deploy as web service
    - in BPEL created one partner link using same wsdl file from local file system
    - put invoke activity to call this partner link
    - deployed process
    - copied all class file with package folder inside $ORACLE_HOME/bpel/system/classes folder
    When i initiate the process i get error
    Failed get wsdl service definition.
    Failed to get a WSDL service that support the portType "{http://BusinessProcess/}Greeting" in WSDL definition "{http://BusinessProcess/}Greeting".
    Please verify that WSDL portType "{http://BusinessProcess/}Greeting" is supported by a service in WSDL file.
    Please help.

    Hi Jack
    Does your WSDL have the "binding" and "service" section? I do not use JDev or anything else to create the WSDL for me, I create it by hand so I don´t know how to help you in JDev, but it seens that JDev does not generate this sections and you must set then in order to use WSIF Bindings to Java or EJB.
    Regards
    Marcelo

  • Invoking a PL/SQL function from BPEL throws fault.

    Hi, I'm trying to invoke a PL/SQL function that inserts data in to a table from a BPEL via DB Adapter. The process, when I test it, throws a runtime fault as follows:
    *Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'EmpRegister' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. AddEmployee:EmpRegister [ EmpRegister_ptt::EmpRegister(InputParameters,OutputParameters) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/DBConn_215'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/DBConn_215. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.*
    Also, the fault description was a s follows:
    *JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/DBConn_215'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/DBConn_215. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server.*
    I know, it looks like a JCA adapter error, but when I do a DB to DB table synchronization with this connection factory, no problems happen. Is ther any special procedure I should follow in mapping input data to db schema?

    HI,
    I am working on BPEL process and human workflow...
    I created a process and a Data control and now can see it as JCA Adapter in console..in this adapter I am executing a sql procedure.. we can execute in in BPEL process through invoke activity, now my requirement is how to invoke this data control through custom java code. please help...\
    now i have two wsdl files.
    RegistrationUpload.wsdl(process name)
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions name="RegistrationUpload"
    targetNamespace="http://xmlns.oracle.com/RegistrationUpload_jws/RegistrationUpload/RegistrationUpload"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:client="http://xmlns.oracle.com/RegistrationUpload_jws/RegistrationUpload/RegistrationUpload"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
         <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         TYPE DEFINITION - List of services participating in this BPEL process
         The default output of the BPEL designer uses strings as input and
         output to the BPEL Process. But you can define or import any XML
         Schema type and use them as part of the message types.
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
         <wsdl:types>
              <schema xmlns="http://www.w3.org/2001/XMLSchema">
                   <import namespace="http://xmlns.oracle.com/RegistrationUpload_jws/RegistrationUpload/RegistrationUpload" schemaLocation="xsd/RegistrationUpload.xsd" />
              </schema>
         </wsdl:types>
         <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         MESSAGE TYPE DEFINITION - Definition of the message types used as
         part of the port type defintions
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
         <wsdl:message name="RegistrationUploadRequestMessage">
              <wsdl:part name="payload" element="client:process"/>
         </wsdl:message>
         <wsdl:message name="RegistrationUploadResponseMessage">
              <wsdl:part name="payload" element="client:processResponse"/>
         </wsdl:message>
         <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         PORT TYPE DEFINITION - A port type groups a set of operations into
         a logical service unit.
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
         <!-- portType implemented by the RegistrationUpload BPEL process -->
         <wsdl:portType name="RegistrationUpload">
              <wsdl:operation name="process">
                   <wsdl:input message="client:RegistrationUploadRequestMessage"/>
              </wsdl:operation>
         </wsdl:portType>
         <!-- portType implemented by the requester of RegistrationUpload BPEL process
         for asynchronous callback purposes
         -->
         <wsdl:portType name="RegistrationUploadCallback">
              <wsdl:operation name="processResponse">
                   <wsdl:input message="client:RegistrationUploadResponseMessage"/>
              </wsdl:operation>
         </wsdl:portType>
         <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         PARTNER LINK TYPE DEFINITION
         the RegistrationUpload partnerLinkType binds the provider and
         requester portType into an asynchronous conversation.
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
         <plnk:partnerLinkType name="RegistrationUpload">
              <plnk:role name="RegistrationUploadProvider">
                   <plnk:portType name="client:RegistrationUpload"/>
              </plnk:role>
              <plnk:role name="RegistrationUploadRequester">
                   <plnk:portType name="client:RegistrationUploadCallback"/>
              </plnk:role>
         </plnk:partnerLinkType>
    </wsdl:definitions>
    uploadDataToPermananentDB.wsdl
    <?binding.jca uploadDataToPermananentDB_db.jca?>
    <wsdl:definitions name="uploadDataToPermananentDB"
    targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/db/RegistrationUpload/RegistrationUpload/uploadDataToPermananentDB"
    xmlns:db="http://xmlns.oracle.com/pcbpel/adapter/db/DAMSMGR/TEMP_TO_PERMANENTDB/"
    xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/db/RegistrationUpload/RegistrationUpload/uploadDataToPermananentDB"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/">
    <plt:partnerLinkType name="uploadDataToPermananentDB_plt">
    <plt:role name="uploadDataToPermananentDB_role">
    <plt:portType name="tns:uploadDataToPermananentDB_ptt"/>
    </plt:role>
    </plt:partnerLinkType>
    <wsdl:types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://xmlns.oracle.com/pcbpel/adapter/db/DAMSMGR/TEMP_TO_PERMANENTDB/"
    schemaLocation="xsd/DAMSMGR_TEMP_TO_PERMANENTDB.xsd"/>
    </schema>
    </wsdl:types>
    <wsdl:message name="args_in_msg">
    <wsdl:part name="InputParameters" element="db:InputParameters"/>
    </wsdl:message>
    <wsdl:portType name="uploadDataToPermananentDB_ptt">
    <wsdl:operation name="uploadDataToPermananentDB">
    <wsdl:input message="tns:args_in_msg"/>
    </wsdl:operation>
    </wsdl:portType>
    </wsdl:definitions>
    please help me how to call the data adaper from my java code..
    hope i will get some hint in this forum...
    Edited by: user13370040 on Mar 22, 2011 5:55 AM

  • Invoking long running web service from BPEL

    I have a web service. It takes more than 5 minutes (could be up to a few hours) to run. Now I need to invoke it from the BPEL workflow. I tried it, but doesn't work. It seems that there is timeout problem. Does anyone know how to integrate the long-running process into workflow?
    Thanks a lot.

    Yes, I am using a sync process. Currently, I divide the process into two parts: launchProcess() and getResult(). Then in BPEL workflow, I use a loop to check getResult(). It works, but I am wondering if there is any better solution.
    I think my situation is very common in the community. Fortunately, I can split the process into two parts. But for some long-running process, it can be difficult to split. How can we implement the process as an async process and integrate it into BPEL workflow? My process is written in Java. I am not familiar to the async process. Any suggestions?
    Thanks a lot.

Maybe you are looking for