In the window that opens, enter BPEL2ODIAsync in the Application Name field. Click OK.

In the Create Project window that appears, click Cancel. The BPEL2ODIAsync application appears in the Applications Navigator.

Select File > Open. Browse to the G:\ODIInvokerService_generation2 directory and select the ODIInvokerService.jpr file. Click Open and the ODIInvokerService appears in the Applications Navigator.

Note: At this point, you have imported the Java Wrapper Service (ODIInvokerService) that acts as the intermediary between BPEL and ODI. It is recommended that you take some time to browse the classes and details of the service to gain an understanding of how it works. Note that the Java application contains two interfaces: a synchronous Web service interface (ODIAsyncStarterWebService) and a stand-alone Java interface (odi-async-standalone.jar). You will be invoking the Web service interface, which requires to pass callback information to call back the correct BPEL instance via the BPEL API and the ODI information to invoke the correct ODI scenario via the ODI API.

To configure the library locations that will be used at run time, right-click the ODIInvokerService in the Applications Navigator and select Project Properties. In the window that opens, select Libraries from the Explorer on the left. From the Libraries list, select the Orabpel.jar library and click Edit. On the Edit Library Definition window, highlight the current Class Path value and click Remove.

Highlight Class Path: and click Add Entry. Browse to your SOA_HOME/bpel/lib directory (E:\SOASuite10131\bpel\lib) and select orabpel.jar (if you get this library from another location, ensure that it is the same version as your installed SOA Suite). Click Select. On the Edit Library Definition window, ensure that the Deployed by Default check box is selected and click OK.

Similarly, from the Libraries list, select the Orabpel-common.jar library and click Edit. In the window that appears, highlight the current Class Path value and click Remove. Highlight Class Path: and click Add Entry. Browse to your SOA_HOME/bpel/lib directory (E:\SOASuite10131\bpel\lib) and select orabpelcommon.jar (if you get this library from another location, ensure that it is the same version as your installed SOA Suite). On the Edit Library Definition window, ensure that the Deployed by Default check box is selected and click OK.

On the Project Properties page, make sure that Export is selected for all the libraries that you edited and click OK. From the Applications Navigator, right-click ODIInvokerService and select Rebuild.

To deploy the Java service, ensure that you have a connection configured in JDeveloper to your application server, and that it is up and running. In the Applications Navigator, expand Applications > BPEL2ODIAsync > ODIInvokerService > Resources. Right-click WebServices.deploy and select Deploy to > your application server connection (for example, SoademoApplicationServer as shown in the screenshot). Click OK in any windows that appear. The Deployment Log appears at the bottom of the page and displays a message indicating that the deployment is complete as shown below.

