Skip Headers
Oracle® Fusion Middleware Tutorial for Running and Building an Application with Oracle SOA Suite
11g Release 1 (11.1.1)

Part Number E10275-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

2 Running the Sample Application

This chapter describes how to deploy Fusion Order Demo, place an order, and monitor the order as it is processed by the WebLogic Fusion Order Demo application. It explains two different order scenarios for the Web client and how to monitor orders processed through the business flow.

Before following the instructions in this chapter, perform all the procedures in Chapter 1.

This chapter includes the following sections:

2.1 Deploying the Fusion Order Demo Applications

To run the demo, deploy the applications for the Store Front module and the WebLogic Fusion Order Demo application, performing the following tasks:

2.1.1 Task 1: Install the Schema for the Fusion Order Demo Application

To install the schema for the sample application:

  1. Start Oracle JDeveloper 11g and from the main menu choose File > Open.

  2. In the Open dialog, browse to DEMO_DOWNLOAD_HOME/Infrastructure and select Infrastructure.jws. Click Open.

  3. When prompted to migrate files to the 11.1.1.1.0 format, click Yes. When the migration is complete, click OK.

  4. In the Application Navigator, expand MasterBuildScript and then Resources, and double-click build.properties.

  5. In the editor, modify the following properties for your environment:

    Element Value
    jdeveloper.home The root directory where you have Oracle JDeveloper 11g installed. For example:

    C:/JDeveloper/11

    jdbc.urlBase The base JDBC URL for your database in the format jdbc:oracle:thin:@<yourhostname>. For example:

    jdbc:oracle:thin:@foddb-server

    jdbc.port The port for your database. For example:

    1521

    jdbc.sid The SID of your database. For example:

    ORCL or XE

    db.adminUser The administrative user for your database. For example:

    system

    db.demoUser.tablespace The tablespace name for the Fusion Order Demo users. For example:

    USERS


  6. From the JDeveloper main menu, choose File > Save All.

  7. In the Application Navigator, under the Resources node, right-click build.xml and choose Run Ant Target > buildAll.

  8. When prompted, enter the administrative-user password for your database.

    The buildAll command then creates the FOD user and populates the tables in the FOD schema. In the Apache Ant - Log, a series of SQL scripts display, followed by:

    buildAll:
    BUILD SUCCESSFUL
    Total time: nn minutes nn seconds
    

    For more information on the demo schema and scripts, see the README.txt file in the MasterBuildScript project.

2.1.2 Task 2: Deploy the Store Front Module

You place orders by running the home.jspx page in the StoreFrontUI project of the Store Front module. The StoreFrontUI project uses JavaServer Faces (JSF) as the view technology, and relies on the Oracle ADF Model layer to interact with Oracle ADF Business Components in the StoreFrontService project.

Figure 2-1 StoreFrontUI Home Page

Description of Figure 2-1 follows
Description of "Figure 2-1 StoreFrontUI Home Page"

From the home page, you can browse the Web site as an anonymous user, then log in as a registered customer to place an order.

The Fusion Order Demo application ships with predefined customer data. Because the Fusion Order Demo application implements Oracle ADF Security to manage access to Oracle ADF resources, only the authenticated user can view orders in their cart. The following table shows the preregistered customers. You place orders as ngreenbe later in this chapter.

Username Password Application Role
ngreenbe welcome1 Customer (CUST)
sking welcome1 Staff (STAFF)
pbrown welcome1 Supplier (SUPP)

To learn more about the Store Front module and to understand its implementation details, see Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

