Correlation initiate in invoke in the Async BPEL

Hello, All
I need you help. Now I have a Async BPEL. and I need to use the Correlation waiting for message at a second Receive activity. So I need initial the Correlation. But I do not initial the Correlation in the first Receive, I want to initial the Correlation in the Invoke activity before the second Receive activity. But the BPEL can not receive the message. If I do the same operation in the Sync BPEL. It is ok. so I can not initial the Correlation in the invoke activity? but how can I resolve the problem. BPEL diagramm is :
Receive
|
Invoke(set Correlation and initial the Correlation)
|
Receive(Set Correlation)
|
Invoke
Thank you.
Allen
Edited by: user12043916 on 2009/10/13 23:32

Its an old link, but see if it is helpful, probably it speaks about what u are looking for.
http://swapnil-soa.blogspot.com/2008/01/correlation-this-post-would-effort-to.html
hope that helps,
SwapSawe.
P.S. By any chance are you working on Async Request/Reply scenario of JMS Adapter in Oracle 11g?
Edited by: SwapSawe on Nov 30, 2009 4:50 AM

Similar Messages

  • Sync Mediator calling Async BPEL

    Hi,
    I have an Synchronous mediator which will invoke an Async BPEL. Aync BPEL will do some processing and need to send the response back to the mediator which is not happening.
    Any ideas on how to get the response from the Async BPEL pass on to the Sync Mediator which is calling the Async BPEL.

    Its async. It would not synchronize with a response. it doesnt matter if you link sync to async. In case, if you really want a response , please change your async to sync.

  • Callback activity not getting invoked in Async BPEL

    Hi
    I have an Async BPEL process which uses correlations.I have a receive activity in the middle using the correlation.
    When executed the BPEL gets invoked and waits during the receive activity and proceeds further when the service is hit with the required correlated data also but the problem is the process does not get into completed state.When viewed from the BPEL console it shows all the activites upto Call back client but not the call back activity.The other activities get executed properly without any error.
    One more point i would like to mention here is another Sync BPEL is invoking this process [The Sync BPEL just invokes and proceeds further without waiting for any result from the Async process.]
    Need Urgent help on this plss.
    Vamsi

    Hi Peter,
    Thanx for your reply. Actually i tried putting Java embedding activity [with checkpoint()] before and after the call back activity. When i execute the same it comes upto the java embedding which is before the call back and just hnags there. The status of the bpel is also shown as Active.
    Any more help pls..
    Vamsi

  • Invoking a WS from BPEL - WS URL is hardcoded in the WSDL

    I have published a PL/SQL package as a webservice and deployed it successfully to a development instance (say DEV).
    I created a BPEL process and used a Partner Link to invoke the above web service. When I deploy the BPEL process to the DEV instance, it works fine. However when I deployed the above WS and BPEL process to another instance (say TEST), the BPEL process still calls the WS in the original (DEV) instance. I verified by invoking the WS in the TEST instance and it is working fine.
    When I created the partner link in the BPEL process, I had to provide the actual WS url from the DEV instance and it created the WSDL for me. This probably is causing the issue as the DEV WS url is hardcoded in the WSDL. However I do not know how to provide the WSDL in the partner link so that url/server name is not hardcoded.
    Any help with this is greatly appreciated.
    JDev - 10.1.3.4
    SOA Suite - 10.1.3.4
    Thanks.
    Edited by: user13163442 on Jul 21, 2011 1:10 PM

    Naren,
    Thanks for looking into this.
    Yes, the web service is calling a packaged procedure which is available in both the environments. This web service is independent and may be used by other BPEL processes or other applications too.
    I developed the WS & BPEL process in the dev environment and then deployed to the TEST environment. I did not make any changes to the BPEL & WS before deploying to TEST. The only change I did after deploying the WS to the TEST environment is to map the jndi.
    I am not calling the package directly -- I want to consume the WS.
    I am not sure about the Composite? Is this something in SOA 11g? I am still on SOA 10.1.3.4
    Is this helpful? Did I answer your questions correctly?
    Thanks again.

  • Problem in building schema when try to invoke the another BPEL service

    Hi all,
    Whenever try to Invoke a another BPEL service using the Invoke activiy and Partnerlink, we need to create a variable structure similar to the providing service.
    For this I used create Auto Varible option available in the invoke activity. But after creating the variable, I tried to expand the variable for the copy operation, the error iam getting is Problem in building schema.
    This error never happened to me before. I have no clue.
    Jdev version:10.1.3.3.0
    Soa version:10.1.3.3.0
    Please help me on this.
    Thanks.

    Hi Lokesh,
    Iam not able to understand what you are trying to say. But my Input variable and Invoke Input variable are compatible, no problem on this. I got some clue from your reply.
    Finally I got it worked by doing it in another way.
    In my Invoking BPEL Process(ie. BPEL Process is trying to invoke the another BPEL Process using Partnerlink) wsdl I imported the partnerlink BPEL schema and it get solved my problem.
    eg) <import namespace="http://xmlns.oracle.com/BpelProcessname" schemaLocation="ParnerLinkBPELSchema.xsd"/>
    This can be usefull for others and I never did this to import the schema manually before, but it works without any errors.
    Now only it causing this problem, whether it is any Jdeveloper issue.
    And i tryed this using Jdev version 10.1.3.4.0, but still the same exception.
    This workaround will usefull for others.
    Thanks for your reply.
    bye.....

  • OdiInvokeWebService invoke the Async ws error!! not a well-formed document

    Hello, Everybody, I need you help.
    I use the OdiInvokeWebService utility to invoke the Async web service in the ODI Design. the Async service can run successful. but the ODI has the error:The root element is required in a well-formed document. If I use the OdiInvokeWebService to invoke the sync web service. It is ok, not error happens. so i guess that maybe beacause the Async has not the reponse message. but I don't know how to resolve the problem. PLZ help. thanks.
    com.sunopsis.wsinvocation.SnpsWSInvocationException: org.xml.sax.SAXParseException: The root element is required in a well-formed document.
         at com.sunopsis.wsinvocation.client.a.a.d.requestReply(d.java)
         at com.sunopsis.graphical.wsclient.f.b(f.java)
         at com.sunopsis.graphical.tools.utils.swingworker.v.call(v.java)
         at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
         at com.sunopsis.graphical.tools.utils.swingworker.l.run(l.java)
         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
         at java.lang.Thread.run(Unknown Source)
    Caused by: org.xml.sax.SAXParseException: The root element is required in a well-formed document.
         at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
         at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:701)
         at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
         at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
         at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
         at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
         at org.apache.axis.client.Call.invoke(Call.java:2767)
         at org.apache.axis.client.Call.invoke(Call.java:1792)
         at com.sunopsis.wsinvocation.client.a.a.d.a(d.java)
         ... 8 more
    Caused by: org.xml.sax.SAXParseException: The root element is required in a well-formed document.
         at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1213)
         at org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:570)
         at org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.endOfInput(XMLDocumentScanner.java:790)
         at org.apache.xerces.framework.XMLDocumentScanner.endOfInput(XMLDocumentScanner.java:418)
         at org.apache.xerces.validators.common.XMLValidator.sendEndOfInputNotifications(XMLValidator.java:712)
         at org.apache.xerces.readers.DefaultEntityHandler.changeReaders(DefaultEntityHandler.java:1031)
         at org.apache.xerces.readers.XMLEntityReader.changeReaders(XMLEntityReader.java:168)
         at org.apache.xerces.readers.UTF8Reader.changeReaders(UTF8Reader.java:182)
         at org.apache.xerces.readers.UTF8Reader.lookingAtChar(UTF8Reader.java:197)
         at org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:686)
         at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381)
         at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
         at javax.xml.parsers.SAXParser.parse(Unknown Source)
         at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
         at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
         ... 15 more
    Caused by:
    AxisFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
    faultSubcode:
    faultString: org.xml.sax.SAXParseException: The root element is required in a well-formed document.
    faultActor:
    faultNode:
    faultDetail:
         {http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException: The root element is required in a well-formed document.
         at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1213)
         at org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:570)
         at org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.endOfInput(XMLDocumentScanner.java:790)
         at org.apache.xerces.framework.XMLDocumentScanner.endOfInput(XMLDocumentScanner.java:418)
         at org.apache.xerces.validators.common.XMLValidator.sendEndOfInputNotifications(XMLValidator.java:712)
         at org.apache.xerces.readers.DefaultEntityHandler.changeReaders(DefaultEntityHandler.java:1031)
         at org.apache.xerces.readers.XMLEntityReader.changeReaders(XMLEntityReader.java:168)
         at org.apache.xerces.readers.UTF8Reader.changeReaders(UTF8Reader.java:182)
         at org.apache.xerces.readers.UTF8Reader.lookingAtChar(UTF8Reader.java:197)
         at org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:686)
         at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381)
         at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
         at javax.xml.parsers.SAXParser.parse(Unknown Source)
         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:435)
         at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
         at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
         at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
         at org.apache.axis.client.Call.invoke(Call.java:2767)
         at org.apache.axis.client.Call.invoke(Call.java:1792)
         at com.sunopsis.wsinvocation.client.a.a.d.a(d.java)
         at com.sunopsis.wsinvocation.client.a.a.d.requestReply(d.java)
         at com.sunopsis.graphical.wsclient.f.b(f.java)
         at com.sunopsis.graphical.tools.utils.swingworker.v.call(v.java)
         at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
         at com.sunopsis.graphical.tools.utils.swingworker.l.run(l.java)
         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
         at java.lang.Thread.run(Unknown Source)
         {http://xml.apache.org/axis/}hostname:IBM-3D5B978A816
    org.xml.sax.SAXParseException: The root element is required in a well-formed document.
         at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
         at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:701)
         at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
         at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
         at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
         at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
         at org.apache.axis.client.Call.invoke(Call.java:2767)
         at org.apache.axis.client.Call.invoke(Call.java:1792)
         at com.sunopsis.wsinvocation.client.a.a.d.a(d.java)
         at com.sunopsis.wsinvocation.client.a.a.d.requestReply(d.java)
         at com.sunopsis.graphical.wsclient.f.b(f.java)
         at com.sunopsis.graphical.tools.utils.swingworker.v.call(v.java)
         at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
         at com.sunopsis.graphical.tools.utils.swingworker.l.run(l.java)
         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
         at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
         at java.lang.Thread.run(Unknown Source)
    Caused by: org.xml.sax.SAXParseException: The root element is required in a well-formed document.
         at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1213)
         at org.apache.xerces.framework.XMLDocumentScanner.reportFatalXMLError(XMLDocumentScanner.java:570)
         at org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.endOfInput(XMLDocumentScanner.java:790)
         at org.apache.xerces.framework.XMLDocumentScanner.endOfInput(XMLDocumentScanner.java:418)
         at org.apache.xerces.validators.common.XMLValidator.sendEndOfInputNotifications(XMLValidator.java:712)
         at org.apache.xerces.readers.DefaultEntityHandler.changeReaders(DefaultEntityHandler.java:1031)
         at org.apache.xerces.readers.XMLEntityReader.changeReaders(XMLEntityReader.java:168)
         at org.apache.xerces.readers.UTF8Reader.changeReaders(UTF8Reader.java:182)
         at org.apache.xerces.readers.UTF8Reader.lookingAtChar(UTF8Reader.java:197)
         at org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XMLDocumentScanner.java:686)
         at org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.java:381)
         at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)
         at javax.xml.parsers.SAXParser.parse(Unknown Source)
         at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
         at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
         ... 15 more

    Hi, Aprendiz, Thanks for you apply. Do you meet this problem. If I use the OdiInvokeWebService to Invoke the sync webservice. It has not problem. But the Async webservice has the error log. Now I must use OdiInvokeWebService.Thank you.
    Allen

  • Problem while invoking ODI Scenario from BPEL

    Hi,
    I am trying to invoke a scenario from BPEL process through ODIPublicWebService.
    When I initiate the process, its failing with following error message....
    InvokeDeptAdmin_invokeScenario_OutputVariable>
    -<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="part1">
    -<ns1:invokeScenarioResponse xmlns:ns1="xmlns.oracle.com/odi/OdiInvoke/">
    <ns1:Ok>false
    </ns1:Ok>
    <ns1:SessionNumber>23101
    </ns1:SessionNumber>
    <ns1:ErrorMessage>Agent didn't execute this command:
    </ns1:ErrorMessage>
    </ns1:invokeScenarioResponse>
    </part>
    </InvokeDeptAdmin_invokeScenario_OutputVariable
    I observed that its failing as I am not giving any input to optional parameters like
    <xsd:element name="SessionName" minOccurs="0" type="xsd:string" />
    <xsd:element name="Keywords" minOccurs="0" type="xsd:string" />
    <xsd:element name="Variables" maxOccurs="unbounded" minOccurs="0" type="VariableType" />
    I can see following empty tags in my Audit of BPELConsole....
    <SessionName/>
    <Keywords/>
    <Variables/>
    And null is being considered as a variable by the Agent and following Exception is thrown in the Operator
    java.lang.Exception: Specified variable not found in the Repository : null
         at com.sunopsis.dwg.dbobj.SnpSession.a(SnpSession.java)
         at com.sunopsis.dwg.dbobj.SnpSession.y(SnpSession.java)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSessionPreTrt(SnpSession.java)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
         at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)
         at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
         at com.sunopsis.dwg.cmd.e.i(e.java)
         at com.sunopsis.dwg.cmd.h.y(h.java)
         at com.sunopsis.dwg.cmd.e.run(e.java)
         at java.lang.Thread.run(Unknown Source)
    Please let me know how can I overcome this problem
    Appreciate earliest response.
    Thanks!!!
    Message was edited by:
    user644377

    Hi, how are you?
    I did works including a parameter in my scenario and put value in this parameter on call scenario from BPEL. If i remove the parameter on the scenario and the call, its dont works.
    Try include a parameter in your scenario.

  • Async BPEL Process Invocation...

    We have a business process, which when invoked from BPEL console works fine, however, when we invoke it from an web application of ours, it does gets initiated, but fails later.
    We have Apache Axis deployed in the same OC4J server as the Oracle BPEL PM(10.1.2.0.2), which exposes few EJBs as SOAP Services.
    The Business Process invokes couple of SOAP Services and then creates a Task and then waits for task completion and based on task action invokes two other SOAP services.
    When we invoke it from the BPEL Console, everything works fine. It also works fine, if we invoke it first (after startup) from BPEL Console and then through our web application.
    However, if we invoke it first through our web application, then it does initiates, but fails at the Task creation. If we try to hit the BPEL Console, we get this error
    Oracle BPEL Process Manager Full Cycle
    An unexpected error has occurred while executing your request. This is most likely related to a defect in the Oracle BPEL Process Manager product. We apologize you can post the error to the OTN forum and we will get back to you as soon as possible.
    Attachments:
    Build Information:
    Oracle BPEL Server version 10.1.2.0.2
    Build: 2196
    Build time: Tue Jan 10 12:31:53 UTC 2006
    Build type: release
    Source tag: BPEL_10.1.2.0.2_GENERIC_060110.1200
    Exception Message:
    [java.lang.Exception]
    Failed to create "ejb/collaxa/system/ServerBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/collaxa/system/ServerBean not found
         at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:164)
         at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:333)
         at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:120)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
    <b>Nothing works after that, unless we re-start.</b>
    Once we re-start, BPEL Console works fine.
    Investigating the flow of the business process, we find the "initiateTask" of the workflow is fine, but it failed at "initiateTaskActionHandler" with the following error:
    <remoteFault>
    <part name="code" >
    <code>WSDLReadingError</code>
    </part>
    <part name="summary" >
    <summary>Failed to read wsdl. Failed to read wsdl at "http://Uranus:9700/orabpel/default/TaskActionHandler/TaskActionHandler?wsdl", because "WSDLException: faultCode=INVALID_WSDL: The document: http://Uranus:9700/orabpel/default/TaskActionHandler/TaskActionHandler?wsdl is not a wsdl file or does not have a root element of "definitions" in the "http://schemas.xmlsoap.org/wsdl/" namespace or the "http://www.w3.org/2004/08/wsdl" namespace.". Make sure wsdl is valid. You may need to start the OraBPEL server, or make sure the related bpel process is deployed correctly. </summary>
    </part>
    </remoteFault>
    <b>Below is the code as to how we are invoking the Business Process...using orabpel taglibs...</b>
    <orabpel:locator domainId="default" password="bpel" contextEnv="jndi">
    <orabpel:deliveryService processId="ApprovalProcess">
    <orabpel:post title="ApprovalProcess">
    <orabpel:part name="payload">
    <customerObj xmlns="http://xmlns.misys.com/ApprovalProcess/approval">
    <applicationNo><%= customer.getApplicationNo() %></applicationNo>
    <customerId><%= customer.getCustomerId() %></customerId>
    <primaryFirstName><%= customer.getPrimaryFirstName() %></primaryFirstName>
    <primaryLastName><%= customer.getPrimaryLastName() %></primaryLastName>
    <primaryCardName><%= customer.getPrimaryCardName() %></primaryCardName>
    <primaryDay><%= customer.getPrimaryDay() %></primaryDay>
    <primaryMonth><%= customer.getPrimaryMonth() %></primaryMonth>
    <primaryYear><%= customer.getPrimaryYear() %></primaryYear>
    <primaryDob><%= customer.getPrimaryDob() %></primaryDob>
    <primarySex><%= customer.getPrimarySex() %></primarySex>
    <primaryPanNo><%= customer.getPrimaryPanNo() %></primaryPanNo>
    <accountType><%= customer.getAccountType() %></accountType>
    <cardType><%= customer.getCardType() %></cardType>
    <primaryStreet1><%= customer.getPrimaryStreet1() %></primaryStreet1>
    <primaryStreet2><%= customer.getPrimaryStreet2() %></primaryStreet2>
    <primaryLandmark><%= customer.getPrimaryLandmark() %></primaryLandmark>
    <primaryCity><%= customer.getPrimaryCity() %></primaryCity>
    <primaryState><%= customer.getPrimaryState() %></primaryState>
    <primaryCountry><%= customer.getPrimaryCountry() %></primaryCountry>
    <primaryPinCode><%= customer.getPrimaryPinCode() %></primaryPinCode>
    <primaryOffPhoneNo><%= customer.getPrimaryOffPhoneNo() %></primaryOffPhoneNo>
    <primaryOffExtnNo><%= customer.getPrimaryOffExtnNo() %></primaryOffExtnNo>
    <primaryResPhoneNo><%= customer.getPrimaryResPhoneNo() %></primaryResPhoneNo>
    <primaryMobileNo><%= customer.getPrimaryMobileNo() %></primaryMobileNo>
    <primaryEmailId><%= customer.getPrimaryEmailId() %></primaryEmailId>
    <productInterest><%= customer.getProductInterest() %></productInterest>
    <sourceReferral><%= customer.getSourceReferral() %></sourceReferral>
    <channel><%= customer.getChannel() %></channel>
    <accountNo><%= " " %></accountNo>
    <documentsSubmitted><%= customer.getDocumentsSubmitted() %></documentsSubmitted>
    <creditRating><%= 0.0 %></creditRating>
    <eligibleCustomer><%= false %></eligibleCustomer>
    <segment><%= " " %></segment>
    <action><%= " " %></action>
    <remarks><%= " " %></remarks>
    <approverEmail><%= customer.getApproverEmail() %></approverEmail>
    <bPELProviderUrl><%= customer.getBPELProviderUrl() %></bPELProviderUrl>
    </customerObj>
    </orabpel:part>
    </orabpel:post>
    </orabpel:deliveryService>
    </orabpel:locator>
    <b>We also tried this way...same result</b>
    Properties jndi = new Properties();
    jndi.put(Context.PROVIDER_URL,"ormi://localhost:23791/orabpel");
    jndi.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
    jndi.put(Context.SECURITY_PRINCIPAL, "admin");
    jndi.put(Context.SECURITY_CREDENTIALS, "welcome");
    jndi.put("dedicated.connection", "true");
    String xml = "....";
    NormalizedMessage input = new NormalizedMessage( );
    input.addPart("payload", xml);
    String conversationId = String.valueOf(System.currentTimeMillis());
    input.setProperty(NormalizedMessage.TITLE, "Dynamic CustomerRegistration Invocation");
    input.setProperty(NormalizedMessage.CONVERSATION_ID, conversationId);
    input.setProperty(NormalizedMessage.CREATOR, "Oracle BPEL");
    Locator locator = new Locator("default","bpel",jndi);
    IDeliveryService deliveryService = (IDeliveryService)locator.lookupService(IDeliveryService.SERVICE_NAME);
    deliveryService.post("ProductRegistration", "initiate", input );
    <b>The entry in application.xml for the web application is as follows:</b><br/>
    <web-module id="registration" path="../../home/applications/registration.war"/>
    The entry in http-web-site.xml for the web application is as follows:<br/>
    <web-app application="orabpel" name="registration" load-on-startup="true" root="/registration"/>
    <web-app application="default" name="registration"      root="/registration"/>
    I have tried to provide all possible relevant info, if you need more, do reply back to me.
    Thanks in advance for helping us to resolve this issue.
    |Soumen|

    We have a business process, which when invoked from BPEL console works fine, however, when we invoke it from an web application of ours, it does gets initiated, but fails later.
    We have Apache Axis deployed in the same OC4J server as the Oracle BPEL PM(10.1.2.0.2), which exposes few EJBs as SOAP Services.
    The Business Process invokes couple of SOAP Services and then creates a Task and then waits for task completion and based on task action invokes two other SOAP services.
    When we invoke it from the BPEL Console, everything works fine. It also works fine, if we invoke it first (after startup) from BPEL Console and then through our web application.
    However, if we invoke it first through our web application, then it does initiates, but fails at the Task creation. If we try to hit the BPEL Console, we get this error
    Oracle BPEL Process Manager Full Cycle
    An unexpected error has occurred while executing your request. This is most likely related to a defect in the Oracle BPEL Process Manager product. We apologize you can post the error to the OTN forum and we will get back to you as soon as possible.
    Attachments:
    Build Information:
    Oracle BPEL Server version 10.1.2.0.2
    Build: 2196
    Build time: Tue Jan 10 12:31:53 UTC 2006
    Build type: release
    Source tag: BPEL_10.1.2.0.2_GENERIC_060110.1200
    Exception Message:
    [java.lang.Exception]
    Failed to create "ejb/collaxa/system/ServerBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/collaxa/system/ServerBean not found
         at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:164)
         at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:333)
         at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:120)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
    <b>Nothing works after that, unless we re-start.</b>
    Once we re-start, BPEL Console works fine.
    Investigating the flow of the business process, we find the "initiateTask" of the workflow is fine, but it failed at "initiateTaskActionHandler" with the following error:
    <remoteFault>
    <part name="code" >
    <code>WSDLReadingError</code>
    </part>
    <part name="summary" >
    <summary>Failed to read wsdl. Failed to read wsdl at "http://Uranus:9700/orabpel/default/TaskActionHandler/TaskActionHandler?wsdl", because "WSDLException: faultCode=INVALID_WSDL: The document: http://Uranus:9700/orabpel/default/TaskActionHandler/TaskActionHandler?wsdl is not a wsdl file or does not have a root element of "definitions" in the "http://schemas.xmlsoap.org/wsdl/" namespace or the "http://www.w3.org/2004/08/wsdl" namespace.". Make sure wsdl is valid. You may need to start the OraBPEL server, or make sure the related bpel process is deployed correctly. </summary>
    </part>
    </remoteFault>
    <b>Below is the code as to how we are invoking the Business Process...using orabpel taglibs...</b>
    <orabpel:locator domainId="default" password="bpel" contextEnv="jndi">
    <orabpel:deliveryService processId="ApprovalProcess">
    <orabpel:post title="ApprovalProcess">
    <orabpel:part name="payload">
    <customerObj xmlns="http://xmlns.misys.com/ApprovalProcess/approval">
    <applicationNo><%= customer.getApplicationNo() %></applicationNo>
    <customerId><%= customer.getCustomerId() %></customerId>
    <primaryFirstName><%= customer.getPrimaryFirstName() %></primaryFirstName>
    <primaryLastName><%= customer.getPrimaryLastName() %></primaryLastName>
    <primaryCardName><%= customer.getPrimaryCardName() %></primaryCardName>
    <primaryDay><%= customer.getPrimaryDay() %></primaryDay>
    <primaryMonth><%= customer.getPrimaryMonth() %></primaryMonth>
    <primaryYear><%= customer.getPrimaryYear() %></primaryYear>
    <primaryDob><%= customer.getPrimaryDob() %></primaryDob>
    <primarySex><%= customer.getPrimarySex() %></primarySex>
    <primaryPanNo><%= customer.getPrimaryPanNo() %></primaryPanNo>
    <accountType><%= customer.getAccountType() %></accountType>
    <cardType><%= customer.getCardType() %></cardType>
    <primaryStreet1><%= customer.getPrimaryStreet1() %></primaryStreet1>
    <primaryStreet2><%= customer.getPrimaryStreet2() %></primaryStreet2>
    <primaryLandmark><%= customer.getPrimaryLandmark() %></primaryLandmark>
    <primaryCity><%= customer.getPrimaryCity() %></primaryCity>
    <primaryState><%= customer.getPrimaryState() %></primaryState>
    <primaryCountry><%= customer.getPrimaryCountry() %></primaryCountry>
    <primaryPinCode><%= customer.getPrimaryPinCode() %></primaryPinCode>
    <primaryOffPhoneNo><%= customer.getPrimaryOffPhoneNo() %></primaryOffPhoneNo>
    <primaryOffExtnNo><%= customer.getPrimaryOffExtnNo() %></primaryOffExtnNo>
    <primaryResPhoneNo><%= customer.getPrimaryResPhoneNo() %></primaryResPhoneNo>
    <primaryMobileNo><%= customer.getPrimaryMobileNo() %></primaryMobileNo>
    <primaryEmailId><%= customer.getPrimaryEmailId() %></primaryEmailId>
    <productInterest><%= customer.getProductInterest() %></productInterest>
    <sourceReferral><%= customer.getSourceReferral() %></sourceReferral>
    <channel><%= customer.getChannel() %></channel>
    <accountNo><%= " " %></accountNo>
    <documentsSubmitted><%= customer.getDocumentsSubmitted() %></documentsSubmitted>
    <creditRating><%= 0.0 %></creditRating>
    <eligibleCustomer><%= false %></eligibleCustomer>
    <segment><%= " " %></segment>
    <action><%= " " %></action>
    <remarks><%= " " %></remarks>
    <approverEmail><%= customer.getApproverEmail() %></approverEmail>
    <bPELProviderUrl><%= customer.getBPELProviderUrl() %></bPELProviderUrl>
    </customerObj>
    </orabpel:part>
    </orabpel:post>
    </orabpel:deliveryService>
    </orabpel:locator>
    <b>We also tried this way...same result</b>
    Properties jndi = new Properties();
    jndi.put(Context.PROVIDER_URL,"ormi://localhost:23791/orabpel");
    jndi.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
    jndi.put(Context.SECURITY_PRINCIPAL, "admin");
    jndi.put(Context.SECURITY_CREDENTIALS, "welcome");
    jndi.put("dedicated.connection", "true");
    String xml = "....";
    NormalizedMessage input = new NormalizedMessage( );
    input.addPart("payload", xml);
    String conversationId = String.valueOf(System.currentTimeMillis());
    input.setProperty(NormalizedMessage.TITLE, "Dynamic CustomerRegistration Invocation");
    input.setProperty(NormalizedMessage.CONVERSATION_ID, conversationId);
    input.setProperty(NormalizedMessage.CREATOR, "Oracle BPEL");
    Locator locator = new Locator("default","bpel",jndi);
    IDeliveryService deliveryService = (IDeliveryService)locator.lookupService(IDeliveryService.SERVICE_NAME);
    deliveryService.post("ProductRegistration", "initiate", input );
    <b>The entry in application.xml for the web application is as follows:</b><br/>
    <web-module id="registration" path="../../home/applications/registration.war"/>
    The entry in http-web-site.xml for the web application is as follows:<br/>
    <web-app application="orabpel" name="registration" load-on-startup="true" root="/registration"/>
    <web-app application="default" name="registration"      root="/registration"/>
    I have tried to provide all possible relevant info, if you need more, do reply back to me.
    Thanks in advance for helping us to resolve this issue.
    |Soumen|

  • How to change a Async BPEL process into Sync bpel process

    Hi All,
    Can we change a bpel process which has been created by choosing the template as Asynchronous BPEL Process and after my requirement has
    been changed i want to change my bpel process into synchronous bpel process. Is it possible to change the process or else we have to delete the whole process and once again we have to create a bpel process with synchronous template.
    IF it possible to change the process from Async to sync how. is there any demo link on this. If possibel can anyone share a link on this.
    Regards,
    CH

    Diff between ASYNC & SYNC
    Composite.xml
    SYNC: In service part in only interface.wsdl & binding.ws will be there
    ASYNC: in service part interface.wsdl & binding.ws and one more callback binding.ws is there.
    In .BPEL FILE
    SYNC: In Partner Link name, partnerLinkType, MyRole will be there .
    ASYNC: In partner Link name ,partnerLinkType,MyRole,Partner Role also will be there.
    *.WSDL File*
    SYNC: in portType Input & Output both are there , in partnerLinkType only one role is there i.e Requester Role no provider.
    ASYNC: in portType only Input will there,in PartnerLinkType two roles will be there ProviderRole n Requester Role.
    Also change the activity in the BPEL from Reply to Invoke in the end.
    Respective to your requirements you can change your BPEL to Sync/ASync.
    I hope it will help.

  • Correlation without correlation initiate in receive

    Hello all,
    I am writing a process which is waiting for at a receive activity. The problem is that the I need to correlate the input message with the current executing process.
    1. Say there is a process which has a receive activity which initiates the process
    2. Then it waits at receive activity. The receive activity will contain an ID used for correlation probably the instance id of the process.
    3. reply.
    The correlation has to be initiated before step 2. But the instance id is not the part of the input, where can I initiate the correlation.
    The correlation is usually correlated in the receive activity or the invoke where the variable is available. Please suggest how can this be achieved.
    Regards,

    HI
    Yes u r right sashwat, u must initiate the correlation before the receive activity and in recevice use the correlation initiate as false.
    you can use any field element of your payload to initiate the corelation and u must check this value should not be change and unique also.
    bye bye

  • Unable to invoke an asynch Oracle BPEL process

    Im currently struggling to invoke an Oracle BPEL web service from another Oracle BPEL process.
    When creating the invoking process I pasted in the wsdl from the BPEL console to describe the invoked process rather than use the original wsdl generated by the tool.
    The wsdl is given below :
    At run time execution fails at the point where the invoking BPEL web service calls the first BPEL process, the error is a binding fault with desc : unable to find available port.
    <?xml version="1.0" encoding="UTF-8" ?>
    - <definitions name="Supplier" targetNamespace="http://xmlns.oracle.com/Supplier" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://xmlns.oracle.com/Supplier" xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:client="http://xmlns.oracle.com/Supplier">
    - <types>
    - <schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/Supplier" xmlns="http://www.w3.org/2001/XMLSchema">
    - <element name="SupplierProcessRequest">
    - <complexType>
    - <sequence>
    <element name="input" type="string" />
    </sequence>
    </complexType>
    </element>
    - <element name="SupplierProcessResponse">
    - <complexType>
    - <sequence>
    <element name="result" type="string" />
    </sequence>
    </complexType>
    </element>
    </schema>
    - <schema xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://pc1520952:9700/orabpel/xmllib/ws-addressing.xsd" />
    </schema>
    </types>
    - <message name="ReplyToHeader">
    <part name="ReplyTo" element="wsa:ReplyTo" />
    </message>
    - <message name="MessageIDHeader">
    <part name="MessageID" element="wsa:MessageID" />
    </message>
    - <message name="SupplierRequestMessage">
    <part name="payload" element="tns:SupplierProcessRequest" />
    </message>
    - <message name="SupplierResponseMessage">
    <part name="payload" element="tns:SupplierProcessResponse" />
    </message>
    - <message name="RelatesToHeader">
    <part name="RelatesTo" element="wsa:RelatesTo" />
    </message>
    - <portType name="Supplier">
    - <operation name="initiate">
    <input message="tns:SupplierRequestMessage" />
    </operation>
    </portType>
    - <portType name="SupplierCallback">
    - <operation name="onResult">
    <input message="tns:SupplierResponseMessage" />
    </operation>
    </portType>
    - <binding name="SupplierCallbackBinding" type="tns:SupplierCallback">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    - <operation name="onResult">
    <soap:operation style="document" soapAction="onResult" />
    - <input>
    <soap:header message="tns:RelatesToHeader" part="RelatesTo" use="literal" encodingStyle="" />
    <soap:body use="literal" />
    </input>
    </operation>
    </binding>
    - <binding name="SupplierBinding" type="tns:Supplier">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    - <operation name="initiate">
    <soap:operation style="document" soapAction="initiate" />
    - <input>
    <soap:header message="tns:ReplyToHeader" part="ReplyTo" use="literal" encodingStyle="" />
    <soap:header message="tns:MessageIDHeader" part="MessageID" use="literal" encodingStyle="" />
    <soap:body use="literal" />
    </input>
    </operation>
    </binding>
    - <service name="Supplier">
    - <port name="SupplierPort" binding="tns:SupplierBinding">
    <soap:address location="http://pc1520952:9700/orabpel/default/Supplier/1.0" />
    </port>
    </service>
    - <service name="SupplierCallbackService">
    - <port name="SupplierCallbackPort" binding="tns:SupplierCallbackBinding">
    <soap:address location="http://set.by.caller" />
    </port>
    </service>
    - <plnk:partnerLinkType name="Supplier">
    - <plnk:role name="SupplierRequester">
    <plnk:portType name="tns:SupplierCallback" />
    </plnk:role>
    - <plnk:role name="SupplierProvider">
    <plnk:portType name="tns:Supplier" />
    </plnk:role>
    </plnk:partnerLinkType>
    </definitions>

    I have got the same error.
    and if you look at your wsdl generated in xmlSpy(or something to check xml),
    you will see that the xml is not Valid!!!!
    Here is the fault by no targetNameSpace is in it(like in the first schema)
    <schema xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://pc1520952:9700/orabpel/xmllib/ws-addressing.xsd" />
    </schema>
    This error is generated when trying to invoke a asynchronous BPEL deploy before in the engine.
    Error can be comprehensive is the Wsdl is not valid...
    When I deploy a asynchronous BPEL workflow in BPEL workflow 10.1.2, the compiler add <import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://$server-url$:9700/orabpel/xmllib/ws-addressing.xsd" />
    in the wsdl and is not valid.
    Anyone from the BPEL team know this , and find a solution???
    Thanks.

  • Extending ASYNC BPEL EXECUTION TIME

    Hi,
    I have a Async BPEL process that is calling same webservice several times and each invocation to that webservice results in wait time of 45 secs. so when i invoke the webservices as a partner link from BPEL, the service works fine till first 6 invocations but in case i increase my number of invocations to more than 6, my service moves in BPEL Message Recovery.
    What changes should i make in BPEL properties in order to make my BPEL process run for more than 6 invocations. I tried to change few properties in Soa Infra>Bpel Properties>More BPEL configurations and changed below properties :
    Sync Max wait Time : initially it was 240, i changed to 500
    Also, under recovery Config but the service is still going in reovery.
    How can i make my Aync BPEL process run for more duration without entering in Recovery Mode.
    Ideally, my service executed well for time duration starting 04:06:16 and ended at 04:10:48. If i add one more execution making it wait for another 45 sec, it moves in recovery.
    Please help.
    Thanks.

    Can you let us know the exact version of Server with patch details?

  • Invoking ODI Scenario from BPEL

    Hi,
    I tried invoking a scenario from BPEL. I started the agent before invoking the scenario. However I am getting the following error in the Agent
    java.lang.NullPointerException
    at com.sunopsis.dwg.dbobj.SnpScen.getObjectLst(SnpScen.java)
    at com.sunopsis.dwg.dbobj.SnpScen.getScenarionByCodeAndVersion(SnpScen.java)
    at com.sunopsis.dwg.cmd.DwgCommandScenario.b(DwgCommandScenario.java)
    at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)
    at com.sunopsis.dwg.cmd.DwgCommandBase.prepare(DwgCommandBase.java)
    at com.sunopsis.dwg.cmd.e.t(e.java)
    at com.sunopsis.dwg.cmd.h.y(h.java)
    at com.sunopsis.dwg.cmd.e.run(e.java)
    at java.lang.Thread.run(Thread.java:595)
    java.lang.NullPointerException
    at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)
    at com.sunopsis.dwg.cmd.DwgCommandBase.prepare(DwgCommandBase.java)
    at com.sunopsis.dwg.cmd.e.t(e.java)
    at com.sunopsis.dwg.cmd.h.y(h.java)
    at com.sunopsis.dwg.cmd.e.run(e.java)
    at java.lang.Thread.run(Thread.java:595)
    And i am getting the following error in BPEL Console
    <remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; charset=iso-8859-1</summary>
    </part></remoteFault>
    I am not able to solve the issue. Request you all to help
    Thanks and Regards.
    Edited by: user10714505 on May 12, 2009 11:06 PM

    Hi,
    Thanks its working now. I am facing another issue. I do not use parameters in my Scenario. Now when i run my scenario i m getting the following error. I think its because i have not assigned anything to the Variable element. I guess its taking null value for Variable element here and cheking if such a variable exists. Have you come accross such an issue? If so, please sugest remedy.
    java.lang.Exception: Specified variable not found in the Repository : null
         at com.sunopsis.dwg.dbobj.SnpSession.a(SnpSession.java)
         at com.sunopsis.dwg.dbobj.SnpSession.y(SnpSession.java)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSessionPreTrt(SnpSession.java)
         at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
         at com.sunopsis.dwg.cmd.DwgCommandScenario.treatCommand(DwgCommandScenario.java)
         at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
         at com.sunopsis.dwg.cmd.e.i(e.java)
         at com.sunopsis.dwg.cmd.h.y(h.java)
         at com.sunopsis.dwg.cmd.e.run(e.java)
         at java.lang.Thread.run(Thread.java:619)
    Edited by: silas.john on May 13, 2009 1:29 AM

  • How to deploy my own web services to the Start BPEL PM Server?

    Recently, I am learning the JDeveloper BPEL Designer(version 10.1.2.0), I had finished my first BPEL process CreditFlow flowing the quickstart guider.
    Now I wonder how to deploy my own web services to the Start BPEL PM Server? I mean I don't want to invoke the CreditRatingService as I did flowing the quickstart guider, but to invoke my own web servcies. Now I had made some web services with eclipse and deployed them to the tomcat5.0. but how can I invoke these my own web services just like I invoked the CreditRatingService in the JDeveloper BPEL Designer?
    Thank you!

    Copy the WSDL file from your Tomcat server onto your development machine. Add them to your project in JDeveloper. Then add a partnerlink and specify the WSDL location. Then add you role, variables and compile!

  • How to invoke WADL files from BPEL?

    Hi,
    I have an urgent requirement of invoking WADL files from BPEL process.
    Can anybody help me on how to do it and provide some documentation on it.
    Thanks in advance!!

    We had a similar requirement, BPEL calls the stored procedure, it calls the custom job created in Oracle EBS, this job runs the command script
    Hope this helps,
    N

