> Tutorial: Building Your First Business Process > Step 15: Run and Test the Request Quote Business Process With the Quote Validation Service

Tutorial: Building Your First Business Process

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Step 15: Run and Test the Request Quote Business Process With the Quote Validation Service

In the same way you ran and tested the business process you created when you finished Adding Looping Logic, Parallel Paths . . . of the tutorial, you can run and test the functionality of the business process you created in Part IV using WebLogic Workshop's browser-based interface.

To Launch the Test Browser

To run and test the business process that you have created, complete the following steps:

  1. If WebLogic Server is not already running, from the BEA Workshop menu, choose WindowArrow symbol Show View Arrow symbolOther Arrow symbolServerArrow symbol Servers, and click OK. A Server view is displayed in which the Server and its state are shown.
  2. In the Package Explorer, select and right-click on requestquote.java, click Run As, and click Run On Server.
  3. In the Define a New Server dialog box, select either a Choose an existing server option or Manually define a server (if there is no server defined), and click Next.
  4. In the BEA WebLogic v9.2 Server dialog box, to manually define a server, click Browse, and select the samples integration domain directory from the product installation directory available at BEA_HOME\weblogic92\samples\domains\integration, where BEA_HOME represents the directory in which you installed WebLogic Platform. Click Finish.

    5. The samples domain integration server is started, and the RequestQuote application is deployed on it. When WebLogic Server is running, the following indicator is visible in the Servers view.



  5. After the application is deployed, the Test Browser is displayed.
  6. Click the Test Form tab. Open the file browser by clicking Browse beside the xml requestXML (file value) field.
  7. Select RequestQuote.xml from the requestquote\testxml folder in your project.

    8. The QuoteRequest.xml file is available at the following location in your file system:
    Tutorial_Process_Application_WEB\src\testxml\QuoteRequest_a.xml



    The Test Form page refreshes to display a summary of your request parameters and the responses from the Web service in the Message Log.

    You can click any of the methods in the Message Log to view the details of the call. For example, if you click quoteRequest, the Service Request panel displays the XML message sent by the client (you) when the method was called.

    The message log reflects the order of execution of methods in your RequestQuote business process and the services it calls. For the scenario logged in the preceding figure, note the following entries in the message log:

    • quoteRequest—Was called by the client (you in this test instance) to start the RequestQuote business process.
    • mbPubValidate.publish—The publish node in your business process published the Request for Quote to the ValidateOrder Message Broker channel.
    • taxCalcProcess.requestTaxRate—The RequestQuote business process continues to execute. In this case, it calls the requestTaxRate() method on the tax calculation business process before it is interrupted by the mbSubValidate.onMessage message.
    • mbSubValidate.onMessage—In this scenario, when the ValidateOrder process determines that the Request for Quote is invalid, it publishes a message to the StopQuote Message Broker channel. Your RequestQuote business process subscribes to the StopQuote channel—when RequestQuote receives the message, it executes the logic in the OnMessage path, sends a response to the client that sent the Request for Quote (see callback.denyQuote in the Message Log in the preceding figure), and terminates the business process.
    • taxCalcProcess.returnTaxRate—The business process receives a response from the tax calculation service (returnTaxRate()) before it executes the logic in the OnMessage path. (Remember that the after execute property on the OnMessage path specifies that the process engine terminates the business process after execution of the message path. In other words, in this case, the returnTaxRate call is received as part the normal flow of execution because the logic in the OnMessage path is not yet executed.)
    • callback.denyQuote—Your RequestQuote business process sends a denyQuote message to the client that sent the Request for Quote.
    • Instance instanceID is finished—The quote is determined to be invalid by the ValidateOrder service. Therefore, further processing of the quote via the RequestQuote business process is not required. After the callback.denyQuote message is sent to the client from the message path, the business process is terminated.

      • instanceID represents the ID generated when the first method in your business process was called.

      Note: For this business process, the first and second messages in your Message Log are quoteRequest and mbPubValidate.publish. However, the order of subsequent messages can vary depending on your system. For the case shown in the preceding figure, the asynchronous message (taxCalcProcess.requestTaxRate) was sent to the tax calculation service before the interrupt message (mbSubValidate.onMessage) was received from the Stop Quote Message Broker channel. In addition, a response message (taxCalcProcess.returnTaxRate) was received from the tax calculation service before the business process was terminated as a result of receiving the mbSubValidate.onMessage message.

      You can click any log entry to see the details of that interaction in the right panel of the Test Form.
To Monitor Instances of Your Business Process

You can use the WebLogic Integration Administration Console to monitor your processes.

  1. Invoke the Administration Console in one of the following ways:
    • Click Monitor on the Message Log in the Test Browser's Test Form page.
    • From your BEA Workshop Tools menu:

      • ToolsArrow symbolWebLogic IntegrationArrow symbolWebLogic Integration Administration Console

    • By entering the following URL in a Web browser:
      • http://localhost:7001/wliconsole

      The default username is weblogic and the password for the sample integration server is also weblogic.

  2. The WebLogic Integration Administration Console opens on the Process Instance Details page.



  3. Click Process Instance Monitoring to open a page that allows you to:
    • View process instance statistics, including the number of instances in each state (running, suspended, aborted, and completed).
    • View the summary or detailed status for selected instances.
    • Suspend, resume, or terminate, selected instances.

      • If you invoked the Process Instance Monitoring page after running the RequestQuote business process, as described in this step, three business processes are listed in the Process Instance Statistics page: RequestQuote, TaxCalcProcess, and Validate Order.



  4. Click the name of any business process in the Display Name column to go to a page that displays more information about that process. For example, to learn more about the instance of the ValidateOrder business process that ran in your test:
  5. Click ValidateOrder in the Display Name column on the Process Instance Statistics page displayed in the preceding figure.
  6. A Process Instance Summary page is displayed. This page lists all the instances of the ValidateOrder business process that ran or are running.
  7. To display a page which contains more details about any instance, click the Instance ID in the ID column on the Process Instance Summary page.
  8. On the Process Instance Details page, click Graphical View to display a graphical representation of this instance of the ValidateOrder business process.
  9. To display information about the nodes, click each node of the ValidateOrder business process. Note that if you started your RequestQuote business process in the BEA Workshop Test Browser with the QuoteRequest_a.xml test data, the ValidateOrder process determines that the order is not valid. In that case, the No path on the Valid Order? Decision node is executed and highlighted in the Process Graph; the Yes path is gray, indicating that this path was not executed for this instance.

To learn more about Process Instance Monitoring in the WebLogic Integration Administration Console, see the Process Instance Monitoring topic in the Administration Console online help.

To Monitor the Message Broker Channels

You can use the WebLogic Integration Administration Console to monitor the Message Broker channels in your system, specifically the name, status, and the number of subscribers for each channel.

Open the Channel Summary List page in one of the following ways:

The Channel Summary List page is displayed. The list displays all the channels in your system (in the samples integration domain in this case). Note that the TutorialPrefix/Tutorial/StopQuote and TutorialPrefix/Tutorial/ValidateOrder channels used by your business process in Part IV of the tutorial are displayed:

Note the following information about the Message Broker channels:

To learn more about the Message Broker module in the WebLogic Integration Administration Console, see the Message Broker topic in the Administration Console online help.


  Back to Top       Previous  Next