To verify that the service is deployed and accessible, open Application Server Control in a browser (http://localhost:8888/em/). Log in using your administrator credentials (User name: oc4jadmin and Password: welcome1). On the Enterprise Manager page, select the oc4j container to which you deployed ODIInvokerService (Home JVMs). On the OC4J Home page, click the Applications tab. On the Applications tab, under default, locate and select the odi-webservice application.

On the odi-webservice page, click the Web Services tab, and then click the Test Service button.

Note: Do not close the last page that you opened as you need it to copy the WSDL URL location in the next section. At this point, you do not test the service but you can see the input fields that are used to call the ODI scenario, and then call back to the BPEL process. The ODIINvokerService is now deployed and ready to run.

On the BPEL Project Creation Wizard screen, name the project AsyncODICall and ensure that Asynchronous BPEL Process is selected. Click Next. Click the Flashlight icon next to the Input Schema Element field. Browse to your OBE_LABS directory and select ODIService.xsd. Click Open.

In the Type Chooser window, expand Imported Schemas > ODIService.xsd and select ODIProcessRequest. Click OK.

Click the Flashlight icon next to the Output Schema Element field. In the Type Chooser window, expand Imported Schemas > ODIService.xsd and select ODIProcessResponse. Click OK.

Click Finish on the BPEL Project Creation Wizard screen. Your new AsyncODICall project opens in the main JDeveloper window. Save your project (select File > Save All).

Right-click ODIInvokerServiceResponseMessage and select Insert inside message - ODIInvokerServiceResponseMessage > http://schemas.xmlsoap.org/wsdl/ > part. In the window that appears, name the part payload. Select the Reference Type to be element. Enter ns1:ODIInvokerServiceResponse in the Part Type field. Click OK.

Similarly, in the Structure pane, expand definitions and right-click Messages. Select Insert Message. In the window that appears, name the message ODIInvokerServiceFaultMessage. Click OK. Right-click the ODIInvokerServiceFaultMessage and select Insert inside ODIInvokerServiceFaultMessage >http://schemas.xmlsoap.org/wsdl > part. Name the part payload. Select the Reference Type to be element. Enter ns1:ODIInvokerServiceFault in the Part Type field. Click OK.

Verify that your AsyncODICall.wsdl has the structure as shown below.

Under Port Types, select and right-click AsyncODICall. Select Insert inside AsyncODICall > http://schemas.xmlsoap.org/wsdl/ > operation. In the window that appears, name the operation onODIResult. Select One Way from the Operation Type drop-down list. Select client:ODIInvokerServiceResponseMessage from the Input drop-down list and click OK. A new operation appears under initiate.

Again under Port Types, select and right-click AsyncODICall. Select Insert inside AsyncODICall > http://schemas.xmlsoap.org/wsdl/ > operation. In the window that appears, name the operation onODIError. Select One Way from the Operation Type drop-down list. Select client:ODIInvokerServiceFaultMessage from the Input drop-down list and click OK. A new operation appears under initiate.

Verify that your AsyncODICall.wsdl has the structure as shown below. Save your project (select File > Save All) and close the AsyncODICall.wsdl file. Click the AsyncODICall.bpel file tab and click the green check mark at the top of the page. This should refresh the BPEL process with the changes that you just made (you may have to close and reopen the BPEL file for the changes to take effect).

Note: You have now updated the BPEL interface by creating two new operations: onODIResult and onODIError.

From the Partner Link Type drop-down list, select ODIAsyncStarterWebservice_PL. From the Partner Role drop-down list, select ODIAsyncStarterWebservice_Role. Leave the other fields with the defaults and click OK. The ODIAsyncStarterWebservice Partner Link appears in your process diagram.

From the Components Palette at the right, select Process Activities from the drop-down list, and then drag the Invoke activity onto your process between the receiveInput and callbackClient activities. Drag one of the arrows from the new Invoke activity onto the ODIAsyncStarterWebservice Partner Link.

In the Edit Invoke window, name the activity Invoke_ODI. Click the Magic Wand icon next to the Input Variable field. In the Create Variable window, name the variable startOdiPlan_InputVariable. Click OK.

In the Property Value box, enter 1. From the Encryption drop-down list, select Plain Text. Click the Create icon and repeat the preceding steps for the preferences in the following table. You should have your Deployment Descriptor Properties as shown in the following screenshot. Click OK.

Note: Some of the property values are specific to your environment. The values here are generally correct if you have performed a basic SOA installation. Check your values.

Double-click the new Assign_1 activity. Click the General tab and name the activity Assign_ODIValues. Click the Copy Operation tab and from the Create drop-down list, select Copy Operation.

In the window that opens, in the From column, expand Process > Variables > inputVariable > payload > ODIProcessRequest > ODI_Info. In the To column, expand Process > Variables > startOdiPlan_InputVariable > parameters > StartOdiPlanElement > OdiInformationDTO_1. Click OK.

Now set the preferences from the last section. From the Create drop-down list, select Copy Operation. A new dialog box appears. In the From column, from the Type drop-down list, select Expression. Click the Xpath Expression Builder button at the top-right of the From column.

In the Expression Builder window, under the Functions heading, select BPEL Xpath Extension Functions from the drop-down list. From the updated list, select getPreference and click the Insert Into Expression button. The Expression window now contains ora:getPreference(). Change this to ora:getPreference("retryCount"), where retryCount is the name of one of the preferences that you set earlier. Click OK.

In the To column, expand Process > Variables > startOdiPlan_InputVariable > parameters > StartOdiPlanElement > CallbackInformationDTO_2 > retryAttempts. Click OK.

Repeat the above steps (that created the retryCount copy rule from a preference) to create copy rules for the other preferences. The From and To fields are listed in the following table. Your Assign activity with the six copy rules should now match the following screenshot.

You still need to create eight more copy rules. For each row in the following table, create a copy rule, select Expression in the From column and enter the corresponding value from the following table. In the To column expand Process > Variables > startOdiPlan_InputVariable > parameters > StartOdiPlanElement > CallbackInformationDTO_2 and select the value that matches the value from the table. Your copy operation should now have 14 copy rules inside it and look similar to the following screenshot. Click OK.

In the Code Snippet field, cut and paste the code provided below. To save your project, select File > Save All.

/* The following code appends the Credentials preference
with the instance conversation ID,then encrypts and
assigns to the ODIInvokerService input message.
*/                 

String pw = (String)getPreference("Credentials");
try {
String encryptedPW =
com.collaxa.cube.util.CXPasswordUtils.encrypt(pw + "||" + getConversationId());
addAuditTrailEntry("Credentials Encrypted");
setVariableData ("startOdiPlan_InputVariable","parameters",
"/ns1:startOdiPlanElement/ns1:CallbackInformationDTO_2/ns1:pw", encryptedPW);
} catch(Exception e) {
e.printStackTrace();
addAuditTrailEntry("Encryption failed: " + e.getMessage());
javax.xml.namespace.QName qname = new
javax.xml.namespace.QName
("http://bpel.oracle.com/", "EncryptionFailure");
throw new com.oracle.bpel.client.BPELFault (qname);
}
addAuditTrailEntry ("Added encrypted credentials successfully");

Double-click the message branch at the extreme left of the Pick activity. In the window that appears, click the Flashlight icon next to the Partner Link field. Expand Process > Partner Links > client. Click OK.

From the Operation drop-down list, select onODIResult. Click the Magic Wand icon next to the Variable field. Name the variable OnMessage_onODIResult and click OK. Click OK in the OnMessage Branch window.

Double-click the remaining (right) message branches of the Pick activity. In the window that appears, click the Flashlight icon next to the Partner Link field. Expand Process > Partner Links > client. Click OK.

From the Operation drop-down list, select onODIError. Click the Magic Wand icon next to the Variable field. Name the variable OnMessage_onODIError and click OK. Click OK in the OnMessage Branch window.

Double-click the onAlarm branch. Change Time from 1 day to 1 hour (or whatever time is appropriate for your load to complete) as shown below. Click OK.

Expand all three branches. From the Components Palette, drag an Assign activity into all the three branches as shown below.

Open Assign_1 in the first (onODIResponse) onMessage branch. Create new copy rules to map the following variables and expressions to the output variable as shown in the following table (refer to the examples of screenshots below).

Click the General tab and name the activity Assign_ODIResponse. Click OK.

Double-click to open Assign_2 in the second (onODIError) onMessage branch. Create new copy rules to map the following variables and expressions to the output variable as shown in the following table. Your Assign_2 activity should look similar to the following screenshot. Click the General tab and name the activity Assign_ODIError. Click OK.

Open the Assign_3 activity in the third onAlarm branch. Create new copy rules to map the following variables and expressions to the output variable as shown in the following table. Your Assign_3 activity should look similar to what is shown below. Click the General tab and name the activity Assign_TimeOut. Click OK.

Verify that your process diagram matches the following image. Click the Validate Process icon at the top of the process diagram to refresh and validate your process. Save your project (File > Save All).

Click the Create icon and select defaultInput from the drop-down list. Click OK.

Copy the the XML code provided below and paste it in the Property Value field. Click OK. Save your project.

Note: The above XML contains details to call a specific ODI scenario SCEN_IMPORTXFORMEXPORTXML, which was created in the OBE titled Developing an ODI XML Transformation That Can Be Executed Within a BPEL Process, in a specific ODI repository (WORKREP). If you are attempting to invoke your own scenario, make sure that you update the values in the above XML to properly represent the details of the ODI scenario. In this case, update the XML values to invoke your ODI scenario and remove the commented section if you are not passing any parameters.

In the logging window at the bottom of the page, click the Apache Ant - Log tab. Verify that Build Successful is displayed in green when the process has finished deploying.

Note: If you see any errors and/or your process fails to deploy, revisit the above steps to correct the errors.

Select your AsyncODICall process in the list of processes at the left. Click the Descriptor tab. On this tab, you can view and set the preferences that you created in the earlier steps. Review and update any of these values if they are not correct.

.

Return to the Initiate tab. From the Operation drop-down list, select initiate. Ensure that your ODI agent is running and your ODI scenario is ready to be invoked. Click the Post XML Message button to start the process. When the page refreshes, click the Visual Flow link to view the process execution.

Click the Invoke_ODI activity to see the synchronous response from ODIInvokerService and verify that it has received the request successfully. Close the Invoke_ODI activity window.

Click the Refresh View link . This refreshes the page to receive the asynchronous callback when the load is complete. Open the callbackClient activity to see the result of the execution. Open ODI Operator and verify that your ODI scenario was invoked and successfully completed.