To deploy the Store Front module:

  1. Choose File > Open.

  2. In the Open dialog, browse to DEMO_DOWNLOAD_HOME/StoreFrontModule and select StoreFrontModule.jws. Click Open.

  3. When prompted to migrate files to the 11.1.1.1.0 format, click Yes. When the migration is complete, click OK.

    The following figure shows the Application Navigator after you open the file for the application workspace.

    TBD
    Description of the illustration storeprojects.gif

  4. Deploy the services used by the Store Front module to send orders to the OrderBookingComposite composite.

    1. In the Application Navigator, right click StoreFrontModule and choose Deploy > StoreFrontModule_SDOServices > to > MyAppServerConnection. You created this connection in Section 1.2.4, "Task 4: Create a Connection to an Oracle WebLogic Server."

    2. In the Select Deployment Targets dialog, select the Managed Server for the Oracle WebLogic Server, such as soa_server, and click OK

    3. In the Deployment Configuration dialog, accept the default MDS repository name and partition name, and then click Deploy.

  5. Deploy the Store Front module. From the Application menu, select Deploy > StoreFrontModule > to > MyAppServerConnection.

2.1.3 Task 3: Deploy the WebLogic Fusion Order Demo Application

To deploy the WebLogic Fusion Order Demo application to an Oracle SOA Suite installation, containing an Oracle WebLogic Server domain with an Administration Server and a Managed Server.

  1. In the Application Navigator, select WebLogicFusionOrderDemo.

  2. Expand bin and then Resources, and double-click build.properties.

  3. In the editor, modify the following properties for your environment:

    Parameter Value
    oracle.home The root directory where you have Oracle JDeveloper 11g installed. For example:

    C:\\Oracle\\Middleware\\jdeveloper\\

    soa.only.deployment false

    You set this property to true if you are using the OrderSDOComposite composite to place orders. This tutorial assumes you are using the Store Front Module to place orders. Therefore, you must modify this property to false.

    admin.server.host The DNS name or IP address of the Administration Server for Oracle SOA Suite for hosting applications. For example:

    soahost

    admin.server.port The port of the Administration Server. For example:

    7001

    managed.server The DNS name or IP address of the Managed Server for Oracle SOA Suite for hosting applications. For example:

    soahost

    managed.server.port The port of the Managed Server for Oracle SOA Suite for hosting applications. For example:

    8001

    server.user The Oracle WebLogic Server administrator. For example:

    weblogic

    server.password The password of the Oracle WebLogic Server administrator. For example:

    welcome1

    server.targets The name of the Managed Server. For example:

    soa_server

    soa.server.oracle.home The location of where to store the deployment plans for the adapters. For example:

    C:\\AS11gR1SOA

    foreign.mds.type The location of the Oracle Metadata Repository.

    Leave the default value to jdev. You do not have to specify the values for the following parameters:

    • jdbc-userid

    • jdbc-password

    • jdbc.url

    These parameters are ignored when the value is set it jdev.

    For an environment in which you are deploying from a server location without Oracle JDeveloper, then specify db and supply values for the jdbc-userid, jdbc-password, and jdbc.url parameters to specify the location of the MDS Repository.


  4. From the JDeveloper main menu, choose File > Save All.

  5. In the Application Navigator, under the Resources node, right-click build.xml and choose Run Ant Target and select the following ant targets in the following sequential order:

    Target Description
    1. setupWorkspaceForJDeveloperUse This script sets up the application workspace in Oracle JDeveloper.
    2. seedFodJmsResources This script populates the JMS resources for the Fulfillment mediator.
    3. seedDemoUsers This script adds jstein as the user to approve orders for over $2,000. When you run the demo, you place an order for $2,000 and log in to the Oracle BPM Worklist as jstein and approve the order.

    If you do not run this script, the OrderProcessor BPEL process generates a recoverable error and assigns the task to the weblogic administrator.

    4. compile-build-all This script compiles and builds all the SOA composites.
    5. compile-deploy-all This script compiles, builds, and deploys all the SOA composites to the Managed Server for Oracle SOA Suite.

    Do not run the next target in the sequence until the previous one completes successfully. In the Apache Ant - Log, ensure you see the following message before proceeding to the next script:

    BUILD SUCCESSFUL
    Total time: nn minutes nn seconds
    

    For more information about the ant targets, see the following resources:

2.2 Placing Two Orders in the Store Front