Maybe you are looking for

  • Creating a new environment in UDS 5.2

    Hi there, I am wondering if someone can help us with this problem: We are installing UDS 5.2 on Solaris 8. After the installation when we try to create a new environment, we get the environment status as INDETERMINABLE. Any new component than added t

  • Webhelp display in Firefox does not use stylesheet.

    I have created a Webhelp system using Robohelp, single-sourced from FrameMaker. I have a custom stylesheet (CSS) file that I am deploying with the Webhelp. On IE and Chrome, the stylesheet is used. On Firefox, it is not. Does anyone know why this mig

  • Why is Adobe Captivate Chat support closed?

    It's 11:05 Am on Monday.  Here's what the Chat link says, Open "Sunday 6pm-Friday 7pm PT Chat is currently closed".  Time to wake up Adobe!

  • Searching an Index:  Adobe Reader 8.1 has encountered a problem - Crash

    We've just upgrade to Adobe Reader 8.1.2 here and now whenever we "Use Advanced Search Options","Look in", "Select Index", and search for words, Reader crashes. This has been reproduced on multiple PC's running Reader 8.1.2. Error Signature: AppName:

  • I have installed LR 6 for windows (win7) and LR will not start but hangs up

    I have installed LR 6 for windows (win7) and LR will not start but hangs up. I have uninstalled the software and re-installed it, Tried to open it as Administrator and it still hangs up with the Adobe banner (the picture) being displayed. Nothing hap