CorrelationSet in bpel

hi,
i have set correlation set in bpel but when iam excuting the process, the properties value of correlationSet in correlationSets is becomming " " and the final result of the process after excution is failing .
what is the error here.. why this is happening? plz some one help me..
Message was edited by:
suja

It is hard to comment on what happened without knowing any more details of your BPEL and WSDL files.
I assume that the query that you mentioned in the property alias for the property you are looking at resulted in a node that has " " (empty value). Did you use NB bpel editor to build the correlatins based BPEL. If so i would doubt any user errors. So you should check your message files and the queries of your property aliases.
One more thing, you mentioned some error, what is it?

Similar Messages

  • How to define callback in conversation webservice on WLS

    Hello,
    I have a very simple Conversation WS (source included) for WebLogic and I like to use it in BPEL process. But BPEL Designer does not recognize callback method. I can see callback method as standard WS operation for synchronous call. Please help me. When I use this WS in WLI (Web Logic Integration Server) everything is ok.
    Thank you for your help.
    JMELICHN
    --- Code of WS: --------------------------------------
    package ws;
    public class SimpleAsynchrWS implements com.bea.jws.WebService
    * @common:control
    * @jc:timer timeout="10 s"
    private com.bea.control.TimerControl timer;
    public Callback callback;
    static final long serialVersionUID = 1L;
    private String internal = "";
    * @common:operation
    * @jws:conversation phase="start"
    public void setString(String text)
    this.internal = text;
    this.timer.start();
    return;
    public interface Callback extends com.bea.control.ServiceControl
    * @jws:conversation phase="finish"
    void textCallback(String text);
    public void timer_onTimeout(long time)
    callback.textCallback(internal);
    timer.stop();

    I'm allmost sure that they are using SOAP converation. I attached WSDL generated for my service:
    <?xml version="1.0" encoding="utf-8" ?>
    - <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:conv="http://www.openuri.org/2002/04/soap/conversation/" xmlns:cw="http://www.openuri.org/2002/04/wsdl/conversation/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:jms="http://www.openuri.org/2002/04/wsdl/jms/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:s0="http://www.openuri.org/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="http://www.openuri.org/">
    - <types>
    - <s:schema xmlns:s="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://www.openuri.org/">
    - <s:element name="setString">
    - <s:complexType>
    - <s:sequence>
    <s:element name="text" type="s:string" minOccurs="0" />
    </s:sequence>
    </s:complexType>
    </s:element>
    - <s:element name="setStringResponse">
    - <s:complexType>
    <s:sequence />
    </s:complexType>
    </s:element>
    - <s:element name="textCallbackResponse">
    - <s:complexType>
    <s:sequence />
    </s:complexType>
    </s:element>
    - <s:element name="textCallback">
    - <s:complexType>
    - <s:sequence>
    <s:element name="text" type="s:string" minOccurs="0" />
    </s:sequence>
    </s:complexType>
    </s:element>
    </s:schema>
    - <s:schema elementFormDefault="qualified" targetNamespace="http://www.openuri.org/2002/04/soap/conversation/">
    <s:element name="StartHeader" type="conv:StartHeader" />
    <s:element name="ContinueHeader" type="conv:ContinueHeader" />
    <s:element name="CallbackHeader" type="conv:CallbackHeader" />
    - <s:complexType name="StartHeader">
    - <s:sequence>
    <s:element minOccurs="0" maxOccurs="1" name="conversationID" type="s:string" />
    <s:element minOccurs="0" maxOccurs="1" name="callbackLocation" type="s:string" />
    </s:sequence>
    </s:complexType>
    - <s:complexType name="ContinueHeader">
    - <s:sequence>
    <s:element minOccurs="1" maxOccurs="1" name="conversationID" type="s:string" />
    </s:sequence>
    </s:complexType>
    - <s:complexType name="CallbackHeader">
    - <s:sequence>
    <s:element minOccurs="1" maxOccurs="1" name="conversationID" type="s:string" />
    </s:sequence>
    </s:complexType>
    </s:schema>
    </types>
    - <message name="setStringSoapIn">
    <part name="parameters" element="s0:setString" />
    </message>
    - <message name="setStringSoapOut">
    <part name="parameters" element="s0:setStringResponse" />
    </message>
    - <message name="textCallbackSoapIn">
    <part name="parameters" element="s0:textCallbackResponse" />
    </message>
    - <message name="textCallbackSoapOut">
    <part name="parameters" element="s0:textCallback" />
    </message>
    - <message name="setStringHttpGetIn">
    <part name="text" type="s:string" />
    </message>
    <message name="setStringHttpGetOut" />
    <message name="textCallbackHttpGetIn" />
    - <message name="textCallbackHttpGetOut">
    <part name="text" type="s:string" />
    </message>
    - <message name="setStringHttpPostIn">
    <part name="text" type="s:string" />
    </message>
    <message name="setStringHttpPostOut" />
    <message name="textCallbackHttpPostIn" />
    - <message name="textCallbackHttpPostOut">
    <part name="text" type="s:string" />
    </message>
    - <message name="StartHeader_literal">
    <part name="StartHeader" element="conv:StartHeader" />
    </message>
    - <message name="CallbackHeader_literal">
    <part name="CallbackHeader" element="conv:CallbackHeader" />
    </message>
    - <portType name="SimpleAsynchrWSSoap">
    - <operation name="setString">
    <input message="s0:setStringSoapIn" />
    <output message="s0:setStringSoapOut" />
    </operation>
    - <operation name="textCallback">
    <output message="s0:textCallbackSoapOut" />
    <input message="s0:textCallbackSoapIn" />
    </operation>
    </portType>
    - <portType name="SimpleAsynchrWSHttpGet">
    - <operation name="setString">
    <input message="s0:setStringHttpGetIn" />
    <output message="s0:setStringHttpGetOut" />
    </operation>
    - <operation name="textCallback">
    <output message="s0:textCallbackHttpGetOut" />
    <input message="s0:textCallbackHttpGetIn" />
    </operation>
    </portType>
    - <portType name="SimpleAsynchrWSHttpPost">
    - <operation name="setString">
    <input message="s0:setStringHttpPostIn" />
    <output message="s0:setStringHttpPostOut" />
    </operation>
    - <operation name="textCallback">
    <output message="s0:textCallbackHttpPostOut" />
    <input message="s0:textCallbackHttpPostIn" />
    </operation>
    </portType>
    - <binding name="SimpleAsynchrWSSoap" type="s0:SimpleAsynchrWSSoap">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
    - <operation name="setString">
    <soap:operation soapAction="http://www.openuri.org/setString" style="document" />
    <cw:transition phase="start" />
    - <input>
    <soap:body use="literal" />
    <soap:header xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" wsdl:required="true" message="s0:StartHeader_literal" part="StartHeader" use="literal" />
    </input>
    - <output>
    <soap:body use="literal" />
    </output>
    </operation>
    - <operation name="textCallback">
    <soap:operation soapAction="http://www.openuri.org/textCallback" style="document" />
    <cw:transition phase="finish" />
    - <input>
    <soap:body use="literal" />
    </input>
    - <output>
    <soap:body use="literal" />
    <soap:header xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" wsdl:required="true" message="s0:CallbackHeader_literal" part="CallbackHeader" use="literal" />
    </output>
    </operation>
    </binding>
    - <binding name="SimpleAsynchrWSHttpGet" type="s0:SimpleAsynchrWSHttpGet">
    <http:binding verb="GET" />
    - <operation name="setString">
    <http:operation location="/setString" />
    <cw:transition phase="start" />
    - <input>
    <http:urlEncoded />
    </input>
    <output />
    </operation>
    - <operation name="textCallback">
    <http:operation location="/textCallback" />
    <cw:transition phase="finish" />
    - <input>
    <mime:mimeXml part="Body" />
    </input>
    - <output>
    <http:urlEncoded />
    </output>
    </operation>
    </binding>
    - <binding name="SimpleAsynchrWSHttpPost" type="s0:SimpleAsynchrWSHttpPost">
    <http:binding verb="POST" />
    - <operation name="setString">
    <http:operation location="/setString" />
    <cw:transition phase="start" />
    - <input>
    <mime:content type="application/x-www-form-urlencoded" />
    </input>
    <output />
    </operation>
    - <operation name="textCallback">
    <http:operation location="/textCallback" />
    <cw:transition phase="finish" />
    - <input>
    <mime:mimeXml part="Body" />
    </input>
    - <output>
    <mime:content type="application/x-www-form-urlencoded" />
    </output>
    </operation>
    </binding>
    - <service name="SimpleAsynchrWS">
    - <port name="SimpleAsynchrWSSoap" binding="s0:SimpleAsynchrWSSoap">
    <soap:address location="http://ntb22:7001/eShopWs/ws/SimpleAsynchrWS.jws" />
    </port>
    - <port name="SimpleAsynchrWSHttpGet" binding="s0:SimpleAsynchrWSHttpGet">
    <http:address location="http://ntb22:7001/eShopWs/ws/SimpleAsynchrWS.jws" />
    </port>
    - <port name="SimpleAsynchrWSHttpPost" binding="s0:SimpleAsynchrWSHttpPost">
    <http:address location="http://ntb22:7001/eShopWs/ws/SimpleAsynchrWS.jws" />
    </port>
    </service>
    </definitions>
    I'd like to try definition of explicite correlationSet in BPEL, but i think that callback must be recognized.
    Thnak you for yor attention.
    JMELICHN

  • Regression

    Hi all,
    is there a regression about the Correlation Set in the latest version of the Process Manager?
    I tryed it with PM 2.0.11 and it works fine.
    While in PM 2.1.2 it doesn't work properly.
    In order to use the Correlation set I've just to set the
    attribute useCorrelationSet to "yes" and put the <propetry name="correlation">correlationSet</property> into the partner I want to communicate with.
    Please, read the example below: I'd use the Correlation Set feature only with the partnerLink "aService".
    <?xml version="1.0"?>
    <BPELSuitcase>
         <BPELProcess useCorrelationSet="yes" id="LoanFlowAV3" src="LoanFlowAV3.bpel">
              <partnerLinkBindings>
                   <partnerLinkBinding name="client">
                        <property name="wsdlLocation">LoanFlowAV3.wsdl</property>
                   </partnerLinkBinding>
                   <partnerLinkBinding name="creditRatingService">
                        <property name="wsdlLocation">http://localhost:9700/orabpel/default/CreditRatingService/CreditRatingService?wsdl</property>
                   </partnerLinkBinding>
                   <partnerLinkBinding name="InfoService">
                        <property name="wsdlLocation">http://localhost:9700/orabpel/default/InfoService/InfoService?wsdl</property>
                   </partnerLinkBinding>
                   <partnerLinkBinding name="aService">
              <property name="correlation">correlationSet</property>
                        <property name="wsdlLocation">LoanService.wsdl</property>
                   </partnerLinkBinding>
              </partnerLinkBindings>
         </BPELProcess>
    </BPELSuitcase>
    Please help me! I found a workflow where the Correlation ID is weak, and it is necessary to use BPEL4WS Correlation Sets.
    Thanks in advance

    Hi Marcello:
    Please check out orabpel/samples/tutorials/109.CorrelationSets/Seller/bpel.xml
    In it you have the following property in the service partnerLinkBinding:
    <property name="correlation">correlationSet</property>
    This tells the compiler don't generate the WS-Addressing
    header for this service.
    At client side (check out 109.CorrelationSets/Seller), you
    don't need to do any special setting.
    regards,
    - glenn

  • CorrelationSet error while invoking Bpel from a java appli

    Hi There,
    I'm trying to send a signal from a java application to a bpel process (already instanciated before) and I get the following error :
    [Erreur ORABPEL-10015] : propriété de corrélation non résolue
    [Description] : à la ligne 25 de "/oracle/product/10.1.2/.../myProjectConvertPdf.bpel", la propriété de corrélation "{http://xmlns.oracle.com/myProjectConvertPdf/correlationset}filename" du correlationSet "CorrelationSet_signalConvOk" n'est pas définie.
    [Solution potentielle] : assurez-vous que la propriété "{http://xmlns.oracle.com/myProjectConvertPdf/correlationset}filename" est définie dans l'un des fichiers WSDL référencés.
    My java application is designed to get the value of the correlation parameter from another source (the bpel process calls a webservice a webservice in another virtual machine and transmits the parameter value by a database table or a file)
    My file .bpel contains :
    <receive name="Receive_signalConvOk" partnerLink="signalConvPdfOk" portType="client:projectSignal" operation="receiveSignal" variable="Receive_signalConvOk_receiveSignal" createInstance="no">
    <correlations>
    <correlation initiate="no" set="CorrelationSet_signalConvOk"/>
    </correlations>
    </receive>
    the correlation is defined as followed :
    <correlationSets>
    <correlationSet name="CorrelationSet_signalConvOk" properties="ns1:filename"/>
    </correlationSets>
    and the property alias :
    <definitions
    name="properties"
    targetNamespace="http://xmlns.oracle.com/myProjectConvertPdf/correlationset"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    >
    <bpws:property name="filename" type="xsd:string"/>
    </definitions>
    My java appli calls the bpel process by the following code :
    String xml = "<filename xmlns=\"http://xmlns.oracle.com/myProjectConvertPdf\">"+parameterValue+"</filename>\n";
    NormalizedMessage nm = new NormalizedMessage( );
    nm.addPart("payload", xml );
    deliveryService.post(nomProcessBpel,
    null,
    "signalConvPdfOk",
    null,
    nomOpBpel,
    nm);
    My first problem is obviousy the error message and my second problem is that I don't know how to transmit the correlation parameter in the request my java appli does to the bpel process.
    Thanks in advance for your help

    Hi,
    Refer below thread and links for more information. Hope this should help you guys.
    ESB Not allowing to call Secured Service
    Regards

  • [Patch 정보] TRACKING BUG FOR CUMULATIVE MLR#6 ON TOP OF BPEL PM 10.1.3.3.1

    최근에 출시된 BPEL PM 10.1.3.3.1의 통합패치입니다.
    아래는 readme.txt에 포함된 patch list입니다.
    # WARNING: Failure to carefully read and understand these requirements may
    # result in your applying a patch that can cause your Oracle Server to
    # malfunction, including interruption of service and/or loss of data.
    # If you do not meet all of the following requirements, please log an
    # iTAR, so that an Oracle Support Analyst may review your situation. The
    # Oracle analyst will help you determine if this patch is suitable for you
    # to apply to your system. We recommend that you avoid applying any
    # temporary patch unless directed by an Oracle Support Analyst who has
    # reviewed your system and determined that it is applicable.
    # Requirements:
    # - You must have located this patch via a Bug Database entry
    # and have the exact symptoms described in the bug entry.
    # - Your system configuration (Oracle Server version and patch
    # level, OS Version) must exactly match those in the bug
    # database entry - You must have NO OTHER PATCHES installed on
    # your Oracle Server since the latest patch set (or base release
    # x.y.z if you have no patch sets installed).
    # - [Oracle 9.0.4.1 & above] You must have Perl 5.00503 (or later)
    # installed under the ORACLE_HOME, or elsewhere within the host
    # environment.
    # Refer to the following link for details on Perl and OPatch:
    # http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=189489.1
    # If you do NOT meet these requirements, or are not certain that you meet
    # these requirements, please log an iTAR requesting assistance with this
    # patch and Support will make a determination about whether you should
    # apply this patch.
    # 10.1.3.3.1 Bundle Patch 6823628
    # DATE: March 14, 2008
    # Platform Patch for : Generic
    # Product Version # : 10.1.3.3.1
    # Product Patched : Oracle(R) SOA
    # Bugs Fixed by 10.1.3.3.1 Initial patch 6492514 :
    # Bug 5473225 - PATCH01GENESIS HOT UNABLE TO CATCH AN EXCEPTION DURING A
    # TRANSFORM
    # Bug 5699423 - PARTNERLINK PROPERTY THAT SET BPELXPROPERTY FUNCTION DOESN'T
    # WORK
    # Bug 5848272 - STATEFUL WEBSERVICES DEMO ON OTN DOES NOT WORK 10.1.3.1
    # Bug 5872799 - ANT DEPLOY BPEL TEST FAILS/RUNS ON DEFAULT DOMAIN NOT
    # SPECIFIED TARGET DOMAIN
    # Bug 5883401 - ALLOW A WAY TO CREATE EMPTY NODES - AND USE FOR REQUIRED
    # NODES
    # Bug 5919412 - SAMPLE DEMO BPEL PROCESSES MIMESERVICE MIMEREQUESTER AXIS
    # JAVA EXAMPLE ERROR
    # Bug 5924483 - ESB SHOULD SUPPORT SOAP EDNPOINT LOCATION DYNAMIC UDDI LOOKUP
    # Bug 5926809 - ORAPARSEESCAPEDXML XPATH EXPRESSION FAILED TO EXECUTE
    # FOTY0001 TYPE ERROR
    # Bug 5937320 - STRANGE BEHAVIOUR CALLING FROM BPEL TO BPEL GETTING
    # NULLPOINTEREXCEPTION.
    # Bug 5944641 - BPA BLUEPRINT NOT AVAIALBLE IN JDEVELOPER
    # Bug 5945059 - JAVA.LANG.NULLPOINTEREXCEPTION SENDING EMAILS WITH PAYLOADS
    # LARGER THAT 1MB
    # Bug 5962677 - WS RESPONSE IS EMPTY SOAP BODY IN ONE-WAY CALL
    # Bug 5963425 - WHEN THE OUTCOMES FOR A HT CHANGED & IMPORTED - UPDATE
    # CONNECTION ROLES IN BPEL
    # Bug 5964097 - AQ ADAPTER DEPLOYMENT CAUSES OPMN TO PERFORM A FORCEFUL
    # SHUTDOWN IN SOA
    # Bug 5971534 - CANNOT GRANT USER TASK VIEWS TO GROUPS, ONLY TO USERS.
    # Bug 5989367 - REFER TO SR 6252219.993 BPEL 10.1.3 ONLY COPIES IN ASSIGN,
    # IN 10.1.2 IT CREATES
    # Bug 5989527 - ENHANCEMENT WARNING SHOULD BE GIVEN UPON UPLOAD IF BPEL
    # PROCESS IS OPEN IN ARIS
    # Bug 5997936 - ESB FAULT DOES NOT GET PROPAGATED TO BPEL
    # Bug 6000575 - PERF NEED ESB PURGE SCRIPT TO PURGE BY DATE AND PROCESS
    # Bug 6001796 - POSTING OF DATE RECEIVED FROM XML GATEWAY TO BPEL FAILED IN
    # ESB
    # Bug 6005407 - BPEL PROCESS DOESN'T PROPOGATE FAULT THROWN BY BPEL
    # SUB-PROCESS
    # Bug 6017846 - MIMETYPE OF EMAIL NOTIFICATION IS NOT SET THROUGH HUMAN TASK
    # Bug 6027734 - DECISION SERVICE IMPORT - LOCATING DECISION SERVICE IN .DECS
    # FILE IMPROPER
    # Bug 6028985 - EXCEEDED MAXIMUM NUMBER OF SUBSCRIBERS FOR QUEUE
    # ORAESB.ESB_CONTROL
    # Bug 6041508 - CREATING/UPDATING DVM CAUSE EXCEPTION
    # Bug 6053708 - FTP ADAPTER DOES NOT SUPPORT ENCRYPTED PASSWORD IN
    # OC4J-RA.XML
    # Bug 6054034 - INDEX4,INDEX5 AND INDEX6 CANNOT BE USED IN BPEL CONSOLE
    # Bug 6068801 - BACKPORT OF BPEL ON WEBLOGIC - VERSION 10.1.3.3
    # Bug 6070991 - HT EXPORT DOES NOT EXPORT PARAMETERS, ALLOW PARTICIPANTS TO
    # INVITE OTHERS
    # Bug 6071001 - WSIF HTTP BINDING NOT WORKING FROM ESB
    # Bug 6073311 - STRESS SCOPE NOT FOUND ON CALLBACK - WRONG (DUPE)
    # SUBSCRIPTION IN TABLE
    # Bug 6081070 - JMS ADAPTER REJECTION HANDLER CREATE 0 BYTE FILES
    # Bug 6083419 - DECISION SERVICE SCOPE NEED TO HAVE A SPECIAL INDICATOR
    # Bug 6085799 - HUMAN TASK ADDED IN SCOPE IN JDEV IS NOT UPDATED TO BPA
    # SERVER
    # Bug 6085933 - EXPORT AND EXPLORE SHOULD USE USER LANGUAGE AND NOT ENGLISH
    # ALWAYS
    # Bug 6086281 - STRING INDEX OUT OF RANGE ERROR FOR COBOL COPYBOOK WITH PIC
    # CLAUSE HAVING S
    # Bug 6086453 - DOMAINS CREATED IN A CLUSTER GETS NOT PROPAGATED TO NEW OR
    # EXISTING NODES
    # Bug 6087484 - MULTIPLE HEADER SETTING CAUSES ESB EXCEPTION
    # Bug 6087645 - ESB SHOULD ALLOW USER PICK RUNTIME PROTOCOL (HTTP/HTTPS)
    # Bug 6110231 - TRANSLATION NOT BASED ON MQ CCSID CHARSET
    # Bug 6120226 - BPEL IS NOT SETTING THE APPS CONTEXT CORRECTLY
    # Bug 6120323 - COMPLETIONPERSISTPOLICY ON DOMAIN LEVEL HAS DISAPPEARED
    # Bug 6125184 - ESB JMS SESSION ROLLBACK ORACLE.JMS.AQJMSEXCEPTION
    # Bug 6127824 - [AIA2.0] CURRENT XREF IMPLEMENTATION IS MISSING REQUIRED
    # INDEXES ON XREF SCHEMA
    # Bug 6128247 - HTTPCONNECTOR POST() METHOD SHOULD RAISE EXCEPTION FOR ALL
    # STATUS CODES EXCEPT 2
    # Bug 6131159 - ENABLE USERS TO CHOOSE XSD WHEN CREATING A BPEL PROCESS FROM
    # BLUE PRINT
    # Bug 6132141 - PROCESS_DEFAULT TABLE STILL CONTAINS INFORMATION FROM
    # UNDEPLOYED PROCESSES
    # Bug 6133190 - ENABLING ESB CONSOLE HTTP/S IS MAKING THE CONSOLE TO COME UP
    # BLANK.
    # Bug 6139681 - BPEL WSDL LINK IN CLUSTERED RUNTIME POINTS TO A SINGLE NODE
    # Bug 6141259 - BASICHEADERS NOT PUTTING WWW-AUTHENTICATE HEADERS FOR HTTP
    # BINDING IN BPEL
    # Bug 6148021 - BPEL NATIVE SCHEMA FOR COBOL COPYBOOK WITH IMPLIED DECIMAL
    # LOSES DIGIT IN OUTPUT
    # Bug 6149672 - XOR DATA - CONDITION EXPRESSION SPECIFICATION IS NOT
    # INTUITIVE IN BPMN MODELS
    # Bug 6152830 - LOSING CONDITIONAL EXPRESSIONS CREATED IN JDEV UPON MERGE
    # Bug 6158128 - BASICHEADERS NOT PUTTING WWW-AUTHENTICATE HEADERS FOR HTTP
    # BINDING
    # Bug 6166991 - WHEN STARTING SOA SUITE,, PROCESSES FAIL DUE TO UNDEFINED
    # WSDL
    # Bug 6168226 - LOCATION-RESOLVER EXCEPTION THROWN IN OPMN LOGS
    # Bug 6187883 - CHANGES FOR BPEL RELEASE ON JBOSS- VERSION 10.1.3.3
    # Bug 6206148 - [AIA2.0] NEW FUNCTION REQUEST, XREFLOOKUPPOPULATEDCOLUMNS()
    # Bug 6210481 - BPEL PROCESS WORKS INCORRECTLY WHEN AN ACTIVITY HAS MULTIPLE
    # TRANSITIONCONDITION
    # Bug 6240028 - WEBSERVICE THAT DOES NOT CHALLENGE FOR BASIC CREDENTIALS
    # CANNOT BE INVOKED
    # Bug 6257116 - MULTIPLE HEADER SETTING CAUSES ESB EXCEPTION
    # Bug 6258925 - MESSAGE RECEIVED BY THE TARGET ENDPOINT VIA HTTP POST IS
    # MISSING THE XML HEADER
    # Bug 6259686 - TOO MANY UNNECESSARY WORKFLOW E-MAIL NOTIFICATIONS GENERATED
    # Bug 6267726 - 10.1.3.3 ORACLE APPLICATIONS ADAPTER - NOT ABLE TO CAPTURE
    # BUSINESS EVENT
    # Bug 6272427 - WEBSPHERE BPEL FAILS FOR DATA RETRIEVAL OF SIZE 500+ KB
    # Bug 6276995 - MERGE SCOPE NAME IS NOT UPDATED WHEN CHANGED IN THE SERVER
    # Bug 6280570 - XPATH EXPRESSION ERROR IN MEDIATOR FOR ASSIGNING USER-DEFINED
    # CONTEXT VALUES
    # Bug 6282339 - RETRYCOUNT DOES NOT WORK PROPERLY
    # Bug 6311039 - ONE RECORD IS INSERTED TO SYNC_STORE IF
    # COMPLETIONPERSISTPOLICY SET TO FAULTED
    # Bug 6311809 - [AIA2.0] NON-RETRYABLE ERRORS ARE NOT POSTED ON ESB_ERROR
    # TOPIC
    # Bug 6314784 - THE PRIORITY DEFINED IN THE BPA SUITE IS NOT TRANSFERRED TO
    # THE JDEV CORRECTLY
    # Bug 6314982 - THREADPOOL RACE CONDITION IN ADAPTER INITIALIZATION MESSAGES
    # NOT PROCESSED
    # Bug 6315104 - (SET)CLASSNAME MISSING IN TSENSOR JAXB OBJECTS
    # Bug 6316554 - CONSUME FUNCTIONALITY OF JMS ADAPTER FOR BEA WEBLOGIC DOES
    # NOT WORK
    # Bug 6316950 - FILEADAPTER HARPER ENHANCEMENTS SYNC WRITE AND CHUNKED
    # INTERACTION SPEC
    # Bug 6317398 - THE ICON FOR COMPUTING DIFFERENCE IS MISSING IN JDEV REFRESH
    # FROM SERVER DIALOG
    # Bug 6320506 - IMPORT FAILS WHEN THERE IS AN UNNAMED CASE
    # Bug 6321011 - CANNOT PROCESS 0 BYTE FILE USING FTP ADAPTER
    # Bug 6325749 - TRACKING BUG FOR TRACKING ADDITIONAL CHANGES TO BUG #6032044
    # Bug 6328584 - NEED A NEW XPATH EXPRESSION TO GET ATTACHMENT CONTENT VIA
    # SOAP INVOKATION
    # Bug 6333788 - COLLAPSING OF CONSECUTIVE ASSIGN TASKS BREAKS BAM SENSOR
    # Bug 6335773 - BUILD.XML CONTAINS DO NOT EDIT .. - WHILE <CUSTOMIZE> TASK
    # MUST BE IN <BPELC>
    # Bug 6335805 - AQ ADAPTER OUTBOUND DOESN'T RECONNECT AFTER FAILURE
    # Bug 6335822 - [AIA2.0] PSRPERFESB - RUNTIME DVM PERFORMANCE OVERHEAD IN ABS
    # USE CASE
    # Bug 6339126 - CHECKPOINT BPEL JAVA METHOD DOESN'T WORK IN BPEL 10.1.3.3
    # Bug 6342899 - OUTLINECHANGE.XML NOT UPDATE WITH ACTIVITY FROM NEW BRANCH
    # Bug 6343299 - ESB CONCRETE WSDL NAMESPACE SHOULD BE DIFFERENT FROM IMPORTED
    # WSDL NAMESPACE
    # Bug 6372741 - DEHYDRATION DATABASE KEEPS GROWING IN 10.1.3.3
    # Bug 6401295 - NXSD SHOULD SUPPORT ESCAPING THE TERMINATED/QUOTED/SURROUNDED
    # DELIMITERS
    # Bug 6458691 - DIST DIRECTORY FOR 10.1.3.3.1 NEEDS UPDATE
    # Bug 6461516 - BPEL CONSOLE CHANGES FOR DISPLAYING RELEASE 10.1.3.3.1
    # Bug 6470742 - CHANGE THE VERSION NUMBER AND BUILD INFO IN ABOUT DIALOG IN
    # ESB
    # BUG ADDED IN MLR#1, 6671813 :
    # Bug 6494921 - ORABPEL-02154 IF LONG DOMAIN AND SUITECASE NAMES IN USE
    # BUGS ADDED IN MLR#2, 6671831 :
    # Bug 6456519 - ERROR IN BPEL CONSOLE THREADS TAB:SERVLETEXCEPTION CANNOT GET
    # DISPATCHER TRACE
    # Bug 6354719 - WHICH JGROUP CONFIGURATION PARAMETER IMPACTS BPEL CLUSTER
    # ACTIVITY
    # Bug 6216169 - SCOPE NOT FOUND ERROR WHILE DELIVERING EXPIRATION MESSAGE OF
    # ONALARM
    # Bug 6395060 - ORA-01704 ON INSERTING A FAULTED INVOKE ACTIVITY_SENSOR
    # Bug 6501312 - DEHYDRATION DATABASE KEEPS GROWING IN 10.1.3.3 #2
    # Bug 6601020 - SEARCHBASE WHICH INCLUDES PARENTHESIS IN THE NAMES DOES NOT
    # WORK
    # Bug 6182023 - WAIT ACTIVITY FAILS TO CONTINUE IN CLUSTER WHEN PROCESSING
    # NODE GOES DOWN
    # BUGS ADDED IN MLR#3, 6723162 :
    # Bug 6725374 - INSTANCE NOT FOUND IN DATASOURCE
    # Bug 4964824 - TIMED OUT IF SET CORRELATIONSET INITIATE YES IN REPLY
    # ACTIVITY
    # Bug 6443218 - [AIA2.0]BPEL PROCESS THAT REPLIES A CAUGHT FAULT AND THEN
    # RETHROWS IT IS STUCK
    # Bug 6235180 - BPPEL XPATH FUNCTION XP20 CURRENT-DATETIME() IS RETURNING AN
    # INCORRET TIME
    # Bug 6011665 - BPEL RESTART CAUSES ORABPEL-08003 FAILED TO READ WSDL
    # Bug 6731179 - INCREASED REQUESTS CAUSE OUTOFMEMORY ERRORS IN OC4J_SOA WHICH
    # REQUIRES A RESTART
    # Bug 6745591 - SYNC PROCESS <REPLY> FOLLOWED BY <THROW> CASE CAUSING
    # OUTOFMEMORY ERRORS
    # Bug 6396308 - UNABLE TO SEARCH FOR HUMAN TASK THAT INCLUDES TASK HISTORY
    # FROM PREVIOUS TASK
    # Bug 6455812 - DIRECT INVOCATION FROM ESB ROUTING SERVICE FAILS WHEN CALLED
    # BPEL PROCESS
    # Bug 6273370 - ESBLISTENERIMPL.ONFATALERROR GENERATING NPE ON CUSTOM ADAPTER
    # Bug 6030243 - WORKFLOW NOTIFICATIONS FAILING WITHOUT BPELADMIN USER
    # Bug 6473280 - INVOKING A .NET 3.0 SOAP SERVICE EXPOSED BY A ESB ENDPOINT
    # GIVES A NPE
    # BUGS ADDED IN MLR#4, 6748706 :
    # Bug 6336442 - RESETTING ESB REPOSITORY DOES NOT CLEAR DB SLIDE REPOSITORY
    # Bug 6316613 - MIDPROCESS ACTIVATION AGENT DOES NOT ACTIVATED FOR RETIRED
    # BPEL PROCESS
    # Bug 6368420 - SYSTEM IS NOT ASSIGNING TASK FOR REAPPROVAL AFTER REQUEST
    # MORE INFO SUBMITTED
    # Bug 6133670 - JDEV: UNABLE TO CREATE AN INTEGRATION SERVER CONNETION WHEN
    # ESB IS ON HTTPS
    # Bug 6681055 - TEXT ATTACHMENT CONTENT IS CORRUPTED
    # Bug 6638648 - REQUEST HEADERS ARE NOT PASSED THROUGH TO THE OUTBOUND HEADER
    # Bug 5521385 - [HA]PATCH01:ESB WILL LOSE TRACKING DATA WHEN JMS PROVIDER IS
    # DOWN
    # Bug 6759068 - WORKLIST APPLICATION PERFORMANCE DEGRADATION W/ SSL ENABLED
    # FOR BPEL TO OVD
    # BUGS ADDED IN MLR#5, 6782254 :
    # Bug 6502310 - AUTOMATED RETRY ON FAILED INVOKE WITH CORRELATIONSET INIT
    # FAILS
    # Bug 6454795 - FAULT POLICY CHANGE NEEDS RESTART OF BPEL SERVER
    # Bug 6732064 - FAILED TO READ WSDL ERROR ON THE CALLBACK ON RESTARTING BPEL
    # OC4J CONTAINER
    # Bug 6694313 - ZERO BYTE FILE WHEN REJECTEDMESSAGEHANDLERS FAILS
    # Bug 6686528 - LINK IN APPLICATION.XML FILES CHANGED TO HARD LINKS WHEN MORE
    # THAN 1 HT PRESENT
    # Bug 6083024 - TEXT AND HTML DOC THAT RECEIVED AS ATTACHMENTS WERE EITHER
    # BLANK OR GARBLED
    # Bug 6638648 - REQUEST HEADERS ARE NOT PASSED THROUGH TO THE OUTBOUND HEADER
    # Bug 6267726 - 10.1.3.3 ORACLE APPLICATIONS ADAPTER - NOT ABLE TO CAPTURE
    # BUSINESS EVENT
    # Bug 6774981 - NON-RETRYABLE ERRORS ARE NOT POSTED ON ESB_ERROR TOPIC
    # Bug 6789177 - SFTP ADAPTER DOES NOT SUPPORT RENAMING FILES
    # Bug 6809593 - BPEL UPGRADE TO 10.1.3.3.1 WITH ESB CALLS FAILS DUE TO
    # CACHING OF PLNK - SERVICE
    # BUGS ADDED IN MLR#6, 6823628 :
    # Bug 6412909 - <BPELX:RENAME> DOES NOT ADD XMLNS DECLARATION AUTOMATICALLY
    # Bug 6753116 - OUTPUT FROM HUMAN TASK IS NOT IS NOT CONSISTENT WITH
    # SCHEMA
    # ORDERING
    # Bug 6832205 - BAD VERIFICATIONSERVICE PERFORMANCE IF LDAP SERVICE HAS HUGE
    # DATA
    # Bug 6189268 - CALLING BPEL PROCESS VIA SOAP FROM ESB FAILS WITH
    # NAMENOTFOUNDEXCEPTION
    # Bug 6834402 - JMS ADAPTER IMPROPERLY CASTS XAQUEUESESSION TO QUEUESESSION
    # Bug 6073117 - TASK SERVICE DOESN'T RENDER THE TASK ACTIONS
    # Bug 6054263 - REUSING SOAP WSDL IN RS CAUSES SOAP ACTION'S NS TO BE
    # STRIPPED
    # AWAY
    # Bug 6489703 - ESB: NUMBER OF LISTENERS > 1 GIVES JMS EXCEPTION UNDER STRESS
    # Bug 5679542 - FTP ADAPTER: COULD NOT PARSE TIME:
    # JAVA.LANG.STRINGINDEXOUTOFBOUNDSEXCEPTION
    # Bug 6770198 - AQ ACTIVATIONINSTANCES >1 DOESN'T WORK IN ESB
    # Bug 6798779 - ESB ROUTING RULES CORRUPTED ON RE-REGISTERING WITH ROUTING
    # ORDER
    # IN WSDL CHANGED
    # Bug 6617974 - BACKPORT REQUEST FOR MOVING FILES FUNCTION OF FTP ADAPTER
    # Bug 6705707 - VALIDATION ON ESB CAN'T HANDLE NESTED SCHEMAS
    # Bug 6414848 - FTP ADAPTER ARCHIVE FILENAME FOR BPEL IS BEING SCRAMBLED
    # AFTER
    # THE 10.1.3.3 UPGR
    # Bug 5990764 - INFORMATION ARE LOST WHEN BPEL PROCESS IS POLLING FOR MAILS
    # WITH
    # ATTACHEMENTS
    # Bug 6802070 - ORA-12899 SUBSCRIBER_ID/RES_SUBSCRIBER COLUMN SMALL FOR LONG
    # DOMAIN AND PROCESS
    # Bug 6753524 - WRONG SERVICE ENDPOINT OPEN WHEN TEST WEB SERVICE OF ESB
    # Bug 6086434 - PROBLEM IN BPEL FILE ADAPTER WHILE READING A FIXED LENGTH
    # FILE
    # Bug 6823374 - BPEL 10.1.3.3.1 BAM SENSOR ACTION FAILS WITH BAM 11
    # Bug 6819677 - HTTS STATUS 202 RETURNED INSTEAD OF SOAP FAULT
    # Bug 6853301 - MQ ADAPTER REJECTED MESSAGES IS NOT REMOVED FROM THE RECOVERY
    # QUEUE
    # Bug 6847200 - 10.1.3.3.1 PATCH (#6748706) HAS STOPPED FTP ADAPTER POLLING
    # IN
    # SFTP MODE
    # Bug 6895795 - AQ OUTBOUND DOESN'T WORK WITH MLR#6
    업무에 참고하시기 바랍니다.

    David,
    You are right, theer are some changes incorporated in the latest MLR # 16 on the configurations files and on the dehydration store metrics(such as performance, fields,..).
    However, I would not suggest to continue working on olite, even for Development/Test purposes as you might get stuck with strange errors...and the only solution would be to re-install SOA Suite if your olite gets corrupted. There might be ways to gets your olite back to position, but trust me..its not so simple.
    Also, when you develop and stress test all your testcase scenarios in an TEST Adv installation, its simple to mimic the same in actual production box, as you exactly know its behavior.
    So, go for a brand new SOA 10.1.3.4 MLR # 5 (or) 10.1.3.3.1 MLR # 16 SOA Suite Advanced installation with Oracle DB 10.2.0.3 as its dehydration store.
    Hope this helps!
    Cheers
    Anirudh Pucha

  • How to make sure one instance of BPEL process runs at a time.

    Hello,
    we have a BPEL web service and would like to run the BPEL processes serially. below is our senario
    Process "A" kicks of ( 100's of them via file polling)
    at some activity (not at the beginning) the BPEL process should check if there are any other BPEL instances of same Process "A" are running? If so then it should wait until the process completes.
    is there an API to check what other instances are running and if so if they completed or not?

    Have a look at metalink note 779136.1, you have to be on
    10.1.3.3.1 MLR#14 or above
    10.1.3.4 MLR1
    There is a note saying model on a synchronous pattern. There is no instructions on how to do this you need to create a new message definition to the wsdl
    <message name ="Dummy">
    <part xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="Dummy_element" type="xsd:string"/>
    </message>
    in the port type add an output definition
    <portType name="Read_ptt">
    <operation name="Read">
    <input message="tns:payload_msg"/>
    <output message="dummy_output"/>
    </operation>
    </portType>
    here is an example
    <definitions
    name="GetFile"
    targetNamespace="http://xmlns.oracle.com/pcbpel/adapter/file/GetFile/"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://xmlns.oracle.com/pcbpel/adapter/file/GetFile/"
    xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    xmlns:plt="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:jca="http://xmlns.oracle.com/pcbpel/wsdl/jca/"
    xmlns:pns1="http://xmlns.oracle.com/ComplexFile/correlationset"
    xmlns:pc="http://xmlns.oracle.com/pcbpel/"
    xmlns:imp1="http://TargetNamespace.com/GetFile"
    xmlns:hdr="http://xmlns.oracle.com/pcbpel/adapter/file/"
    >
    <import namespace="http://xmlns.oracle.com/ComplexFile/correlationset" location="ComplexFile_Properties.wsdl"/>
    <import namespace="http://xmlns.oracle.com/pcbpel/adapter/file/" location="fileAdapterInboundHeader.wsdl"/>
    <types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://TargetNamespace.com/GetFile" schemaLocation="sample_1.xsd"/>
    </schema>
    </types>
    <message name="payload_msg">
    <part name="payload" element="imp1:payload"/>
    </message>
    <message name="dummy_msg">
    <part name="dummy_string" xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string"/>
    </message>
    <portType name="Read_ptt">
    <operation name="Read">
    <input message="tns:payload_msg"/>
    <output message="tns:dummy_msg"/>
    </operation>
    </portType>
    <binding name="Read_binding" type="tns:Read_ptt">
    <pc:inbound_binding/>
    <operation name="Read">
    <jca:operation PhysicalDirectory="c:\temp\inbound\ComplexFile" ActivationSpec="oracle.tip.adapter.file.inbound.FileActivationSpec"
    DeleteFile="true" IncludeFiles=".*\..*" PollingFrequency="10" MinimumAge="0"
    Sorter="oracle.tip.adapter.file.inbound.listing.TimestampSorterDescending"
    OpaqueSchema="false"/>
    <input>
    <jca:header message="hdr:InboundHeader_msg" part="inboundHeader"/>
    </input>
    <output/>
    </operation>
    </binding>
    <service name="GetFile">
    <port name="Read_pt" binding="tns:Read_binding">
    <jca:address location="eis/FileAdapter" UIincludeWildcard="*.*"/>
    </port>
    </service>
    <plt:partnerLinkType name="Read_plt">
    <plt:role name="Read_role">
    <plt:portType name="tns:Read_ptt"/>
    </plt:role>
    </plt:partnerLinkType>
    </definitions>
    cheers
    James

  • Error in defining a correlation in netbeans for a BPEL

    hallo,
    would anybdy be kind enough to tell me where i've done somthing wrong?
    there are two receive activities in a BPEL, recieve1 and recieve2. on the latter i have defined a correlation whose initiator is recieve1. the related source code from correlationWSDL is :
    <vprop:property name="wzrd_prop_ContactNo_ContactNo" type="xsd:int"/>
        <vprop:propertyAlias propertyName="tns:wzrd_prop_ContactNo_ContactNo" messageType="ns:checkLeadDuplicationStatusRequest" part="part1">
            <vprop:query>/ns0:LeadCoreInfo/ns0:ContactNo</vprop:query>
        </vprop:propertyAlias>
        <vprop:propertyAlias propertyName="tns:wzrd_prop_ContactNo_ContactNo" messageType="ns:leadWSOperationRequest" part="part1">
            <vprop:query>/ns0:LeadDetailedInfo/ns0:LeadCoreInfo/ns0:ContactNo</vprop:query>
        </vprop:propertyAlias>error that i'm getting is:
    ERROR: The first step has to be "ns0:LeadCoreInfo", if an absolute path is used for query. Expression: "/ns0:LeadCoreInfo/ns0:ContactNo"
    regards

    thanks, mr. bhasin.
    i have used the same wizard for correlation.i haven't solved the problem, but have found an alternative instead. lemme tell you what i have done. if i replace
    <vprop:query>/ns0:LeadDetailedInfo/ns0:LeadCoreInfo/ns0:ContactNo</vprop:query>with the following code line then it works:
       <vprop:query>/ns0:LeadCoreInfo/ns0:ContactNo</vprop:query>the problem is that the element that is correlated on the two recieve activities has to be on the same level of hierarchy, otherwise it does give error. it seems quite ridiculous to me, coz inputs might be different at any two activities, and is the case most of the times.
    part of the schema is:
    <xsd:element name="LeadCoreInfo" type="tns:leadCoreInfoType"/>
        <xsd:element name="LeadDetailedInfo" type="tns:leadDetailedInfoType"></xsd:element>
        <xsd:element name="LeadDuplicationStatus" type="xsd:string"/>
        <xsd:element name="LeadCreated" type="xsd:integer"/>
        <xsd:element name="AgentAssigned" type="tns:agentType"/>
        <xsd:element name="AutoID" type="xsd:int"/>
        <xsd:element name="Result" type="xsd:string"/>
        <xsd:complexType name="leadCoreInfoType">
            <xsd:sequence>
                <xsd:element name="FirstName" type="xsd:string"/>
                <xsd:element name="LastName" type="xsd:string"/>
                <xsd:element name="ContactNo" type="xsd:int"/>
                <xsd:element name="Email" type="xsd:string"/>
                <xsd:element name="AutoID" type="xsd:int"/>
            </xsd:sequence>
        </xsd:complexType>
        <xsd:complexType name="leadDetailedInfoType">
            <xsd:sequence>
                <xsd:element name="LeadCoreInfo" type="tns:leadCoreInfoType"/>
                <xsd:element name="LeadOwner" type="xsd:string"/>
                <xsd:element name="Title" type="xsd:string"/>
                <xsd:element name="LeadSource">
                    <xsd:complexType>
                        <xsd:choice>
                            <xsd:element name="ColdCall" type="xsd:string"/>
                            <xsd:element name="ExistingCustomer" type="xsd:string"/>
                            <xsd:element name="IncomingCall" type="xsd:string"/>
                            <xsd:element name="EmailLead" type="xsd:string"/>
                            <xsd:element name="CustomerReferral" type="xsd:string"/>
                            <xsd:element name="Web" type="xsd:string"/>
                            <xsd:element name="WordOfMouth" type="xsd:string"/>
                        </xsd:choice>
                    </xsd:complexType>
                </xsd:element>
    in leadBPEL  i have defined a correlation on recieve2 whose initiator is recieve1. in correlation wizard, i mapped AutoID (of message sent to recieve1) to AutoID (of message sent to recieve2). the source code of leadBPEL is:
    <?xml version="1.0" encoding="UTF-8"?>
    <process
        name="leadBPEL"
        targetNamespace="http://enterprise.netbeans.org/bpel/LeadWebService/leadBPEL"
        xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable"
        xmlns:xsd="http://www.w3.org/2001/XMLSchema"
        xmlns:tns="http://enterprise.netbeans.org/bpel/LeadWebService/leadBPEL" xmlns:sxt="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/Trace" xmlns:sxed="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/Editor" xmlns:ns0="http://enterprise.netbeans.org/bpel/WizardCorrelationProperties" xmlns:ns1="http://xml.netbeans.org/schema/LeadSchema">
        <import namespace="http://j2ee.netbeans.org/wsdl/leadWS" location="leadWS.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>
        <import namespace="http://j2ee.netbeans.org/wsdl/checkLeadDuplicationWS" location="checkLeadDuplicationWS.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>
        <import namespace="http://j2ee.netbeans.org/wsdl/createLeadWS" location="createLeadWS.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>
        <import namespace="http://enterprise.netbeans.org/bpel/WizardCorrelationProperties" location="WizardCorrelationProperties.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>
        <partnerLinks>
            <partnerLink name="checkLeadDuplicationWSpartner" xmlns:tns="http://j2ee.netbeans.org/wsdl/checkLeadDuplicationWS" partnerLinkType="tns:checkLeadDuplicationWS" partnerRole="checkLeadDuplicationWSPortTypeRole"/>
            <partnerLink name="createLeadWSpartner" xmlns:tns="http://j2ee.netbeans.org/wsdl/createLeadWS" partnerLinkType="tns:createLeadWS" partnerRole="createLeadWSPortTypeRole"/>
            <partnerLink name="leadWSpartner" xmlns:tns="http://j2ee.netbeans.org/wsdl/leadWS" partnerLinkType="tns:leadWS" myRole="leadWSPortTypeRole"/>
        </partnerLinks>
        <variables>
            <variable name="CreateLeadOperationOut" xmlns:tns="http://j2ee.netbeans.org/wsdl/leadWS" messageType="tns:leadWSOperationResponse"/>
            <variable name="AutoAssignLeadOperationOut" xmlns:tns="http://j2ee.netbeans.org/wsdl/createLeadWS" messageType="tns:createLeadWSOperationResponse"/>
            <variable name="AutoAssignLeadOperationIn" xmlns:tns="http://j2ee.netbeans.org/wsdl/createLeadWS" messageType="tns:createLeadWSOperationRequest"/>
            <variable name="CreateNewLeadOperationOut" xmlns:tns="http://j2ee.netbeans.org/wsdl/createLeadWS" messageType="tns:createNewLeadOperationResponse"/>
            <variable name="CreateNewLeadOperationIn" xmlns:tns="http://j2ee.netbeans.org/wsdl/createLeadWS" messageType="tns:createNewLeadOperationRequest"/>
            <variable name="CreateLeadOperationIn" xmlns:tns="http://j2ee.netbeans.org/wsdl/leadWS" messageType="tns:leadWSOperationRequest"/>
            <variable name="CheckLeadDuplicationStatusIn1" xmlns:tns="http://j2ee.netbeans.org/wsdl/leadWS" messageType="tns:checkLeadDuplicationStatusRequest"/>
            <variable name="CheckLeadDuplicationStatusOut" xmlns:tns="http://j2ee.netbeans.org/wsdl/leadWS" messageType="tns:checkLeadDuplicationStatusResponse"/>
            <variable name="CheckLeadDuplicationWSOperationOut" xmlns:tns="http://j2ee.netbeans.org/wsdl/checkLeadDuplicationWS" messageType="tns:checkLeadDuplicationWSOperationResponse"/>
            <variable name="CheckLeadDuplicationWSOperationIn" xmlns:tns="http://j2ee.netbeans.org/wsdl/checkLeadDuplicationWS" messageType="tns:checkLeadDuplicationWSOperationRequest"/>
            <variable name="CheckLeadDuplicationStatusIn" xmlns:tns="http://j2ee.netbeans.org/wsdl/leadWS" messageType="tns:checkLeadDuplicationStatusRequest"/>
        </variables>
        <correlationSets>
            <correlationSet name="wzrd_set_Receive1_Receive2" properties="ns0:wzrd_prop_AutoID_AutoID"/>
            <correlationSet name="wzrd_set_Receive1_Receive2_1" properties="ns0:wzrd_prop_AutoID_AutoID"/>
        </correlationSets>
        <sequence>
            <receive name="Receive1" createInstance="yes" partnerLink="leadWSpartner" operation="checkLeadDuplicationStatus" xmlns:tns="http://j2ee.netbeans.org/wsdl/leadWS" portType="tns:leadWSPortType" variable="CheckLeadDuplicationStatusIn">
                <correlations>
                    <correlation set="wzrd_set_Receive1_Receive2_1" initiate="yes"/>
                </correlations>
            </receive>
            <assign name="Assign1">
                <copy>
                    <from variable="CheckLeadDuplicationStatusIn" part="part1"/>
                    <to variable="CheckLeadDuplicationWSOperationIn" part="part1leadCoreInfo"/>
                </copy>
            </assign>
            <invoke name="Invoke1" partnerLink="checkLeadDuplicationWSpartner" operation="checkLeadDuplicationWSOperation" xmlns:tns="http://j2ee.netbeans.org/wsdl/checkLeadDuplicationWS" portType="tns:checkLeadDuplicationWSPortType" inputVariable="CheckLeadDuplicationWSOperationIn" outputVariable="CheckLeadDuplicationWSOperationOut"></invoke>
            <assign name="Assign2">
                <copy>
                    <from variable="CheckLeadDuplicationWSOperationOut" part="leadDuplicationStatus"/>
                    <to variable="CheckLeadDuplicationStatusOut" part="leadDuplicationStatus"/>
                </copy>
            </assign>
            <reply name="Reply1" partnerLink="leadWSpartner" operation="checkLeadDuplicationStatus" xmlns:tns="http://j2ee.netbeans.org/wsdl/leadWS" portType="tns:leadWSPortType" variable="CheckLeadDuplicationStatusOut"></reply>
            <receive name="Receive2" createInstance="no" partnerLink="leadWSpartner" operation="createLeadOperation" xmlns:tns="http://j2ee.netbeans.org/wsdl/leadWS" portType="tns:leadWSPortType" variable="CreateLeadOperationIn">
                <correlations>
                    <correlation set="wzrd_set_Receive1_Receive2_1" initiate="no"/>
                </correlations>
            </receive>
            <assign name="Assign3">
                <copy>
                    <from variable="CreateLeadOperationIn" part="part1"/>
                    <to variable="CreateNewLeadOperationIn" part="leadDetailedInfo"/>
                </copy>
            </assign>
            <invoke name="Invoke2" partnerLink="createLeadWSpartner" operation="createNewLeadOperation" xmlns:tns="http://j2ee.netbeans.org/wsdl/createLeadWS" portType="tns:createLeadWSPortType" inputVariable="CreateNewLeadOperationIn" outputVariable="CreateNewLeadOperationOut"/>
            <if name="If1">
                <condition>$CreateNewLeadOperationOut.leadCreated = 1</condition>
                <sequence name="Sequence1">
                    <assign name="Assign4">
                        <copy>
                            <from variable="CreateNewLeadOperationIn" part="leadDetailedInfo"/>
                                <to variable="AutoAssignLeadOperationIn" part="leaddetailedInfo"/>
                        </copy>
                    </assign>
                    <invoke name="Invoke3" partnerLink="createLeadWSpartner" operation="autoAssignLeadOperation" xmlns:tns="http://j2ee.netbeans.org/wsdl/createLeadWS" portType="tns:createLeadWSPortType" inputVariable="AutoAssignLeadOperationIn" outputVariable="AutoAssignLeadOperationOut"/>
                    <assign name="Assign6">
                        <copy>
                            <from>1</from>
                            <to variable="CreateLeadOperationOut" part="leadCreated"/>
                        </copy>
                        <copy>
                            <from variable="AutoAssignLeadOperationOut" part="agentAssigned"/>
                            <to variable="CreateLeadOperationOut" part="agentAssigned"/>
                        </copy>
                    </assign>
                </sequence>
                <else>
                    <assign name="Assign5">
                        <copy>
                            <from>0</from>
                            <to variable="CreateLeadOperationOut" part="leadCreated"/>
                        </copy>
                        <copy>
                            <from>'NULL'</from>
                            <to>$CreateLeadOperationOut.agentAssigned/ns1:FirstName</to>
                        </copy>
                        <copy>
                            <from>'NULL'</from>
                            <to>$CreateLeadOperationOut.agentAssigned/ns1:Lastname</to>
                        </copy>
                        <copy>
                            <from>0</from>
                            <to>$CreateLeadOperationOut.agentAssigned/ns1:agentID</to>
                        </copy>
                    </assign>
                </else>
            </if>
            <reply name="Reply2" partnerLink="leadWSpartner" operation="createLeadOperation" xmlns:tns="http://j2ee.netbeans.org/wsdl/leadWS" portType="tns:leadWSPortType" variable="CreateLeadOperationOut"/>
        </sequence>
    </process>
    the generated source code of correlation wizard is:
    <vprop:property name="wzrd_prop_AutoID_AutoID" type="xsd:int"/><vprop:propertyAlias propertyName="tns:wzrd_prop_AutoID_AutoID" messageType="ns:checkLeadDuplicationStatusRequest" part="part1">
            *<vprop:query>/ns0:LeadCoreInfo/ns0:AutoID</vprop:query>*
        </vprop:propertyAlias>
        <vprop:propertyAlias propertyName="tns:wzrd_prop_AutoID_AutoID" messageType="ns:leadWSOperationRequest" part="part1">
            <vprop:query>/ns0:LeadDetailedInfo/ns0:LeadCoreInfo/ns0:AutoID</vprop:query>
        </vprop:propertyAlias>
    the error that i get is:C:/Documents and Settings/bushra/My Documents/NetBeansProjects/LeadWebService/src/WizardCorrelationProperties.wsdl:28,8
    ERROR: The first step has to be "ns0:LeadCoreInfo", if an absolute path is used for query. Expression: "/ns0:LeadCoreInfo/ns0:AutoID"
    if this AutoIDs in both queries are in same level of hierarchy (if  for example i send LeadDetailedInfo to recieve2, instead of LeadCoreInfo), then there is no error. Why is that?

  • BPEL Test waits forever to receive callback from human task service

    Hi,
    I've created a test (CreditCardInvalidTest.xml) to test a bpel process (testbpel.bpel) which contains a call to a human task service. The problem is when the test executes it waits forever to receive the response message from the human task service but clearly i've emulated it! Would appreciate help.
    I've attached both files and highlighted the relevant sections. Thanks.
    testbpel.bpel
    <process name="testbpel" targetNamespace="http://xmlns.oracle.com/testbpel"
    xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    xmlns:wfcommon="http://xmlns.oracle.com/bpel/workflow/common"
    xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
    xmlns:xp20="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
    xmlns:ns4="http://www.oracle.com/XSL/Transform/java/oracle.tip.xref.xpath.XRefXPathFunctions"
    xmlns:ns7="http://xmlns.oracle.com/testbpel/creditFault"
    xmlns:ldap="http://schemas.oracle.com/xpath/extension/ldap"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:wf="http://schemas.oracle.com/bpel/extension/workflow"
    xmlns:ns5="http://oracle.com/esb/namespaces/Fufillment"
    xmlns:client="http://xmlns.oracle.com/testbpel"
    xmlns:ns6="http://www.creditcardagency.com/CreditCardService"
    xmlns:ora="http://schemas.oracle.com/xpath/extension"
    xmlns:taskservice="http://xmlns.oracle.com/bpel/workflow/taskService"
    xmlns:ns9="http://xmlns.oracle.com/testbpel/orderRejected"
    xmlns:ns1="http://xmlns.oracle.com/bpel/workflow/xpath"
    xmlns:ns3="http://www.oracle.com/XSL/Transform/java/oracle.tip.esb.server.headers.ESBHeaderFunctions"
    xmlns:ns2="http://xmlns.oracle.com/bpel/services/IdentityService/xpath"
    xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
    xmlns:task="http://xmlns.oracle.com/bpel/workflow/task"
    xmlns:orcl="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc"
    xmlns:ns8="http://xmlns.oracle.com/testbpel/genericFault">
    <!--
    PARTNERLINKS
    List of services participating in this BPEL process
    -->
    <partnerLinks>
    <!--
    The 'client' role represents the requester of this service. It is
    used for callback. The location and correlation information associated
    with the client role are automatically set using WS-Addressing.
    -->
    <partnerLink name="client" partnerLinkType="client:testbpel"
    myRole="testbpelProvider" partnerRole="testbpelRequester"/>
    <partnerLink name="ShipmentService" partnerRole="execute_pptProvider"
    partnerLinkType="ns5:execute_pptLT"/>
    <partnerLink name="CreditCardService"
    partnerRole="CreditCardServiceProvider"
    partnerLinkType="ns6:CreditCardService"/>
    <partnerLink myRole="TaskServiceCallbackListener" name="TaskService"
    partnerRole="TaskService"
    partnerLinkType="taskservice:TaskService"/>
    </partnerLinks>
    <!--
    VARIABLES
    List of messages and XML documents used within this BPEL process
    -->
    <variables>
    <!-- Reference to the message passed as input during initiation -->
    <!-- Reference to the message that will be sent back to the requester during callback -->
    <variable name="inputVariable"
    messageType="client:testbpelRequestMessage"/>
    <variable name="outputVariable"
    messageType="client:testbpelResponseMessage"/>
    <variable name="n" type="xsd:integer"/>
    <variable name="Invoke_ShipmentService_execute_InputVariable"
    messageType="ns5:orderRequest_request"/>
    <variable name="paymentFault"
    messageType="client:testbpelFaultMessage"/>
    <variable name="ApproveOrder_1_globalVariable"
    messageType="taskservice:taskMessage"/>
    <variable name="orderRejectedFault"
    messageType="client:testbpelFaultMessage"/>
    </variables>
    <faultHandlers>
    <catchAll>
    <sequence name="Sequence_6">
    <throw name="Throw_AllFaults"
    faultName="ns8:testbpelGenericFault"
    faultVariable="paymentFault"/>
    </sequence>
    </catchAll>
    </faultHandlers>
    <!--
    ORCHESTRATION LOGIC
    Set of activities coordinating the flow of messages across the
    services integrated within this business process
    -->
    <sequence name="main">
    <!-- Receive input from requestor. (Note: This maps to operation defined in testbpel.wsdl) -->
    <receive name="receiveInput" partnerLink="client"
    portType="client:testbpel" operation="initiate"
    variable="inputVariable" createInstance="yes"/>
    <!--
    Asynchronous callback to the requester. (Note: the callback location and correlation id is transparently handled using WS-addressing.)
    -->
    <scope name="CheckForApproval">
    <sequence name="Sequence_4">
    <sequence name="Sequence_5">
    <scope name="ApproveOrder_1"
    xmlns:wf="http://schemas.oracle.com/bpel/extension/workflow"
    wf:key="ApproveOrder_1_globalVariable">
    <bpelx:annotation>
    <bpelx:pattern patternName="bpelx:workflow"></bpelx:pattern>
    </bpelx:annotation>
    <variables>
    <variable name="initiateTaskInput"
    messageType="taskservice:initiateTaskMessage"/>
    <variable name="initiateTaskResponseMessage"
    messageType="taskservice:initiateTaskResponseMessage"/>
    </variables>
    <correlationSets>
    <correlationSet name="WorkflowTaskIdCor"
    properties="taskservice:taskId"/>
    </correlationSets>
    <sequence>
    <assign name="ApproveOrder_1_AssignTaskAttributes">
    <copy>
    <from expression="concat(ora:getProcessURL(), string('/ApproveOrder/ApproveOrder.task'))"/>
    <to variable="initiateTaskInput"
    part="payload"
    query="/taskservice:initiateTask/task:task/task:taskDefinitionURI"/>
    </copy>
    <copy>
    <from expression="number(3)"/>
    <to variable="initiateTaskInput"
    part="payload"
    query="/taskservice:initiateTask/task:task/task:priority"/>
    </copy>
    <copy>
    <from>
    <payload xmlns="http://xmlns.oracle.com/bpel/workflow/task"/>
    </from>
    <to variable="initiateTaskInput"
    part="payload"
    query="/taskservice:initiateTask/task:task/task:payload"/>
    </copy>
    </assign>
    <assign name="ApproveOrder_1_AssignSystemTaskAttributes">
    <copy>
    <from expression="ora:getInstanceId()"/>
    <to variable="initiateTaskInput"
    part="payload"
    query="/taskservice:initiateTask/task:task/task:processInfo/task:instanceId"/>
    </copy>
    <copy>
    <from expression="ora:getProcessId()"/>
    <to variable="initiateTaskInput"
    part="payload"
    query="/taskservice:initiateTask/task:task/task:processInfo/task:processName"/>
    </copy>
    <copy>
    <from expression="ora:getProcessId()"/>
    <to variable="initiateTaskInput"
    part="payload"
    query="/taskservice:initiateTask/task:task/task:processInfo/task:processId"/>
    </copy>
    <copy>
    <from expression="ora:getProcessVersion()"/>
    <to variable="initiateTaskInput"
    part="payload"
    query="/taskservice:initiateTask/task:task/task:processInfo/task:processVersion"/>
    </copy>
    <copy>
    <from expression="ora:getDomainId()"/>
    <to variable="initiateTaskInput"
    part="payload"
    query="/taskservice:initiateTask/task:task/task:processInfo/task:domainId"/>
    </copy>
    <copy>
    <from expression="string('BPEL')"/>
    <to variable="initiateTaskInput"
    part="payload"
    query="/taskservice:initiateTask/task:task/task:processInfo/task:processType"/>
    </copy>
    </assign>
    <invoke name="initiateTask_ApproveOrder_1"
    partnerLink="TaskService"
    portType="taskservice:TaskService"
    operation="initiateTask"
    inputVariable="initiateTaskInput"
    outputVariable="initiateTaskResponseMessage">
    <correlations>
    <correlation initiate="yes"
    set="WorkflowTaskIdCor"
    pattern="in"/>
    </correlations>
    </invoke>
    *<receive name="receiveCompletedTask_ApproveOrder_1"*
    partnerLink="TaskService"
    portType="taskservice:TaskServiceCallback"
    operation="onTaskCompleted"
    variable="ApproveOrder_1_globalVariable"
    createInstance="no">
    *<correlations>*
    *<correlation initiate="no"*
    set="WorkflowTaskIdCor"/>
    *</correlations>*
    *</receive>*
    </sequence>
    </scope>
    <switch name="taskSwitch">
    <case condition="bpws:getVariableData('ApproveOrder_1_globalVariable', 'payload', '/task:task/task:systemAttributes/task:state') = 'COMPLETED' and bpws:getVariableData('ApproveOrder_1_globalVariable', 'payload', '/task:task/task:systemAttributes/task:outcome') = 'REJECT'">
    <bpelx:annotation>
    <bpelx:pattern patternName="case">Task outcome is REJECT</bpelx:pattern>
    </bpelx:annotation>
    <sequence>
    <assign name="AssignOrderRejected">
    <copy>
    <from expression="string('Order rejected by manager')"/>
    <to variable="paymentFault"
    part="payload"
    query="/client:testbpelProcessFault/client:status"/>
    </copy>
    </assign>
    <throw name="ThrowOrderRejected"
    faultName="ns9:orderRejectedFault"
    faultVariable="orderRejectedFault"/>
    </sequence>
    </case>
    <case condition="bpws:getVariableData('ApproveOrder_1_globalVariable', 'payload', '/task:task/task:systemAttributes/task:state') = 'COMPLETED' and bpws:getVariableData('ApproveOrder_1_globalVariable', 'payload', '/task:task/task:systemAttributes/task:outcome') = 'APPROVE'">
    <bpelx:annotation>
    <bpelx:pattern patternName="case">Task outcome is APPROVE</bpelx:pattern>
    </bpelx:annotation>
    <sequence>
    <empty name="Empty_1"/>
    </sequence>
    </case>
    <otherwise>
    <bpelx:annotation>
    <bpelx:pattern>Task is outcome is EXPIRED, STALE, WITHDRAWN or ERRORED</bpelx:pattern>
    </bpelx:annotation>
    <sequence>
    <empty name="Empty_2"/>
    </sequence>
    </otherwise>
    </switch>
    </sequence>
    </sequence>
    </scope>
    <scope name="CheckCreditCard">
    <variables>
    <variable name="InvokeCreditCardService_process_InputVariable"
    messageType="ns6:CreditCardServiceRequestMessage"/>
    <variable name="InvokeCreditCardService_process_OutputVariable"
    messageType="ns6:CreditCardServiceResponseMessage"/>
    </variables>
    <sequence name="Sequence_2">
    <assign name="Assign_1">
    <copy>
    <from variable="inputVariable" part="payload"
    query="/client:testbpelProcessRequest/client:CreditCardNumber"/>
    <to variable="InvokeCreditCardService_process_InputVariable"
    part="payload"
    query="/ns6:CreditCardServiceProcessRequest/ns6:CreditCardNumber"/>
    </copy>
    </assign>
    <scope name="Scope_1">
    <compensationHandler>
    <sequence name="Sequence_7">
    <empty name="Empty_3"/>
    </sequence>
    </compensationHandler>
    <invoke name="InvokeCreditCardService"
    partnerLink="CreditCardService"
    portType="ns6:CreditCardService" operation="process"
    inputVariable="InvokeCreditCardService_process_InputVariable"
    outputVariable="InvokeCreditCardService_process_OutputVariable"/>
    </scope>
    <switch name="CheckCreditCardValid">
    <case condition="bpws:getVariableData('InvokeCreditCardService_process_OutputVariable','payload','/ns6:CreditCardServiceProcessResponse/ns6:result') = 'false'">
    <sequence name="Sequence_3">
    <assign name="AssignCreditFault">
    <copy>
    <from expression="string('Invalid credit card number')"/>
    <to variable="paymentFault" part="payload"
    query="/client:testbpelProcessFault/client:status"/>
    </copy>
    </assign>
    <throw name="ThrowCreditFault"
    faultName="ns7:CreditCardNumberFault"
    faultVariable="paymentFault"/>
    </sequence>
    </case>
    </switch>
    </sequence>
    </scope>
    <assign name="AssignInitial">
    <copy>
    <from expression="string('Select Manufacturer')"/>
    <to variable="outputVariable" part="payload"
    query="/client:testbpelProcessResponse/client:result"/>
    </copy>
    <copy>
    <from expression="1"/>
    <to variable="n"/>
    </copy>
    <copy>
    <from expression="0.0"/>
    <to variable="outputVariable" part="payload"
    query="/client:testbpelProcessResponse/client:price"/>
    </copy>
    </assign>
    <while name="While_1"
    condition="bpws:getVariableData('n') &lt;= count(bpws:getVariableData('inputVariable','payload','/client:testbpelProcessRequest/client:input'))">
    <sequence name="Sequence_1">
    <assign name="DoCalculation">
    <copy>
    <from expression="bpws:getVariableData('inputVariable','payload', concat('/client:testbpelProcessRequest/client:input[', bpws:getVariableData('n'), ']/client:quantity')) * bpws:getVariableData('inputVariable','payload',concat('/client:testbpelProcessRequest/client:input[', bpws:getVariableData('n'), ']/client:bookPrice')) + bpws:getVariableData('outputVariable','payload','/client:testbpelProcessResponse/client:price')"/>
    <to variable="outputVariable" part="payload"
    query="/client:testbpelProcessResponse/client:price"/>
    </copy>
    <copy>
    <from expression="bpws:getVariableData('n') + 1"/>
    <to variable="n"/>
    </copy>
    </assign>
    </sequence>
    </while>
    <assign name="Transform_2">
    <bpelx:annotation>
    <bpelx:pattern>transformation</bpelx:pattern>
    </bpelx:annotation>
    <copy>
    <from expression="ora:processXSLT('TransformOrder.xsl',bpws:getVariableData('inputVariable','payload'))"/>
    <to variable="Invoke_ShipmentService_execute_InputVariable"
    part="orderRequest"/>
    </copy>
    </assign>
    <invoke name="Invoke_ShipmentService" partnerLink="ShipmentService"
    portType="ns5:execute_ppt" operation="execute"
    inputVariable="Invoke_ShipmentService_execute_InputVariable"/>
    <invoke name="callbackClient" partnerLink="client"
    portType="client:testbpelCallback" operation="onResult"
    inputVariable="outputVariable"/>
    </sequence>
    </process>
    CreditCardInvalidTest.xml
    <BPELTest processName="testbpel"
    xmlns="http://xmlns.oracle.com/bpel/instancedriver"
    xmlns:client="http://xmlns.oracle.com/testbpel">
    <initiate operation="initiate">
    <inboundMessage>
    <part fileName="testInput.xml" name="payload"/>
    </inboundMessage>
    </initiate>
    <activityDriver name="callbackClient">
    <assertValue variableName="outputVariable" partName="payload"
    comparisonMethod="string" fatal="false" patternMatch="false">
    <message>Expected "Select Manufacturer"</message>
    <actualPath>/client:testbpelProcessResponse/client:result</actualPath>
    <expected>Select Manufacturer</expected>
    </assertValue>
    <assertValue variableName="outputVariable" partName="payload"
    comparisonMethod="string" fatal="true" patternMatch="false">
    <message>Expected price of "1"</message>
    <actualPath>/client:testbpelProcessResponse/client:price</actualPath>
    <expected>1</expected>
    </assertValue>
    </activityDriver>
    *<activityDriver name="receiveCompletedTask_ApproveOrder_1">*
    *<emulate duration="PT">*
    *<inboundMessage>*
    *<part fileName="approverResponse.xml" name="payload"/>*
    *</inboundMessage>*
    *</emulate>*
    *</activityDriver>* <--- it waits FOREVER at this bit to receive the approverResponse.xml :s
    <activityDriver name="InvokeCreditCardService">
    <emulate duration="PT">
    <inboundMessage>
    <part fileName="creditCardServiceResponse.xml" name="payload"/>
    </inboundMessage>
    </emulate>
    </activityDriver>
    <activityDriver name="initiateTask_ApproveOrder_1">
    <emulate duration="PT">
    <inboundMessage>
    <part fileName="getApproval.xml" name="payload"/>
    </inboundMessage>
    </emulate>
    </activityDriver>
    </BPELTest>

    RaviKiran,
    I agree that the explanation oracle provided in the attach link, is a bit confusing. The main goal there is to describe the behavior of processes, when there is a need to combine, or split the transactions within those processes (or in some cases the processes themselves).
    The thing is - The default transaction for a synchronous process is requiresNew. That was until version 11.1.1.6. On this last version, you are asking to enter a Transaction parameter when creating a new synchronous bpel process. The default value being prompt is required and that's what causing the problem – You automatically accept the default.
    The assumption is, that developing bpel processes, should come with understanding of all those behaviors.
    The problem for my understanding is that some of those behaviors were not so cleared until now.
    Arik

  • BPEL Server bug?

    Hi all,
    I experienced a curious problem using the test Console of BPEL Server 10.1.2. I created a process where, besides other activities, there are 2 receives (the first has createInstance="yes") with correlationSet, on the same partnerLink, portType, operation, and using the same BPEL variable. These 2 receives are in a sequence (not in concurrence). The problem is that when I send the second message on the second receive through the BPEL Console, the Server initiates a new instance of the same process. I went over the BPEL Specification and I think this should be possible according to that document.
    Note, if I try the same think with 2 non ititial receives (without createInstance="yes") it works properly. Even with 2 invokes on the same partnerLink, portType and operation (not in concurrence).
    I suppose this is a bug of the BPEL Server.
    Could you check please?
    Thanks a lot

    While if I use, for the 2nd receive, another 'operation', declared into the same portType, it works properly. I think maybe the BPEL Server maps every process with the operation name used by the first receive activity, in order to create process instances.
    Thanks

  • Correlation property of correlationSet "name" is not defined

    Hi.
    I have got strange problem with correlation property.
    I am using JDeveloper Studio Edition Version 11.1.1.5.0 with Oracle 11g Fusion middleware Version 11.1.1.5.0.
    I created BPEL process driven by EDA. All receive and pick activity are event driven.
    Everything works fine till I tried to make correlation.
    I use wizard to create CorrelationSet and correlation property, assign type and create property aliases.
    Now I get error correlation property "{http://xmlns.process.com/oxygenium/OrderAuthorization/OrderAuthorization/correlationset}webOrder_property" of correlationSet "webOrderCorrelationSet" is not defined.
    Error message points to line with <correlationSets><correlationSet name="webOrderCorrelationSet" properties="ns7:webOrder_property"/></correlationSets>
    xmlns:ns7="http://xmlns.process.com/oxygenium/OrderAuthorization/OrderAuthorization/correlationset"
    I can't understand what is wrong. Wizard show all dependencies OK.
    Please help.
    Thanks in advance.

    Problem still remains.
    The only way to solve I found is add SOAP webservice interface with partnerlink. After that compiler didn't find any error but what horrible workaround it is...
    I think there is bug in compiler which doesn't allow create correlation set without partnerlink :(
    Please give me a hope that there is a normal solution.
    Thank you

  • BPEL Testcase with pick-activity

    I use JDeveloper 10.1.3.3.0.4157 but I have not opportunity to create "Emulate Receive message" for pick activity.
    When I tried edit test manually
    <activityDriver name="order_Pick">
    <emulate duration="PT">
    <inboundMessage>
    <part fileName="initiationMsg.xml"
    name="payload"/>
    </inboundMessage>
    </emulate>
    </activityDriver>
    I get error:
    [Error ORABPEL-20055]: Invalid emulation.
    [Description]: in line 26 of "main.xml", Activity "order_Pick" is not an onAlarm event handler or a receive,
    invoke, or wait activity. Only those activities can be emulated.
    [Potential fix]: Please correct the test driver appropriately..
    What is wrong?

    Process is too long but I post snippet
    BPEL
    <receive name="receiveInput" partnerLink="client"
    portType="client:order" operation="initiate"
    variable="inputVariable" createInstance="yes">
    <correlations>
    <correlation initiate="yes" set="correlationSet"/>
    </correlations>
    </receive>
    <sequence name="start_Sequence">
    <sequence name="checking">
    <scope name="checking_Scope">
    <sequence name="checking_Sequence">
    <invoke name="checking_Invoke" partnerLink="checking"
    portType="ns2:checking"
    operation="checking"
    inputVariable="checking_InputVariable"
    outputVariable="checking_OutputVariable"/>
    <reply name="replyOutput" partnerLink="client"
    portType="client:order" operation="initiate"
    variable="check_OutputVariable"/>
    </sequence>
    </scope>
    </sequence>
    <pick name="final_Pick">
    <onMessage portType="client:order"
    operation="finalData" variable="inputVariable"
    partnerLink="client"
    bpelx:name="finalData">
    <correlations>
    <correlation initiate="no" set="OrdersCorrelationSet"/>
    </correlations>
    <sequence name="final_Sequence">
    <assign name="final_Assign">
    <copy>
    <from expression="'started'"/>
    <to variable="outputVariable" part="payload"
    query="/client:orderResponse/client:result"/>
    </copy>
    </assign>
    <reply name="final_Reply" partnerLink="client"
    portType="client:order"
    operation="finalData" variable="outputVariable"/>
    </sequence>
    </onMessage>
    <onAlarm for="'PT30M'">
    <terminate name="final_Terminate"/>
    </onAlarm>
    </pick>
    Testcase
    <BPELTest processName="order"
    xmlns="http://xmlns.oracle.com/bpel/instancedriver">
    <initiate operation="initiate">
    <inboundMessage>
    <part fileName="initiationMsg.xml" name="payload"/>
    </inboundMessage>
    </initiate>
    <activityDriver name="checking_Invoke">
    <emulate duration="PT">
    <inboundMessage>
    <part fileName="checkingResponse.xml"
    name="checkingResponseElement"/>
    </inboundMessage>
    </emulate>
    </activityDriver>
    <activityDriver name="final_Pick">
    <triggerOnMessage doBeforeActivity="true" onMessageName="finalData">
    <inboundMessage>
    <part fileName="initiationMsg.xml" name="payload"/>
    </inboundMessage>
    </triggerOnMessage>
    </activityDriver>
    </BPELTest>
    WSDL
    <portType name="order">
    <operation name="initiate">
    <input message="client:RequestMessage"/>
    <output message="client:checkingResponse"/>
    </operation>
    <operation name="checkData">
    <input message="client:RequestMessage"/>
    <output message="client:checkingResponse"/>
    </operation>
    <operation name="finalData">
    <input message="client:RequestMessage"/>
    <output message="client:ResponseMessage"/>
    </operation>
    </portType>

  • CorrelationSet error on TaskActionHandler Service

    Hi all,
    there's an error on CorrelationSet related to property taskId (propertyAlias: task/taskId) when using the Human Workflow Wizard (Pattern= sequential).
    I experienced this problem running "OrderBooking" tutorial and the util StarLoanWithWorkflow. Infact every time I have to copy the output message from the TaskActionHandler Service into the receive activity (onTaskCompleted) of the main process if I want that it works properly, because the message is lost. I tried to re-set correlationSet in file TaskActionHandler.wsdl with the correct field (taskId, which is a xsd:string) and messageType="taskMngr:taskMessage" but it still doesn't work.
    Thank you

    Ok, I undestood! The problem occurs only if I change these properties in the BPEL Admin Panel:
    - BPEL soap callback URL (http://mlr:9700)
    - BPEL soap server URL (http://mlr:9700)
    which I replaced with "http://localhost:9700" for portability reasons.
    How can I use the worklist if I want to change these properties with "localhost" insted of my computer_name "mlr"?
    Thanks

  • Corelation not getting compiled in BPEL

    Hi,
    I have a BPEL ( V 1.1, one-way ) that uses corelation.
    I have created the corelation,added property and then property alias and evrything is visble in structure window.
    But when i try to compile it gives the following error.
    [scac] error: in GDIPExaminationArchingProcess.bpel(129): correlation property "{http://xmlns.oracle.com/GDIP/GDIPExaminationArchingProcess/GDIPExaminationArchingProcess/correlationset}CorrelationSetYASEER_property" of correlationSet "CorrelationSetYASEER" is not defined
         [scac] error: in GDIPExaminationArchingProcess.bpel(180): correlation set "CorrelationSetYASEER" cannot be used in this <correlation>, because property "{http://xmlns.oracle.com/GDIP/GDIPExaminationArchingProcess/GDIPExaminationArchingProcess/correlationset}CorrelationSetYASEER_property  of this correlation set is not associated with the message "{http://xmlns.oracle.com/Biller_Yesser_Integration/BillLoadJMSProducer/BillLoadJMSProducer}BillLoadJMSProducerResponseMessage"
    Please let me know if someone has solution.
    Thanks,
    Lalit

    Looking at the error, I suppose, the correlation set is defined in the BPEL process and it is associated with the JMS adapter invoke/receive? Then, probably you may need to also import the namespace of the correlation set from the BPEL process wsdl to the JMS adapter wsdl (with the <import namespace="..." location="..."/> tag).

  • BPEL Test Suite issue

    I am trying to emulate the human task in BPEL process. here is the test source to emulate the human task
    <initiate operation="process">
    <inboundMessage>
    <part fileName="input_row_id_120780.xml" name="payload"/>
    </inboundMessage>
    </initiate>
    <activityDriver name="initiateTask_WorkFlowFollowUpInitiate_1">
    <emulate duration="PT">
    <inboundMessage>
    <part fileName="initiate_response_12780.xml" name="payload"/>
    </inboundMessage>
    </emulate>
    </activityDriver>
    <activityDriver name="receiveTaskUpdates_WorkFlowFollowUpInitiate_1">
    <triggerOnMessage doBeforeActivity="true" onMessageName="initiateCompleted">
    <inboundMessage>
    <part name="payload" fileName="initiate_withdrawn_120780.xml"/>
    </inboundMessage>
    </triggerOnMessage>
    <assertValue variableName="inputVariable" partName="payload"
    comparisonMethod="string" fatal="false" patternMatch="true">
    <message>test</message>
    <actualPath>/client:WorkFlow4FollowUpProcessProcessRequest/client:input</actualPath>
    <expected>[0-9]+</expected>
    </assertValue>
    </activityDriver>
    but it does not seem to be working. I cannot see any human task created in the worklist application but the instance keep waiting for the callback message which I am already giving through "triggerOnMessage".
    I dont understand what am i doing wrong. Other thing I want to do is can I use the "triggerOnMessage" without emulating the "initiateTask" response.

    Hi Clemens,
    Thanks for the reply. I was not setting the correlation sets previously. but now when I setup the correlation sets, I am getting the following exceptions.
    I am running 10.1.3.5. I tried redeploying the process but with no success. I am using the pick activity to receive callbacks.
    I also see bug *5332819* on metalink. It says this issue was fixed in 10.1.3.2. But still I am running into to the same issue with 10.1.3.5. Any suggestion or workaround
    ORABPEL-03802
    Correlation definition not registered.
    The correlation set definition for operation "onSubTaskUpdated", process "WorkFlow4FollowUpProcess", has not been registered with the process domain.
    Please try to redeploy your process to the process domain.
    I am using the taskId as the correlation property.
    correlation property
    <bpws:property name="taskID_prop" type="xsd:string"/>
    property aliases
    <bpws:propertyAlias propertyName="pns1:taskID_prop" messageType="ns1:initiateTaskResponseMessage" part="payload"
    query="/ns1:initiateTaskResponse/ns3:task/ns3:systemAttributes/ns3:taskId" xmlns:ns1="http://xmlns.oracle.com/bpel/workflow/taskService"
    xmlns:ns3="http://xmlns.oracle.com/bpel/workflow/task" xmlns:ns2="http://xmlns.oracle.com/bpel/workflow/common"/>
    <bpws:propertyAlias propertyName="pns1:taskID_prop" messageType="ns1:taskAssignedMessage" part="payload"
    query="/ns1:taskAssignedMessage/ns2:task/ns2:systemAttributes/ns2:taskId" xmlns:ns1="http://xmlns.oracle.com/bpel/workflow/taskService"
    xmlns:ns2="http://xmlns.oracle.com/bpel/workflow/task"/>
    <bpws:propertyAlias propertyName="pns1:taskID_prop" xmlns:ns2="http://xmlns.oracle.com/bpel/workflow/taskService"
    messageType="ns2:taskMessage" part="payload" query="/ns1:task/ns1:systemAttributes/ns1:taskId"
    xmlns:ns1="http://xmlns.oracle.com/bpel/workflow/task"/>
    <bpws:propertyAlias propertyName="pns1:taskID_prop" messageType="ns1:subTaskUpdatedMessage" part="payload"
    query="/ns1:subTaskUpdatedMessage/ns1:parentTaskId" xmlns:ns1="http://xmlns.oracle.com/bpel/workflow/taskService"
    xmlns:ns3="http://xmlns.oracle.com/bpel/workflow/task" xmlns:ns2="http://xmlns.oracle.com/bpel/workflow/common"/>
    <bpws:propertyAlias propertyName="pns1:taskID_prop" messageType="ns1:taskUpdatedMessage" part="payload"
    query="/ns1:taskUpdatedMessage/ns2:task/ns2:systemAttributes/ns2:taskId" xmlns:ns1="http://xmlns.oracle.com/bpel/workflow/taskService"
    xmlns:ns2="http://xmlns.oracle.com/bpel/workflow/task"/>
    <bpws:propertyAlias propertyName="pns1:taskID_prop"
    messageType="ns1:initiateTaskMessage" part="payload" query="/ns1:initiateTask/ns2:task/ns2:systemAttributes/ns2:taskId"
    xmlns:ns1="http://xmlns.oracle.com/bpel/workflow/taskService" xmlns:ns2="http://xmlns.oracle.com/bpel/workflow/task"/>
    Correlation Set
    <correlationSets>
    <correlationSet name="TaskIdCor" properties="ns20:taskID_prop"/>
    </correlationSets>
    Use in invoking the task service.
    <correlations>
    <correlation initiate="yes" set="TaskIdCor" pattern="in"/>
    </correlations>
    Use in the pick OnMessage activities.
    <correlations>
    <correlation initiate="no" set="TaskIdCor"/>
    </correlations>
    Edited by: tanvirmp on Dec 17, 2009 11:27 AM

  • Correlation Conflict inside BPEL

    Hi ,
    I am getting correlation conflict inside the BPEL process.
    Can any body suggest some solution to it.
    Conflicting receive.
    A similar receive activity is being declared in the same process. Another receive activity or equivalent (currently, onMessage branch in a pick activity)
    has already been enabled with the partnerLink "CreateOrUpdateRWOService", operation name "AcknowledgeRWO" and correlation set "{{http://xmlns.oracle.com/RWOProcessApp/RWOProcess/CreateOrUpdateRWOProcess/correlationset}RWOReference=
    {http://xmlns.oracle.com/RWOProcessApp/RWOProcess/CreateOrUpdateRWOProcess/correlationset}RWOReference=}" (or conversation ID). Appendix A -
    Standard Faults in the BPEL 1.1 specification specifies a fault should be thrown under these conditions. Redeploy the process after removing the conflicting receive activities.
    Regards
    Manish
    Edited by: 858026 on Sep 14, 2011 5:28 PM

    Yes you can achieve this. There are many ways to get this, it depends on your design. I didn't try the correlation sets.
    If i were you I would like to use the message header properties of the JMS queue. Set an MsgID for the request message and use the same MsgId to listen the response. You have to ask the partner to listen to your request message and store the KsgID and set the same MsgID to the header properties in response message.
    Let me know if you have any questions.
    Thanks
    Ramana.

Maybe you are looking for

  • While posting truncation in   *j1incust* (enter withholding tax certificate

    Dear experts while posting truncation in   j1incust (enter withholding tax certificate from customer ) am getting this error No unpaid tax lines exist for the given selection criteria. Message no. 8I702 Diagnosis The corresponding withholding tax lin

  • Can I update plugin on dial-up - check & update page doesn't work

    I am on DIAL UP as I live in remote area. Got message that Flash plugin was disabled because it is out of date. Tried to update and told plugins BLOCKED FOR MY SAFETY, then told to go to "Plugin Check & Update" page. The "Checking Mozilla on Status o

  • IT0008 Work hrs/period and ANSAL issue

    Folks, Work hrs/period in IT0008 is defaulted from customizing or previous record, however for us, it works like this. IT0007 for example has 150hrs, in IT0008 is created as 150/2 - 75hrs, when it is semi-monthly and the text next to work hrs/period

  • "Organizational Rules"

    HI: I am looking for anyone who has experience in developing the "Organizational Rules" in Compliance Calibrator 4.0 or 5.3. We have the basic rule set loaded, with some custom functions and risks.  However, we are the parent company of many subsidia

  • How to find payroll results using includes

    hi all,       I have a requirement to get the payroll results of number of data clusters using includes not by using function modules. I know by using function modules.       How to find out the exact include for given data cluster. If there is any p