The ordering process begins in the storefront UI, where a user shops for and orders products. When an order is submitted, the Application Development Framework Business Component writes the order to database and raises an NewOrderSubmitted business event using the Events Delivery Network (EDN). The OrderPendingEvent mediator subscribes this event, and initiates the main BPEL process, OrderProcessor, to process the order.

In this task, place two orders, one for under $2000 and the other for over $2000. By placing these order, you can see how orders totalling more than $2000 require human approval.

To place orders:

  1. Access the storefront from the following URL:

    http://hostname:port/StoreFrontModule/faces/home.jspx
    

    where hostname is the DNS name or IP address of the Oracle WebLogic Server for Oracle SOA Suite and port is the address of the port on which the Managed Server for the Oracle WebLogic Server is listening for requests (8001 by default).

    You begin the order process by browsing the product catalog. When you click Add next to a product, the site updates the shopping cart region to display the item.

  2. Place an order for under $2000:

    1. Click the Ipod Nano 1 Gb for $149.95 and click Add.

    2. Click the Ipod Nano 2 Gb for $199.95 nd click Add.

      The following shows the cart summary with the two products added. The summary displays a subtotal purchase total of $349.90 for the two items that appear in the cart.

      TBD
      Description of the illustration order1a.gif

    3. Click the Checkout link, located in the middle of the menu bar.

      A login dialog displays.

      TBD
      Description of the illustration order1b.gif

    4. Enter ngreenbe and welcome1 in the Username and Password fields, respectively.

    5. Click Log In.

      The Shipping Details page displays.

      Description of order1c.gif follows
      Description of the illustration order1c.gif

    6. In the Order Information #order_id section, take note of the order ID, as you need it for a later task. In this example, the order ID is 1179.

    7. In the Shipping Information section, take note of the following default settings:

      - 100 N Peach St Philadelphia PA 19139 US

      - 536267 MSTR

    8. In the Order Summary section, take note of the order total, which is $353.86 and click Submit Order to complete the first order.

      The Invoice Details page displays.

      Description of order1d.gif follows
      Description of the illustration order1d.gif

  3. Click the Exit and Continue Shopping link, located in the menu bar, to return to the home page.

    Description of exit.gif follows
    Description of the illustration exit.gif

  4. Place an order for over $2000:

    1. Click the Plasma HD Television for $1,999.99 and click Add.

    2. Click the Playstation 2 Video Game for $199.95 and click Add.

      The Shopping Cart Summary section displays a subtotal purchase total of $2,199.94 for the two items that appear in the cart.

    3. Click the Checkout link.

      The Shipping Details page displays.

    4. In the Order Information #order_id section, take note of the order ID, as you need it for a later task. In this example, the order ID is 1180.

    5. In the Shipping Information section, modify any of the options, such as the address in the Shipping Address field and the credit card in the Payment Options section. Take note of the settings you select.

      - 2100 S Casino Dr. Laughlin NV 89029 US

      - 4111111111111111 VISA

    6. In the Order Summary section, take note of the order total, which is $2,219.42 and click Submit Order to complete the second order.

      The Invoice Details page displays.

      Description of order1e.gif follows
      Description of the illustration order1e.gif

  5. Click the Logout link, located in the right-hand-side of the menu bar, to log ngreenbe out of the session.

    Description of logout.gif follows
    Description of the illustration logout.gif

2.3 Starting Fusion Middleware Control to Monitor Orders

To start Oracle Enterprise Manager Fusion Middleware Control to monitor orders:

  1. Use Mozilla FireFox, version 2.0 or higher, or Internet Explorer, version 7.0 or higher, to access the following URL:

    http://hostname:port/em
    

    where hostname is the host name and port is the port of the Fusion Middleware Control for the Oracle SOA Suite installation.

    The login dialog appears.

  2. Enter weblogic/password and click Login

    where:

    • weblogic is the Fusion Middleware Control Console administrator user name

    • password is the password you provided for the weblogic administrator during installation

  3. From the navigation pane, expand SOA > soa-infra to see the deployed applications:

    TBD
    Description of the illustration fod_deployedcom_menu.gif

    OrderBookingComposite and PartnerSupplierComposite are the two main composites in the WebLogic Fusion Order Demo application.

