| Oracle® Fusion Middleware Tutorial for Running and Building an Application with Oracle SOA Suite 11g Release 1 (11.1.1) Part Number E10275-02 |
|
|
View PDF |
| Oracle® Fusion Middleware Tutorial for Running and Building an Application with Oracle SOA Suite 11g Release 1 (11.1.1) Part Number E10275-02 |
|
|
View PDF |
This chapter describes how to create the first half of the OrderProcessor BPEL process for the OrderBookingComposite composite. This chapter assumes you have performed all the tasks from Chapter 3 through Chapter 4.
This chapter contains the following sections:
Section 5.1, "Overview of Tasks for Creating the First Half of OrderProcessor"
Section 5.2, "Copying Services Used by the OrderProcessor BPEL Process"
Section 5.4, "Wiring the OrderProcessor BPEL Process to the StoreFrontService Service"
Section 5.7, "Creating the Scope_RetrieveCustomerForOrder Scope"
Section 5.8, "Creating CreditCardAuthorizationService Service"
Section 5.10, "Creating Catch Branches for the Scope_AuthorizeCreditCard"
Section 5.11, "Creating the RequiresApprovalRule Business Rule"
Section 5.12, "Adding the Switch_ApprovalRequired Switch to the Scope_CheckApprovalLimit Scope"
Table 5-1 lists and describes the tasks for creating the first half of the OrderProcessor BPEL process for the OrderBookingComposite composite.
Table 5-1 Tasks for Creating the First Half of the OrderProcessor BPEL Process for OrderBookingComposite
| Task | Description | See |
|---|---|---|
|
Copy Services Used by the |
Copy the service definitions you reference later during the modification of the |
|
|
Add the |
Reference the |
|
|
Wire the |
Connect |
|
|
Create the |
Create variable |
|
|
Create the |
Create the |
|
|
Create the |
Create the |
|
|
Create |
Reference the |
|
|
Create the Scope_ |
Create the |
|
|
Create Catch Branches for the |
Add catch branches to the |
|
|
Create the |
Create a business rule activity to specify the Another activity uses the output from the business rule to either automatically approve the order or use a human task to obtain manager approval. |
|
|
Create the |
For an order that requires manual approval because the order total is $2,000 or more, you create the |
Copy the service definitions you reference later during the modification of the OrderProcessor BPEL process:
Copy directory services from DEMO_DOWNLOAD_HOME\CompositeServices\OrderBookingComposite to directory MY_FOD_HOME\CompositeServices\OrderBookingComposite.
In the Application Navigator, select OrderBookingComposite and then click the Refresh icon.
The OrderBookingComposite folder in Oracle JDeveloper updates with the services folder.
The StoreFrontService service contains order and customer information. Perform the following tasks to reference this synchronous service:
To copy the WSDL for the StoreFrontService service:
To create a Web service for the StoreFrontService service:
Click the composite.xml tab to view the SOA Composite Editor again.
From the Component Palette, drag a Web Service from the Service Adapters list into the right swim lane (External References) of the SOA Composite Editor.
The Create Web Service dialog appears.
Enter and select the following values:
Accept the other defaults, and then click OK.
The StoreFrontService service displays in the SOA Composite Editor.
If you receive an error, then it is likely you did not add the BC4J Runtime Service library the OrderBookingComposite project. See Section 4.3.3 to add the library.
To wire (connect) the StoreFrontService service to the OrderProcessor BPEL service component:
Drag a wire from the OrderProcessor BPEL process interface to the StoreFrontService reference handle.
Click Source at the bottom of the visual editor to review the wiring:
<wire> <source.uri>OrderProcessor/StoreFrontService</source.uri> <target.uri>StoreFrontService</target.uri> </wire>
Click Design at the bottom of the visual editor.
Click the OrderProcessor.bpel tab to view the BPEL process again.
The StoreFrontService service displays in the BPEL Designer.
Select Save All from the File main menu to save your work.
In this task, you create variable gOrderInfoVariable as input for when an order is placed. The letter g is used to distinguish this variable as a global variable that can be used throughout the BPEL process. This tutorial requests that you create global variables with a letter g prefix and local variables for individual scopes with a letter l prefix. You can use a local variable only within a scope.
In previous releases, variables and messages exchanged within a BPEL business process were disconnected payload (a snapshot of data returned by a Web service) placed into an XML structure. In some cases, the user required this type of fit. In other cases, this fit presented challenges.
For this release, the entity variable can be used with an Oracle ADF Business Component data provider service using SDO-based data.
To create an entity variable for the purchase order ID and select the StoreFrontService as a partner link to invoke the Oracle ADF Business Component application:
In the canvas workspace for the OrderProcessor BPEL process, click the Variables icon.
The Variables dialog displays.
Click the Create icon to add a variable.
The Create Variable dialog displays.
In the Name field, enter gOrderInfoVariable. Use the letter g to distinguish this variable as a global variable that can be used throughout the process.
In the Type section, select Element and then select the Search icon to the right of the Element field.
The Type Chooser dialog appears with a list of available services.
Expand Project Schema Files > OrderInfoVOSDO.xsd > orderInfoVOSDO.
OrderId represents the order in the Oracle ADF Business Component of the StoreFrontService.
Select orderInfoVOSDO, and then click OK.
In the Create Variable dialog, click the Entity Variable check box and select the Search icon to the right of the Partner Link field.
The Partner Link Chooser window displays.
Expand Process > Partner Links and select StoreFrontService, and then click OK.
The Create Variable dialog shows the element and service information.
Click OK in the Create Variable dialog.
The Variables dialog updates with the gOrderInfoVariable entity variable.
Click OK in the Variables dialog.
The Scope_RetrieveOrder scope uses a bind entity activity to obtain the order ID using the gOrderInfoVariable entity variable.
A scope activity does not actually execute or do anything, it simply holds other activities. Scopes are analogous to curly braces in Java. You can use them to break up your process into logical chunks.
To create this scope, perform these tasks:
To create the Scope_RetrieveOrder scope:
From the Component Palette, drag a Scope activity below the receiveInput activity.
Rename this activity by double-clicking the name underneath the icon. Do not double-click the activity icon itself.
Click the Expand (+) icon to expand the Scope_RetrieveOrder scope.
To create a key to point to the data in the Oracle ADF Business Component data provider service:
From the Component Palette, drag a Bind Entity activity into the Scope_RetrieveOrder scope.
Double-click the Bind Entity activity.
The Bind Entity window displays.
In the Name field, enter findOrderById.
Click the Search icon next to the Entity Variable field.
The Browse Variables dialog appears.
Select the gOrderInfoVariable variable you created in Section 5.5, and then click OK.
In the Unique Keys section of the Bind Entity window, click the Create icon to create a key for retrieving the order ID from the database.
The Specify Key dialog appears.
Configure the following settings to define the binding key:
| Element | Procedure |
|---|---|
| Key Local Part |
|
| Key Namespace URI | Leave the default for the namespace URI for the key. |
| Key Value |
|
Click OK to close the Specify Key dialog.
A name-pair value appears in the Unique Keys table.
Click OK to close the Bind Entity window.
When the bind entity activity is executed at run time, the gOrderInfoVariable entity variable is ready to be used. Otherwise, a run-time fault results.
Click the Collapse (-) icon to minimize the Scope_RetrieveOrder scope.
The Scope_RetrieveCustomerForOrder scope calls the StoreFrontService service to retrieve customer information. It assigns the customer ID from global variable gOrderInfoVariable to local variable lFindCustomerInfo_InputVariable for the scope. The scope then uses an invoke activity to call the StoreFrontService service. The invoke activity provides the lFindCustomerInfo_InputVariable variable as input to the service, and the StoreFrontService service returns information about the customer, such as the customer name and email address, back to the BPEL process through the gCustomerInfoVariable global variable.
Figure 5-2 Scope_RetrieveCustomerForOrder
To create this scope, perform the following tasks:
To create the Scope_RetrieveCustomerForOrder scope:
From the Component Palette, drag a Scope activity below the Scope_RetrieveOrder activity.
Rename this activity by double-clicking the name underneath the icon. Do not double-click the activity icon itself.
In the edit field, change the name to Scope_RetrieveCustomerForOrder.
Click the Expand (+) icon to expand the Scope_RetrieveCustomerForOrder scope.
An invoke activity invokes a service and passes it data, and in this case, wait for a response from the service with the return data. To call the StoreFrontService service, you create an invoke activity:
From the Component Palette, drag an Invoke activity into the Scope_RetrieveCustomerForOrder scope.
Rename this activity by double-clicking name underneath the icon. Do not double-click the invoke icon itself.
In the edit field, change the name to InvokeFindCustomer.
Drag the mouse from the right side of InvokeFindCustomer to the StoreFrontService partner link.
The Edit Invoke dialog appears and is automatically filled in with the following information:
| Element | Value |
|---|---|
| Name | InvokeFindCustomer |
| Partner Link | StoreFrontService |
| Operation | findCustomerInfoV01
You change the value for this field in the next step. |
In the Operation field, change the selection to findCustomerInfoVO1CustomerInfoVOCriteria.
Click the Automatically Create Input Variable icon. It is the first icon to the right of the Input Variable field.
The Create Variable dialog appears for the input variable. This variable provides input data to the StoreFrontService service, namely the ID of the customer.
Enter and select the following values:
| Element | Value |
|---|---|
| Name | lFindCustomerInfo_InputVariable
Use the letter |
| Global Variable/Local Variable | Local Variable, because this variable is not needed for other scopes in the process |
Click OK to close the Create Variable dialog.
The Edit Invoke dialog populates with the variable in the Input Variable field.
Click the Automatically Create Output Variable icon. It is the first icon to the right of the Output Variable field.
The Create Variable dialog appears for the output variable. This variable provides output data to the StoreFrontService service, such as the customer's ID, name, contact information, and membership information.
Enter and select the following values:
| Element | Value |
|---|---|
| Name | gCustomerInfoVariable
Use the letter |
| Global Variable/Local Variable | Global Variable, because other scopes in the process use this variable |
Click OK to close the Create Variable dialog.
The Edit Invoke dialog populates with the variable in the Output Variable field.
In the Edit Invoke dialog, click OK to save the variable settings.
In this task, you create an assign activity to take the customer ID and send it to the input variable for the StoreFrontService service.
From the Component Palette, drag an Assign activity above the InvokeFindCustomer invoke activity.
Rename this activity by double-clicking name underneath the icon. Do not double-click the assign icon itself.
In the edit field, enter AssignCustomerId.
Double-click the AssignCustomerId activity.
The Assign dialog displays.
From the dropdown list, select Copy Operation:
The Create Copy Operation dialog appears.
On the From side, expand Variables > gOrderInfoVariable > ns4:orderInfoVOSDO > ns4:CustomerId. The namespace number values (for example, ns1, ns2) can vary.
On the To side, expand Scope - Scope_RetrieveCustomerForOrder > Variables > lFindCustomerInfo_InputVariable > parameters > ns4:findCustomerInfoVO1CustomerInfoVOCriteria and select ns4:CustId. The namespace number value can vary.
Click OK to close the Create Copy Operation dialog.
The Copy Operation tab in the Assign updates to show the operation you created.
In the Assign dialog, click OK.
Click the Collapse (-) icon to minimize the Scope_RetrieveCustomerForOrder scope.
Select Save All from the File main menu to save your work.
To deploy the OrderBookingComposite composite:
In the Application Navigator, right-click OrderBookingComposite and select Deploy > OrderBookingComposite > to MyAppServerConnection. You created the MyAppServerConnection connection in Section 1.2.4, "Task 4: Create a Connection to an Oracle WebLogic Server."
The SOA Deployment Configuration Dialog displays.
Accept the default settings and click OK.
When prompted with the Authorization Request dialog, enter weblogic in the Username field and the password in the Password field.
In SOA - Log, a series of validations display, followed by:
BUILD SUCCESSFUL Total time: nn seconds
To initiate a test instance of the OrderBookingComposite composite, you must deploy a service using the StoreFrontService.wsdl. If you performed the tasks in Section 2.1.2 and have the Store Font module currently running, then you can use it to test the OrderBookingComposite composite. You can proceed to Section 5.7.6, "Task 6: Initiate a Test Instance for the OrderBookingComposite Composite." If you do not have the Store Front module currently running, then deploy the OrderSDOComposite composite, available from the sample application.
To deploy the OrderSDOComposite composite:
In the Application Navigator, select WebLogicFusionOrderDemo for the sample application in the DEMO_DOWNLOAD_HOME directory.
In the Application Navigator, right-click OrderSDOComposite and select Deploy > OrderSDOComposite > to MyAppServerConnection.
The SOA Deployment Configuration Dialog displays.
Accept the default settings and click OK.
When prompted with the Authorization Request dialog, enter weblogic in the Username field and the password in the Password field.
In SOA - Log, a series of validations display, followed by:
BUILD SUCCESSFUL Total time: nn seconds
In the Application Navigator, select WebLogicFusionOrderDemo for the application you currently building in the MY_FOD_HOME directory.
In this task, you can initiate a test instance of the OrderBookingComposite composite in one of two ways:
You can use the Store Front module by submitting an order, similarly to the first order described in Section 2.2 and monitor the order instance described in Section 2.4. The order should progress through the Scope_RetrieveCustomerForOrder scope.
Use the OrderSDOComposite composite by initiating a test instance of the OrderSDOComposite composite from the Test Web Service page in Fusion Middleware Control. Use the steps described next.
To initiate a test instance of the OrderSDOComposite composite:
Access the Test Web Service page in Fusion Middleware Control through the following options:
| From the SOA Infrastructure Menu... | From the SOA Folder in the Navigator... | From the SOA Composite Menu... |
|---|---|---|
|
Select Test Service > orderprocessor_client_ep. |
In the Inputs Arguments section of the Test Web Service page, in the orderID field, enter an ID under 1000.
Click Test Web Service.
The test results appear in the Response tab upon completion.
Click Launch Message Flow Trace to access the flow trace of the instance.
In the Flow Trace window, in the Trace section, click the OrderProcessor BPEL process.
In the Flow Trace window for the instance, click the Flow tab.
Click the various activities to see the flow through the Scope_RetrieveCustomerForOrder scope.
Click X or Close to the dismiss the Activity Details dialog.
Close the Flow Trace window.
The CreditAuthorizationService service checks whether the customer's credit card is valid. You create it by creating a Web service based on a WSDL from the FusionOrderDemo_R1.zip.
Task 1: Copy WSDL File Needed for CreditCardAuthorizationService
Task 2: Create a Web Service for CreditCardAuthorizationService
Later, in Section 5.8, "Creating CreditCardAuthorizationService Service," you create a scope for the OrderProcessor BPEL process to call this service.
Copy CreditCardAuthorizationService.wsdl from directory DEMO_DOWNLOAD_HOME\CompositeServices\OrderBookingComposite to directory MY_FOD_HOME\CompositeServices\OrderBookingComposite.
In Section 5.3.2, "Task 2: Create a Web Service for StoreFrontService," you created a reference to the Web service from the SOA Composite Editor. In this task, you create the reference from the BPEL Designer.
To create a Web service for the CreditCardAuthorizationService service:
From the Component Palette, drag a Partner Link (Web Service/Adapter) from the BPEL Services list into the right swim lane of the BPEL Designer.
The Create Partner Link dialog appears.
Enter and select the following values:
| Element | Value |
|---|---|
| Name | CreditCardAuthorizationService |
| WSDL file | Browse and select CreditAuthorizationService.wsdl from MY_FOD_HOME\OrderBookingComposite. |
| Partner Link Type | Leave the default as CreditCardAuthorizationService. |
| Partner Role | CreditAuthorizationPort |
| My Role | Leave the default as Not Specified, since this service is synchronous |
Click OK.
The CreditCardAuthorizationService service displays in the right swim lane.
If you click the composite.xml tab, you can see the CreditCardAuthorizationService service automatically propagates to the SOA Composite Editor.
The Scope_AuthorizeCreditCard scope calls the CreditCardAuthorizationService service to retrieve customer information. It assigns the order total, credit card type, and the account number from global variable gOrderInfoVariable to local variable lCreditCardInput for the scope. The scope then uses an invoke activity to call the CreditCardAuthorizationService service. The invoke activity provides the lCreditCardInput variable as input to the service, and the CreditCardAuthorizationService service returns the status back to the BPEL process through the lCreditCardCardOutput local variable. This switch activity checks the results of the credit card validation.
To create this scope, perform the following tasks:
To create the Scope_AuthorizeCreditCard scope:
Back in the OrderProcessor.bpel tab, from the Component Palette, drag a Scope activity from the Component Palette section below the Scope_RetrieveCustomerForOrder scope.
Rename this activity by double-clicking the name underneath the icon. Do not double-click the activity icon itself.
In the edit field, change the name to Scope_AuthorizeCreditCard.
Click the Expand (+) icon to expand the Scope_AuthorizeCreditCard scope.
To create an invoke activity to call CreditCardAuthorizationService service:
From the Component Palette, drag an Invoke activity into the Scope_AuthorizeCreditCard scope.
Rename this activity by double-clicking name underneath the icon. Do not double-click the invoke icon itself.
In the edit field, change the name to InvokeCheckCreditCard.
Drag the mouse from the right side of InvokeCheckCreditCard to the CreditCardAuthorizationService partner link.
The Edit Invoke dialog appears and is automatically filled in with the following information:
| Element | Value |
|---|---|
| Name | InvokeCheckCreditCard |
| Partner Link | CreditCardAuthorizationService |
| Operation | AuthorizeCredit |
Click the Automatically Create Input Variable icon. It is the first icon to the right of the Input Variable field.
The Create Variable dialog appears for the input variable. This variable provides input data to CreditCardAuthorizationService service.
Enter and select the following values:
| Element | Value |
|---|---|
| Name | lCreditCardInput |
| Global Variable/Local Variable | Local Variable. |
Click OK to close the Create Variable dialog.
The Edit Invoke dialog populates with the variable in the Input Variable field.
Click the Automatically Create Output Variable icon. It is the first icon to the right of the Output Variable field.
The Create Variable dialog appears for the output variable. This variable returns status from CreditCardAuthorizationService service.
Enter and select the following values:
| Element | Value |
|---|---|
| Name | lCreditCardOutput |
| Global Variable/Local Variable | Local Variable |
Click OK to close the Create Variable dialog.
The Edit Invoke dialog populates with the variable in the Output Variable field.
In the Edit Invoke dialog, click OK to save the settings.
Next, you create an assign activity to take the credit card type, credit card number, and purchase amount and assign it to the input variable for the CreditAuthorizationService service.
Create an assign activity to assign data to the input variables for the CreditCardAuthorizationService service:
From the Component Palette, drag an Assign activity above the InvokeCheckCreditCard invoke activity.
Rename this activity by double-clicking name underneath the icon. Do not double-click the assign icon itself.
In the edit field, enter Assign_CreditCheckInput.
Double-click the Assign_CreditCheckInput activity.
The Assign dialog displays.
Assign an input variable for the purchase amount to the CreditCardAuthorizationService service:
From the dropdown list, select Copy Operation.
The Create Copy Operation dialog appears.
Select the following values:
| Element | Value |
|---|---|
| From | |
|
Variable |
|
Expand Variables > gOrderInfoVariable > ns4:orderInfoVOSDO and select ns4:OrderTotal.
Note: The namespace number values (for example, ns1, ns2) can vary. |
| To | |
|
Variable |
|
Expand Scope - Scope_AuthorizeCreditCard > Variables > lCreditCardInput > Authorization > ns8:AuthInformation and select ns8:PurchaseAmount. |
Click OK to close the Create Copy Operation dialog and return to the Assign dialog.
The Copy Operation tab in the Assign dialog updates to show the copy operation.
Assign an input variable for the type of credit card to the CreditCardAuthorizationService service:
From the dropdown list, select Copy Operation.
The Create Copy Operation dialog appears.
Select the following values:
| Element | Value |
|---|---|
| From | |
|
Variable |
|
Expand Variables > gOrderInfoVariable > ns4:orderInfoVOSDO and select ns4:CardTypeCode.
Note: The namespace number values (for example, ns1, ns2) can vary. |
| To | |
|
Variable |
|
Expand Scope - Scope_AuthorizeCreditCard > Variables > lCreditCardInput > Authorization > ns8:AuthInformation and select ns8:CCType. |
Click OK to close the Create Copy Operation dialog and return to the Assign dialog.
The Copy Operation tab in the Assign dialog updates to show the copy operation.
Assign an input variable for the credit card account number to the CreditCardAuthorizationService service:
From the dropdown list, select Copy Operation.
The Create Copy Operation dialog appears.
Select the following values:
| Element | Value |
|---|---|
| From | |
|
Variable |
|
Expand Variables > gOrderInfoVariable > ns4:orderInfoVOSDO > ns4:AccountNumber.
Note: The namespace number values (for example, ns1, ns2) can vary. |
| To | |
|
Variable |
|
Expand Scope - Scope_AuthorizeCreditCard > Variables > lCreditCardInput > Authorization > ns8:AuthInformation and select ns8:CCNumber. |
Click OK to close the Create Copy Operation dialog and return to the Assign dialog.
The Copy Operation tab in the Assign dialog updates to show three copy operations.
In the Assign dialog, click OK.
Select Save All from the File main menu to save your work.
To create the switch activity to check the results of the credit card validation:
From the Component Palette, drag a Switch activity below the InvokeCheckCreditCard invoke activity.
Rename this activity by double-clicking name underneath the icon. Do not double-click the assign icon itself.
In the edit field, enter Switch_EvaluateCCResult.
Click the Expand (+) icon to expand the switch.
Specify the conditions for the <case> branch to handle cases where a customer's credit card is not valid. This information is stored in the lCreditCardOuput variable.
Double-click the title bar of the <case> box to display the Switch Case dialog.
In the Switch Case dialog, click the XPath Expression Builder icon above the Expression box to display the Expression Builder dialog.
In the Expression Builder dialog, in the BPEL Variables box, select Scope - Scope_AuthorizeCreditCard > Variables > lCreditCardOuput > status and select ns8:status. The namespace number values (for example, ns1, ns2) can vary.
The Content Preview box shows what to insert. For example:
bpws:getVariableData('lCreditCardOutput','status','/ns8:status')
Click Insert Into Expression.
The Expression box updates with the three parameters.
Append != 'APPROVED' to the expression in the Expression box so that the expression looks like this:
bpws:getVariableData('lCreditCardOutput','status','/ns6:status') != 'APPROVED'
Click OK to close the Expression Builder.
In the Switch Case dialog, click OK.
Remove the unneeded <otherwise> branch.
Right-click the <otherwise> branch and select Delete from the menu.
When prompted to remove the branch, click Yes.
Create the Throw activity in the remaining <case> branch.
For those orders not approved, this activity throws a fault called Throw_Fault_CC_Denied. The OrderProcessor process terminates after executing this throw activity.
From the Component Palette, drag a Throw activity into the <case> branch.
Double-click the new throw activity.
The Throw activity dialog displays.
Enter the following values:
| Element | Value |
|---|---|
| Name | Throw_Fault_CC_Denied |
| Namespace | http://www.globalcompany.example.com/ns/OrderBookingService |
| Local Part | OrderProcessorFault |
| Fault Variable | Do not enter a value. |
Click OK.
Click the Collapse (-) icon to minimize the switch.
Select Save All from the File main menu to save your work.
Add catch branches to the Scope_AuthorizeCreditCard scope for orders in which the credit card number is not provided or the credit type is not valid. Figure 5-4 shows the catches for the scope.
Figure 5-4 Catches in Scope_AuthorizeCreditCard
To create the catches for this scope, perform the following tasks:
You create the gOrderProcessorFaultVariable variable as input for the branches in the next task. This variable uses the OrderProcessorFault element from the OrderProcessor.wsdl file, which you must create in the OrderProcessor.wsdl file.
To create this variable:
From the Application Navigator, double-click OrderProcessor.wsdl.
The WSDL Editor displays, which is a specialized schema-driven editor for editing WSDL documents.
Click the Source tab and add the following definition to the wsdl:definitions section.
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
Click the Design tab.
Create the OrderProcessorFault message:
Click the Expand (+) icon in the Messages section.
Click the Add icon to add a new message.
The Create Message dialog displays.
In the Message Name field, enter OrderProcessorFault, and then click OK.
Select OrderProcessorFault in Messages.
Select OrderProcessorFault and then select part in the right side WSDL component palette.
The Create Part dialog displays.
Enter and select following values:
| Element | Value |
|---|---|
| Part Name | code |
| Reference Type | type |
| Part Name | xsd:string |
Click OK in the Create Part dialog.
Select OrderProcessorFault and then select part in the right side of WSDL component palette.
The Create Part dialog displays.
Enter and select the following values:
| Element | Value |
|---|---|
| Part Name | orderId |
| Reference Type | type |
| Part Name | xsd:string |
Click OK in the Create Part dialog.
Select OrderProcessorFault and then select part in the right side WSDL component palette.
The Create Part dialog displays.
Enter and select the following values:
| Element | Value |
|---|---|
| Part Name | summary |
| Reference Type | type |
| Part Name | xsd:string |
Click OK in the Create Part dialog.
The Messages section displays the parts for the OrderProcessorFault message.
Create the processFault operation for OrderProcessorCallback:
In the Port Types section, select OrderProcessorCallback and then select operation in the right side WSDL component palette.
The Create Operation dialog displays.
Enter and select the following values:
| Element | Value |
|---|---|
| Operation Name | processFault |
| Operation Type | Request Response |
| Input | client:OrderProcessorFault |
| Output | client:OrderProcessorResponseMessage |
Click OK in the Create Operation dialog.
In the Port Types section, expand OrderProcessorCallback and processFault.
Right-click the unneeded output in processFault and select Delete.
Expand processFault > input > OrderProcessorFault > OrderProcessor to see the parts.
Select Save All from the File main menu to save your work.
Click X in the OrderProcessor.wsdl tab to close the WSDL Editor.
You now create the gOrderProcessorFaultVariable variable as input for the branches in the next task.
To create this variable:
In the workspace for the OrderProcessor BPEL process, click the Variables icon.
The Variables dialog displays.
Click the Add icon to add a variable.
The Create Variable dialog displays.
In the Name field, enter gOrderProcessorFaultVariable.
In the Type section, select Message Type and then select the Browse icon to the right of the Message Type field.
The Type Chooser dialog appears with a list of available services.
Expand Message Types > Project WSDL Files > OrderProcessor.wsdl > Message Types and select OrderProcessorFault, which you added to the WSDL file in Section 5.10.2, "Task 2: Create the gOrderProcessorFaultVariable Variable."
Click OK to close the Type Chooser dialog.
In the Create Variables dialog, click OK.
The Variables dialog updates with the gOrderProcessorFault variable.
Click OK in the Variables dialog.
To add catches to the Scope_AuthorizeCreditCard scope:
Click the Add Catch Branch icon for the scope, as shown in the following figure:
Double-click the catch to display the Catch dialog.
In the Fault QName section, click the Browse icon.
In the Fault Chooser dialog, expand System Faults and select selectionFailure, and then click OK. This catch provides a built-in system fault. It is raised from the Assign_CreditCheckInput activity if any of the fields are blank, such as no account number.
Click OK in the Catch dialog.
Click the Expand (+) icon to expand the selectionFailure catch.
In the selectionFailure catch, create an assign activity to assign expression 'CreditCardCheck - NO CreditCard' as input to global variable gOrderProcessorFaultVariable for orders without credit card numbers.
From the Component Palette, drag an Assign activity into the branch.
Rename this activity by double-clicking name underneath the icon. Do not double-click the assign icon itself.
In the edit field, enter Assign_noCCNumber.
Double-click Assign_noCCNumber.
The Assign dialog displays.
From the dropdown list, select Copy Operation.
The Create Copy Operation dialog appears.
Enter and select the following values:
| Element | Value |
|---|---|
| From | |
|
Expression |
|
string('CreditCardCheck - NO CreditCard')
|
| To | |
|
Variable |
|
Expand Variables > gOrderProcessorFaultVariable and select code. You created this variable in Section 5.10.2, "Task 2: Create the gOrderProcessorFaultVariable Variable." |
Click OK to close the Create Copy Operation dialog and return to the Assign dialog.
The Copy Operation tab in the Assign dialog updates to show the copy operation.
In the Assign dialog, click OK.
In the selectionFailure catch, insert a throw activity after assign activity Assign_noCCNumber, so the Scope_AuthorizeCreditCard scope throws a fault:
From the Component Palette, drag a Throw activity below Assign_noCCNumber.
Double-click the new throw activity.
The Throw activity dialog displays.
Enter the following values:
| Element | Value |
|---|---|
| Name | Throw_NoCreditCard |
| Namespace | http://www.globalcompany.example.com/ns/OrderProcessor |
| Local Part | OrderProcessorFault |
Click the Browse Fault Variables icon next to the Fault Variable field.
In the Variable Chooser dialog, select the gOrderProcessFaultVariable and click OK.
Back in the Throw dialog, click OK.
Click the Collapse (-) icon to minimize the catch.
Click the Add Catch Branch icon for the scope to create a second catch.
Double-click the new catch to display the Catch dialog.
Enter the following values:
| Element | Value |
|---|---|
| Namespace | http://www.globalcompany.example.com/ns/CreditCardAuthorizationService |
| Local Part | InvalidCredit |
Click OK in the Catch dialog.
Click the Expand (+) icon to expand the InvalidCredit catch.
In the InvalidCredit catch, assign data to take the credit card type and assign it to global variable gOrderProcessorFaultVariable for orders without a valid credit card type.
From the Component Palette, drag an Assign activity into the branch.
Rename this activity by double-clicking name underneath the icon. Do not double-click the assign icon itself.
In the edit field, enter Assign_InvalidCreditFault.
Double-click Assign_InvalidCreditFault.
The Assign dialog displays.
From the dropdown list, select Copy Operation.
The Create Copy Operation dialog appears.
Enter and select the following values:
| Element | Value |
|---|---|
| From | |
|
Expression |
|
|
| To | |
|
Variable |
|
Expand Variables > gOrderProcessorFaultVariable and select summary. |
Click OK to close the Create Copy Operation dialog and return to the Assign dialog.
The Copy Operation tab in the Assign dialog updates to show the copy operation.
In the InvalidCredit catch, assign data expression 'CreditCardCheck - NOT VALID' to global variable gOrderProcessorFaultVariable.
From the dropdown list in the Assign dialog, select Copy Operation.
The Create Copy Operation dialog appears.
Enter and select the following values:
| Element | Value |
|---|---|
| From | |
|
Expression |
|
string('CreditCardCheck - NOT VALID')
|
| To | |
|
Variable |
|
Expand Variables > gOrderProcessorFaultVariable and select code. |
Click OK to close the Create Copy Operation dialog and return to the Assign dialog.
The Copy Operation tab in the Assign dialog updates to show the copy operation.
In the Assign dialog, click OK.
In the InvalidCredit catch, insert a throw activity after assign activity Assign_InvalidCreditFault, so the Scope_AuthorizeCreditCard scope throws a fault:
From the Component Palette, drag a Throw activity below Assign_InvalidCreditFault.
Double-click the new throw activity.
The Throw activity dialog displays.
Enter the following values:
| Element | Value |
|---|---|
| Name | Throw_OrderProcessingFault |
| Namespace | http://www.globalcompany.example.com/ns/OrderProcessor |
| Local Part | OrderProcessorFault |
Click the Browse Fault Variables icon next to the Fault Variable field.
In the Variable Chooser dialog, select the gOrderProcessFaultVariable and click OK.
Click OK in the Throw dialog.
Click the Collapse (-) icon to minimize the catch.
Click the Collapse (-) icon to minimize the Scope_AuthorizeCreditCard scope.
Select Save All from the File main menu to save your work.
You create a business rule activity to specify the RequiresApprovalRule business rule. This rule specifies that if the order total is $2,000 or more, then a manager's approval is required.
Another activity uses the output from the business rule to either automatically approve the order or use a human task to obtain manager approval.
When you add a business rule activity to a BPEL process, you can create input and output variables to provide input to the business rule activity, and to obtain results from the business rule activity.
To use business rules with Oracle JDeveloper, you perform the following:
Add a business rule activity to the BPEL process
Create input and output variables in the BPEL process
Create an Oracle Business Rules dictionary in the project
If you want, you can associate a business rule service component created in the SOA Composite Editor with a BPEL process service component. You create this association with the business rule activity of the BPEL process. This activity creates a business rule partner link. This activity also enables you to create copy operation assignments between the fact data in your rule set and BPEL variables. When complete, a business rule activity is created that consists of assign and invoke activities to the business rule partner link.
To create the RequiresApprovalRule business rule, perform the following tasks:
Section 5.11.1, "Task 1: Create Scope_CheckApprovalLimit Scope"
Section 5.11.3, "Task 3: Create the Assign_DefaultNotRequiresApproval Assign Activity"
Section 5.11.4, "Task 4: Create the RequiresApprovalRule Business Rule"
Section 5.11.5, "Task 5: Reference the RequiresApprovalRule Dictionary in the BPEL Designer"
Section 5.11.6, "Task 6: Define a Variable in Rules Designer"
Section 5.11.7, "Task 7: Add a New Rule for the Ruleset in Rules Designer"
Section 5.11.8, "Task 8: Redeploy the OrderBookingComposite Composite"
Section 5.11.9, "Task 9: Initiate a Test Instance for the OrderBookingComposite Composite"
The Scope_CheckApprovalLimit scope invokes the RequiresApprovalRule business rule, as shown in Figure 5-5.
Figure 5-5 Scope_CheckApprovalLimit Scope
To add the scope:
From the Component Palette, drag a Scope activity below the Scope_AuthorizeCreditCard scope.
Rename this activity by double-clicking the name underneath the icon. Do not double-click the activity icon itself.
In the edit field, change the name to Scope_CheckApprovalLimit.
Click the Expand (+) icon to expand the Scope_CheckApprovalLimit scope.
In this task, you create local variable lOrderApproved variable, which provides input to a business rule variable.
To create this variable:
In the workspace for the Scope_CheckApprovalLimit scope, click the Variables icon.
The Variables dialog displays.
Click the Add icon to add a variable.
The Create Variable dialog displays.
In the Name field, enter lOrderApproved.
In the Type section, select Simple Type and then select the Browse XML Schema Types icon to the right of the field.
The Type Chooser dialog appears with a list of available services.
Select string under XML Schema Simple Types.
Click OK in the Type Chooser dialog.
Click OK in the Create Variable dialog.
The Variables dialog updates with the lOrderApproved variable.
Click OK in the Variables dialog.
In this task, you create an assign activity to take the order total and send it to the input variable for the business rule.
To assign an input variable for the purchase price to the business rule:
From the Component Palette, drag an Assign activity into the Scope_CheckApprovalLimit scope.
Rename this activity by double-clicking the name underneath the icon. Do not double-click the assign icon itself.
In the edit field, enter Assign_DefaultNotRequiresApproval.
Double-click the Assign_DefaultNotRequiresApproval activity.
The Assign dialog displays.
From the dropdown list, select Copy Operation:
The Create Copy Operation dialog appears.
Enter and select the following values:
| Element | Value |
|---|---|
| From | |
|
Expression |
|
string('false')
|
| To | |
|
Variable |
|
Expand Scope - Scope_CheckApprovalLimit > Variables and select lOrderApproved, which is the variable you created in Section 5.11.2, "Task 2: Add the lOrderApproved Variable." |
Click OK to close the Create Copy Operation dialog and return to the Assign dialog.
The Copy Operation tab in the Assign dialog updates to show the copy operation.
In the Assign dialog, click OK.
Select Save All from the File main menu to save your work.
Click the composite.xml tab to view the SOA Composite Editor.
Drag a Business Rule service component into the SOA Composite Editor.
The Create Business Rule dialog displays.
In the Name field, enter RequiresApprovalRule to be the name of the Oracle Business Rules dictionary.
Leave the default for the Package field.
In the Inputs/Outputs section, from the Add menu, select Input to select the input for the business rule:
The Type Chooser dialog displays.
Import the complete schema located in the DEMO_DOWNLOAD_HOME directory:
Click the Import Schema File icon.
The Import Schema File dialog displays.
Select File System and in the Location section, browse for OrderBookingRules.xsd in DEMO_DOWNLOAD_HOME/CompositeServices/OrderBookingComposite/xsd and click OK.
In the Import Schema dialog, ensure the OrderBookingRules.xsd now displays in the URL field and the Copy to Project option is selected, and then click OK.
The Localized Files dialog displays, prompting you to import the OrderBookingRules.xsd schema file.
Deselect the Maintain original directory for imported files option and click OK to import the file.
The Type Chooser dialog displays.
Select the input for the business rule:
In the Type Chooser dialog, expand OrderBookingRules.xsd and select approve.
Click OK to return to the Create Business Rules dialog.
In the Inputs/Outputs section, select the output for the business rule:
From the Add menu, select Output.
The Type Chooser dialog displays.
Expand OrderBookingRules.xsd and select approve.
Click OK to return to the Create Business Rules dialog.
Click OK to create the business rule.
The RequiresApprovalRule business rule displays in the composite.
Select Save All from the File main menu to save your work.
Double-click RequiresApprovalRule in the SOA Composite Editor.
Oracle JDeveloper displays the Rules Designer, with the dictionary in the RequiresApprovalRule.rules tab.
For an overview of the Rules Designer, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.
As part of the Business Rule designer, a new rule dictionary is created with the following pre-loaded data:
XML fact type model based on the input and output metadata information of the business rule activity.
A new ruleset that must be completed by adding rules to it.
A new service with the input and output contract of the business rule activity. The service is being invoked from the activity at run time.
A new business rule service component for the rule dictionary. You wire it to the BPEL process in Section 5.11.5, "Task 5: Reference the RequiresApprovalRule Dictionary in the BPEL Designer."
You modify this rule in a later task. Therefore, do not close the tab.
To reference the RequiresApprovalRule in the Scope_CheckApprovalLimit scope:
Click the OrderProcessor.bpel tab.
From the Component Palette, drag a Business Rule activity below the Assign_DefaultNotRequiresApproval activity in the Scope_CheckApprovalLimit scope.
The Business Rule dialog displays.
In the Name field, enter BusinessRule_ApprovalRequired.
From the Dictionary list, select RequiresApprovalRule, which is the rule you created in Section 5.11.4, "Task 4: Create the RequiresApprovalRule Business Rule."
Leave the default settings for the Service and Operation fields.
Create input to the business rule, so that the gOrderInfoVariable and lOrderApproved variables assign data to input variable com_example_globalcompany_ns_orderbookingservice_rules_Approve_i for the business rule.
In the Assign Input Facts tab, click the Create icon.
The Decision Fact Map dialog displays.
Enter and select the following values:
| Element | Value |
|---|---|
| From | |
|
Variable |
|
Expand Variables > gOrderInfoVariable > ns4:orderInfoVOSDO and select ns4:OrderTotal.
Note: The namespace number values (for example, ns1, ns2) can vary. |
| To | |
|
Business Rules Facts |
|
Expand com_example_globalcompany_ns_orderbookingservice_rules_Approve_i > ns10:approve and select ns10:price. |
Click OK.
The copy operation displays in the Assign Input Facts tab of the Business Rule dialog.
In the Assign Input Facts tab, click the Create icon again to create a second assignment.
The Decision Fact Map dialog displays.
Enter and select the following values:
| Element | Value |
|---|---|
| From | |
|
Variable |
|
Expand Scope - Scope_CheckApprovalLimit > Variables and select lOrderApproved.
Note: The namespace number values (for example, ns1, ns2) can vary. |
| To | |
|
Business Rule Facts |
|
Expand com_example_globalcompany_ns_orderbookingservice_rules_Approve_i > ns10:approve and select ns10:approvalRequired. |
Click OK.
The two copy operations display in the Assign Input Facts tab of the Business Rule dialog.
Create output from the business rule, so that the variable com_example_globalcompany_ns_orderbookingservice_rules_Approve_o for the business rule sends data to the lOrderApproved variable for the scope:
Click the Assign Output Facts tab.
In the Assign Output Facts tab, click the Create icon.
The Decision Fact Map dialog displays.
Enter and select the following values:
| Element | Value |
|---|---|
| From | |
|
Business Rule Facts |
|
Expand com_example_globalcompany_ns_orderbookingservice_rules_Approve_o > ns10:approve and select ns10:approvalRequired.
Note: The namespace number values (for example, ns1, ns2) can vary. |
| To | |
|
Variable |
|
Expand Scope - Scope_CheckApprovalLimit > Variables and select lOrderApproved. |
Click OK.
The copy operation displays in the Assign Input Facts tab of the Business Rule dialog.
Click OK in the Business Rules dialog.
Select Save All from the File main menu to save your work.
You define variables in the data model. When you make changes later, you must edit the value of the variable. You create a variable named MAX_PRICE to define the dollar amount where orders above this amount would need manual approval from a manager and orders under this amount are approved automatically. You set the MAX_PRICE variable to $2000.
To create the MAX_PRICE variable:
In the Rules Designer, select the Globals tab.
Click the Create icon to add a new variable entry.
The Edit Variable dialog displays.
In the Name field, enter MAX_PRICE.
In the Description field, enter the following string:
Limit for Automatic Approval
From Type dropdown list, select int.
Do not select any value for Bucketset.
Click the icon next to the Value field.
The Expression Builder dialog displays.
In the Expression area, enter 2000, and then click OK to close the Expression Builder.
In the Edit Variable dialog, click OK.
When you create the rule dictionary, an empty ruleset named Ruleset_1 was created without any rules. In this task, you add the CheckOrderTotalAgainstLimit rule. This rule specifies that if the order is greater than or equal to $2,000, then the order requires manual approval.
To create the rule:
In Rules Designer, select Ruleset_1 from the left menu.
From the Create dropdown list, select Create Rule.
A new rule displays:
Click <insert test> to display the statement template.
In the IF section, click the left-hand operand and select approve.price.
Click the operator and select >=.
Click the right-hand operand and select MAX_PRICE.
In the THEN section, click <insert action> and select modify.
Click <target> and select approve.
Click <add property>.
The Properties dialog displays.
In the approvalRequired row, select true from the Value dropdown menu and click the Constant check box.
Click Close.
The business rule updates and is complete.
Select Save All from the File main menu to save your work.
Click X in the RequiresApprovalRule.rules tab to close the Rules Designer.
To redeploy the OrderBookingComposite composite:
In the Application Navigator, right-click OrderBookingComposite and select Deploy > OrderBookingComposite > to MyAppServerConnection.
The SOA Deployment Configuration Dialog displays.
Select Overwrite any existing composite with the same revision ID to overwrite the composite you deployed in Section 5.7.4, "Task 4: Deploy the OrderBookingComposite Composite."
When prompted with the Authorization Request dialog, enter weblogic in the Username field and the password in the Password field.
In SOA - Log, a series of validations display, followed by:
BUILD SUCCESSFUL Total time: nn seconds
Initiate a test instance of the OrderBookingComposite composite, as you did in Section 5.7.6, "Task 6: Initiate a Test Instance for the OrderBookingComposite Composite." This time, in the Flow Trace window, notice how the order progresses through the Scope_CheckApprovalLimit scope.
For an order that requires manual approval because the order total is $2,000 or more, the SwitchApprovalRequired switch in the ScopeCheckApprovalLimit scope consists of a <case> branch that passes control to the ApprovalHumanTask human task activity, which enables a manager named jstein to approve or reject the orders. For orders that do not require manual approval, this switch does not apply to them.
Figure 5-6 shows the SwitchApprovalRequired switch contains a human task activity and another switch activity to handle the manager's response.
Figure 5-6 Switch_ApprovalRequired Switch with Human Task and Switch
To create the SwitchApprovalRequired switch, perform the following tasks:
Task 3: Create a Human Task in the <case> Branch to Approve an Order
Task 4: Modify TaskSwitch Activity in <case> Branch to Handle Manager's Response
Task 6: Initiate a Test Instance for the OrderBookingComposite Composite
To create the Switch_ApprovalRequired switch:
Click the OrderProcessor.bpel tab.
From the Component Palette, drag a Switch activity from the Component Palette section to below the BusinessRule_ApprovalRequired activity.
Rename this activity by double-clicking the name underneath the icon. Do not double-click the activity icon itself.
In the edit field, change the name to Switch_ApprovalRequired.
Click the Expand (+) icon to expand the Switch_ApprovalRequired scope.
Remove the unneeded <otherwise> branch.
Right-click the <otherwise> branch and select Delete from the menu.
When prompted to remove the branch, click Yes.
The switch looks similar to the one in the following figure:
Select Save All from the File main menu to save your work.
To create the <case> branch:
Double-click the title bar of the <case> box to display the Switch Case dialog.
The Switch Case dialog displays.
In the Name box, enter:
approval required = true
Click the XPath Expression Builder icon above the Expression box to display the Expression Builder dialog.
In the BPEL Variables box, expand Scope - Scope_CheckApprovalLimit > Variables and select lOrderApproved.
lOrderApproved is the variable you defined in Section 5.11.2, "Task 2: Add the lOrderApproved Variable."
The Content Preview box should show the following:
bpws:getVariableData('lOrderApproved')
Click Insert Into Expression. The Expression box displays the function with the one parameter.
Append = 'true' to the expression, starting with a space, in the Expression box so that the expression looks like this:
bpws:getVariableData('lOrderApproved') = 'true'
Click OK in the Expression Builder dialog. The Switch Case dialog now contains the expression.
Click OK in the Switch Case dialog to close it.
Select Save All from the File main menu to save your work.
You modify the <case> branch with two activities, a human task activity and a switch activity). To create these activities, you must create a sequence activity to be the container for these two activities.
To create a human task in the <case> branch:
Drag a Human Task activity into the <case> box.
The Create a Human Task dialog appears.
From the Task Definition list, click the Create icon next to the Task Definition field.
The Create Human Task dialog displays.
Enter and select the following values:
| Element | Value |
|---|---|
| Name | ApprovalHumanTask |
| Priority | Leave the priority set to 3 (Normal). |
| Namespace | http://www.globalcompany.com/ns/OrderBooking/ApprovalHumanTask |
| Title | Do not enter a value for the time being. |
In the Parameters section, select the Add Task Parameter icon.
The Add Task Parameter dialog displays.
Click the icon next to the Source field to launch the Task Parameters page for selecting a parameter source.
Expand Variables > gOrderInfoVariable > ns8:orderInfoVOSDO and select the OrderId key.
Click OK to close the Task Parameters dialog.
Back in the Add Task Parameter dialog, in the Parameter Name field, modify the field to orderId.
Click OK to close the Add Task Parameter dialog and return to the Create Human Task dialog.
In the Create Human Task dialog, click OK.
The Human Task Editor appears.
For an overview of the Human Task Editor, see Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.
In the Title field, enter:
Approval Required for Order Id:
Click the icon to the right of the Title field to select the order ID.
The Expression Builder dialog displays.
From the Schema section, expand task:task > task:payload and select task:orderId.
Click Insert Into Expression.
The Expression box updates with the following expression:
/task:task/task:payload/task:orderId
Click OK to close the Expression Builder.
The ApprovalHumanTask.task pages updates with the following for the title:
Approval Required for Order Id:<%/task:task/task:payload/task:orderId%>>
Specify an approver for the human task:
In the Assignment and Routing Policy section, double-click <no participants>.
The Add Participant Type dialog displays.
In the Label field, enter Approver.
From the dropdown menu in the Participant Names table, select Add User.
A new row displays in the Participant Names table.
Click the Browse icon to the far right of the row.
The Identity Lookup dialog appears.
From the Application Server list, select MyAppServerConnection.
Click the Lookup icon. It is located to the right of the User Name field.
The search results display in the Search User section.
Select jstein and then click Select.
jstein is added to the Selected User section.
Click OK to close the Identity Lookup dialog.
jstein displays in the Participants Names table in the Edit Participant Type dialog.
Click OK in the Add Participant Type dialog.
Approver displays in the Assignment and Routing Policy section of the ApprovalHumanTask.task window.
Select Save All from the File main menu to save your work.
Click X in the ApprovalHumanTask.task tab to close the human task.
Click the composite.xml tab to see the human task.
ApprovalHumanTask displays in the SOA Composite Editor.
Oracle JDeveloper created a switch called taskSwitch for you automatically after the human task activity in the OrderProcessor BPEL process, as shown in Figure 5-7.
Figure 5-7 taskSwitch Activity in the <case> Branch
This switch enables you to define the actions to take depending on whether the manager approved or rejected the order, or if the order has expired.
The switch handles these cases:
The manager rejected the order.
The manager approved the order.
The order has expired.
To modify the switch for these actions:
Click the Expand (+) icon to expand the taskSwitch.
In the <case Task outcome is REJECT> branch, remove the CopyPayloadFromTask activity and replace it with a throw activity.
For those orders not approved, this activity throws a fault called Throw_OrderProcessorFault. The OrderProcessor process terminates after executing the throw activity.
Right-click the CopyPayloadFromTask activity and select Delete from the menu.
When prompted to remove the branch, click Yes.
From the Component Palette, drag a Throw activity into the <case Task outcome is REJECT> branch.
Double-click the new throw activity.
The Throw activity dialog displays.
Enter and select the following values:
| Element | Value |
|---|---|
| Name | Throw_OrderProcessorFault |
| Namespace | http://www.globalcompany.example.com/ns/OrderBookingService |
| Local Part | OrderProcessorFault |
| Fault Variable |
|
Click OK.
In the <case Task outcome is APPROVE> branch, remove the CopyPayloadFromTask activity and replace it with an empty assign activity. the empty assign passed the output from the business to the next scope in the process.
Right-click the CopyPayloadFromTask activity and select Delete from the menu.
When prompted to remove the branch, click Yes.
From the Component Palette, drag an Empty activity into the <case Task outcome is APPROVE> branch.
Rename this activity by double-clicking the name underneath the icon.
In the edit field, remove the name.
In the Assign dialog, click OK.
In the <otherwise> branch, remove the CopyPayloadFromTask activity and replace it with a throw activity.
For those orders not approved, this activity throw a fault called ThrowRejected. The OrderProcessor process terminates after executing the throw activity.
Right-click the CopyPayloadFromTask activity and select Delete from the menu.
When prompted to remove the branch, click Yes.
From the Component Palette, drag a Throw activity into the <otherwise Task> branch.
Double-click the new throw activity.
The Throw activity dialog displays.
Enter and select the following values:
| Element | Value |
|---|---|
| Name | Throw_OrderProcessingFault |
| Namespace | http://www.globalcompany.example.com/ns/OrderBookingService |
| Local Part | OrderProcessorFault |
| Fault Variable |
|
Click OK.
Click the Collapse (-) icon to minimize taskSwitch switch.
Click the Collapse (-) icon to minimize the Scope_CheckApprovalLimit scope.
Select Save All from the File main menu to save your work.
To redeploy the OrderBookingComposite composite:
In the Application Navigator, right-click OrderBookingComposite and select Deploy > OrderBookingComposite > to MyAppServerConnection.
The SOA Deployment Configuration Dialog displays.
Select Overwrite any existing composite with the same revision ID to overwrite the composite you previously deployed.
When prompted with the Authorization Request dialog, enter weblogic in the Username field and the password in the Password field.
In SOA - Log, a series of validations display, followed by:
BUILD SUCCESSFUL Total time: nn seconds
Initiate a test instance of the OrderBookingComposite composite, as you have done previously. See Section 5.7.6, "Task 6: Initiate a Test Instance for the OrderBookingComposite Composite" for further information on creating a test instance. For this test instance, make the following adjustments:
In the Inputs Arguments section, in the orderID field, enter an ID over 1000 to submit an order for over $2000.
In the Flow trace window, scroll toward the bottom of the Scope_CheckApprovalLimit scope to see the ApprovalHumanTask human task was initiated after the business rule.
Proceed with Chapter 6, "Creating the Second Half of the OrderProcessor BPEL Process," to complete the creation of the OrderProcessor BPEL process. After the process is complete, you can create a form for the manager to approve orders in Chapter 9, "Creating the Task Display Form for the ApprovalHumanTask Human Task."
|
 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|