2.4 Monitoring the First Order

You now monitor the first order sent from the Store Front module to the OrderBookingComposite composite from the Fusion Middleware Control. This order was submitted by Nancy Greenberg for $353.86.

To monitor the first order:

  1. From the navigation pane, expand SOA > soa-infra to see the deployed applications:

    TBD
    Description of the illustration fod_deployedcom_menu.gif

    OrderBookingComposite and PartnerSupplierComposite are the two main composites in the WebLogic Fusion Order Demo application.

  2. Click the OrderBookingComposite composite.

    TBD
    Description of the illustration fod_deployedcom_menu2.gif

    The SOA Infrastructure home page displays. The upper part of the page displays details about recent SOA composite application instances, recent faults, and rejected messages. The topmost two instances in the Recent Instances table represents the instance of the SOA composite application you created when you placed orders in Section 2.2, "Placing Two Orders in the Store Front."

    TBD
    Description of the illustration fod_upperorderbook.gif

  3. In the Recent Instances section, click the second instance, representing the order for $353.86. Note the instance number.

    The Flow Trace page displays. The Trace section shows the sequence of the message flow through the services, service components, and references that comprise the SOA composite application.

    TBD
    Description of the illustration flow_orderbook.gif

    The Trace section displays the state of each service component within the OrderBookingComposite composite. Notice all the service components have a status of Completed, indicating that the order was successfully processed.

  4. Click the OrderProcessor BPEL process service component in the Instance column to view instance more carefully.

    The Audit Trail tab of the Instance of OrderProcessor window displays execution details about the activities in the BPEL process. Notice, too, the instance you selected displays in the Instance ID field on the right side.

    Description of flow_auditorderbook.gif follows
    Description of the illustration flow_auditorderbook.gif

  5. Click the Flow tab to see a visual representation of the instance.

    A visual representation of the BPEL process activities appears. The icons in the flow are referred to as activities. You can click them to view their details.

    Description of flow_floworderbook.gif follows
    Description of the illustration flow_floworderbook.gif

  6. Click the first activity, the blue, circle receive activity labeled receiveInput.

    Description of receiveinput.gif follows
    Description of the illustration receiveinput.gif

    The Activity Details dialog displays the XML input to this BPEL process instance. It shows the order ID (orderID) you were given when you placed the order through the Store Front module. In this example, the order ID is 1179.

    Description of order_act.gif follows
    Description of the illustration order_act.gif

  7. Click X or Close to the dismiss the Activity Details dialog.

  8. Scroll further in the process to the Scope_RetrieveOrder activity and click findOrderByID to order ID as input to variable gOrderInfoVariable:

    bpelx:bindEntity is executed on variable gOrderInfoVariable with the following key values:
    {{/oracle/fodemo/storefront/store/queries/common/}OrderId=1179}
    
  9. Click X or Close to the dismiss the Activity Details dialog.

  10. Scroll to the Scope_RetrieveCustomerForOrder scope and click the InvokeFindCustomer activity to see the StoreFrontService service being invoked and returning the customer information. Note the following in the Activity Details window:

    • lFindCustomerInfo_InputVariable represents the input variable to the StoreFrontService service. The CustId parameter represents the ID of the customer of customer ngreenbe.

    • gCustomerInfoVariable represents the output from the StoreFrontService service, which returns the customer information for back to the BPEL process.

    Description of order2.gif follows
    Description of the illustration order2.gif

  11. Click X or Close to the dismiss the Activity Details dialog.

  12. Scroll to the Scope_AuthorizeCreditCard scope and click InvokeCheckCreditCard to see the CreditCardAuthorization service being invoked and returning the status of the credit card.

    Note the following in the Activity Details window:

    • lCreditInput represents the input variable to the CreditCardAuthorizationService service. Parameters CCType, CCNumber, and PurchaseAmount represent the input credit card type, number, and order total. These values are set as follows:

      <CCType>MSTR</CCType>
      <CCNumber>536267</CCNumber> 
      <PurchaseAmount>353.86</PurchaseAmount> 
      
    • lCreditCardOuput shows the service returned a status of APPROVED. Therefore, the OrderProcessor BPEL process continues.

  13. Click X or Close to the dismiss the Activity Details dialog.

  14. Scroll to the Scope_CheckApprovalLimit scope and click the Invoke link under the BusinessRule_ApprovalRequired to see the RequiresApprovalRule business rule being invoked.

    Note the following in the Activity Details window:

    • dsIn represents the input variable sent to the business rule. The approve parameter shows the invocation of the rules engine at run time. The price parameter shows the order total was $353.86. The rule engine requires this input to determine whether human approval is required.

    • dsOut shows the output from the business rule. The approvalRequired parameter has a value false. Because this order is under $2,000, no human approval is required. Therefore, the return value is set to false.

    Description of order3.gif follows
    Description of the illustration order3.gif

  15. Click X or Close to the dismiss the Activity Details dialog.

  16. In the Scope_RetrieveQuotes scope, perform the following:

    1. Click the Invoke_PartnerSupplier link to see the order information being sent to the PartnerSupplierMediator mediator. The PartnerSupplierMediator routes the order information to the ExternalPartnerSupplier BPEL process, located in PartnerSupplierComposite composite.

      Description of order4.gif follows
      Description of the illustration order4.gif

    2. Click X or Close to the dismiss the Activity Details dialog.

    3. Click the Invoke_InternalWarehouse link to see the order ID being sent to the InternalWarehouseService BPEL process through the lInternalWarehouseInputVariable variable:

      Description of order5.gif follows
      Description of the illustration order5.gif

    4. Click X or Close to the dismiss the Activity Details dialog.

  17. In the Scope_SelectPreferredSupplier scope, click the Invoke link under BusinessRule_SelectPreferredSupplier to see the EvaluatePreferredSupplierRule business rule being invoked.

    Note the following in the Activity Details window:

    • dsIn represents the input variable sent to the business rule. The warehouse, deliveryDate, and orderTotal parameter values provide the input to the business rule. The rule engine uses this input to pick the supplier with the lowest shipping price to fulfill the order.

      The returned input data for the two warehouse suppliers is as follows:

      <warehouse>InternalWarehouse</warehouse>
      <deliveryDate>2009-02-13</deliveryDate>
      <orderTotal>1000</orderTotal>
      ... 
      
      <warehouse>PartnerWarehouse</warehouse>
      <deliveryDate>2009-02-13</deliveryDate>
      <orderTotal>353.86</orderTotal>
      

      The InternalWarehouse supplier returns a static value of $1,000 for all orders.

    • dsOut shows the output from the business rule. The warehouse parameter value shows the selected warehouse supplier. The PartnerWarehouse supplier was selected, because it provided a lower quote.

    Description of warehouse_order.gif follows
    Description of the illustration warehouse_order.gif

  18. Click X or Close to the dismiss the Activity Details dialog.

  19. In the Scope_FulfillOrder scope, click Invoke_FulfillOrder link to see the order information being sent to the FulfillOrder mediator. The FulfillOrder mediator stores the order in a temporary queue and routes the order to USPS for shipment.

    Description of fulfillordermed_order.gif follows
    Description of the illustration fulfillordermed_order.gif

  20. Click X or Close to the dismiss the Activity Details dialog.

  21. Scroll to the Scope_NotifyCustomerOfCompletion scope and click the InvokeNotificationService link to see the output E-mail notification sent to Nancy Greenberg.

  22. Click X or Close to the dismiss the Activity Details dialog.

  23. Close the Flow Trace window.

2.5 Monitoring the Second Order

You now monitor the second order you submitted for $2,219.42 as Nancy Greenberg. This order is processed differently than the first order, because the order amount is for more than $2,000. Therefore, it requires human approval. In this task, monitor the order with the Fusion Middleware Control, approve the order with Oracle BPM Worklist, and see the order complete in the Fusion Middleware Control.

To monitor the second order, complete the following tasks:

2.5.1 Task 1: View the Order in the Fusion Middleware Control

  1. From the SOA Infrastructure home page, in the Recent Instances section, click the first instance, representing the order for $2,219.42.

    The Flow Trace page displays.

  2. Click the OrderProcessor BPEL process service component in the Instance column.

    The Audit Trail tab of the Flow Trace window displays execution details about the activities in the BPEL process.

  3. In the Recent Instances section, click the first instance, representing the order for 2,219.42. Note the instance number.

    The Flow Trace page displays.

    TBD
    Description of the illustration flow_orderbook2.gif

    Unlike the first order, notice in the Trace section how the service components in the OrderBookingComposite composite are not all complete and the process is stopped at the ApprovalHumanTask component.

  4. Click the OrderProcessor BPEL process service component in the Instance column to look at the instance more carefully in the Instance of OrderProcessor window.

  5. Click the Flow tab to see a visual representation of the instance.

  6. Click the receiveInput. activity to see the order ID you placed.

    The Activity Details dialog displays the XML input to this BPEL process instance. It shows the order ID (orderID) you were given when you placed the order through the Store Front module. In this example, the order ID is 1180.

    Description of order6.gif follows
    Description of the illustration order6.gif

  7. Click X or Close to the dismiss the Activity Details dialog.

  8. Scroll to the Scope_CheckApprovalLimit scope and click the Invoke link under the BusinessRule_ApprovalRequired to see the RequiresApprovalRule business rule being invoked.

    Note the following in the Activity Details window:

    • dsIn represents the input variable sent to the business rule. The approve parameter shows the invocation of the rules engine at run time. The price parameter shows the order total was $2,219.42.

    • dsOut shows the output from the business rule. The approvalRequired parameter has a value true. Because this order is over $2,000, human approval is required. Therefore, the return value is set to true.

    Description of order7.gif follows
    Description of the illustration order7.gif

  9. Click the Collapse icon (-) icon on the BusinessRule_ApprovalRequired to collapse it.

  10. Scroll toward the bottom of the Scope_CheckApprovalLimit scope to see the ApprovalHumanTask human task was initiated after the business rule. The switch under the business rule is like a if-then-else, case, or switch statement in other programming languages. In this case, if approval is required, this switch submits data to the ApprovalHumanTask human task.

    Description of order8.gif follows
    Description of the illustration order8.gif

  11. Click the initiateTask_ApprovalHumanTask_1 activity.

  12. In the Activity Details dialog, scroll to the initiateTaskResponseMessages variable to see the assigneeUsers parameter. This parameter specifies the human task has been assigned to user jstein:

    - <assigneeUsers>
       <id>jstein</id> 
       <type>user</type> 
    </assigneeUsers>
    
  13. Click X or Close to the dismiss the Activity Details dialog.

  14. Click the receiveCompletedTask_ApprovalHumanTask_1 activity to see the human task is awaiting approval.

    Description of order9.gif follows
    Description of the illustration order9.gif

  15. Click X or Close to the dismiss the Activity Details dialog, but do not close the Flow Trace page, as you need it to view order processing when it completes.

2.5.2 Task 2: Use the Oracle BPM Worklist to Approve the Order

To approve the order, use the Oracle BPM Worklist:

  1. Use Internet Explorer 7 or Mozilla Firefox 2.0.0.2 to access the following URL:

    http://hostname:port/integration/worklistapp/faces/home.jspx
    

    where hostname is the DNS name or IP address of the Oracle WebLogic Server for Oracle SOA Suite and port is the address of the port on which the Managed Server for the Oracle WebLogic Server is listening for requests (8001 by default).

    The login dialog appears.

  2. Enter jstein in the Username field and welcome1 in the Password field and click Login.

  3. The Inbox shows the order number 1180 is awaiting approval.

    Description of bpm_order.gif follows
    Description of the illustration bpm_order.gif

  4. Select the order from the table and from the Actions menu, select Approve.

    Description of bpm2.gif follows
    Description of the illustration bpm2.gif

  5. Click OK to acknowledge the approval message.

    The My Tasks tab updates so that no worklist tasks are currently assigned to jstein.

    With the order approval completed, the processing for the order is now complete.

2.5.3 Task 3: View the Approval in the Fusion Middleware Control

To verify the order completed processing with Fusion Middleware Control:

  1. Go back to the Flow Trace page and click the Refresh icon, located in the top right corner:

    Description of refresh_em.gif follows
    Description of the illustration refresh_em.gif

  2. Scroll toward the bottom of the Scope_CheckApprovalLimit scope to see the ApprovalHumanTask human proceeded.

    Description of order10.gif follows
    Description of the illustration order10.gif

  3. Click the receiveCompletedTask_ApprovalHumanTask_1 activity to see the human task.

    Description of order11.gif follows
    Description of the illustration order11.gif

  4. Click X or Close to the dismiss the Activity Details dialog.

  5. In the Scope_SelectPreferredSupplier scope, click the Invoke link under BusinessRule_SelectPreferredSupplier to see the EvaluatePreferredSupplierRule business rule being invoked.

    Note the following in the Activity Details window:

    • dsIn represents the input variable sent to the business rule. The warehouse, deliveryDate, and orderTotal parameter values provide the input to the business rule. The rule engine uses this input to pick the supplier with the lowest shipping price to fulfill the order.

      The returned input data for the two warehouse suppliers is as follows:

      <warehouse>InternalWarehouse</warehouse>
      <deliveryDate>2009-03-13</deliveryDate>
      <orderTotal>1000</orderTotal>
      ... 
      
      <warehouse>PartnerWarehouse</warehouse>
      <deliveryDate>2009-03-13</deliveryDate>
      <orderTotal>2219.42</orderTotal>
      
    • The warehouse parameter value shows the selected warehouse supplier. The InternalWarehouse supplier was selected, because it provided a lower quote.

  6. Click X or Close to the dismiss the Activity Details dialog.

  7. In the Instance of OrderProcessor window, click the Flow Trace breadcrumb to return to the main Flow Trace window.

    Description of flowtrace2.gif follows
    Description of the illustration flowtrace2.gif

    Notice in the Trace section how the service components in the OrderBookingComposite composite are now all complete.

    TBD
    Description of the illustration flow_orderbook3.gif

  8. Close the Flow Trace window.

2.6 Undeploying the Composites for the WebLogic Fusion Order Demo Application

The remainder of this tutorial describes how to build the composite applications for the WebLogic Fusion Order Demo applications. Because you deploy the composite applications during the development process, you can now undeploy the completed ones.

To undeploy the composite applications:

  1. Access Undeploy SOA Composite wizard in Fusion Middleware Control through the following options:

    From the SOA Infrastructure Menu... From the SOA Folder in the Navigator... From the SOA Infrastructure Home Page... From the SOA Composite Menu...
    1. Select SOA Deployment > Undeploy.

      The Select Composite page appears.

    2. In the SOA Composite Deployments section, select OrderBookingComposite and PartnerSupplierComposite to undeploy them, and click Next.

    1. Right-click soa-infra.
    2. Select SOA Deployment > Undeploy.

      The Select Composite page appears.

    3. In the SOA Composite Deployments section, select OrderBookingComposite and PartnerSupplierComposite to undeploy, and click Next.

    1. Click the Deployed Composites tab.
    2. In the Composite table, select both OrderBookingComposite and PartnerSupplierComposite.

    3. Above the Composite table, click Undeploy.

    Select SOA Deployment > Undeploy.

    The Confirmation page appears.

  2. Click Undeploy. Note that you are warned if you are about to undeploy the last remaining revision of a deployed composite application.

    Processing messages are displayed.

  3. When undeployment has completed, click Close.