# Step 12: Run the Request Quote Business Process

You can run and test the functionality of the business process you created using WebLogic Workshop's browser-based interface. Using the Workshop Test Browser, you play the role of the client, invoking the methods on the business process and viewing the responses.

To Launch the Test Browser

1. In the Application pane, select RequestQuote.jpd—the business process you want to test.
2. If it not already selected, click the Design View tab. The business process you selected in the Application pane is displayed in the Design View.
3. If it is not already running, start WebLogic Server. To do so, from the WebLogic Workshop menu, choose Tools —> WebLogic Server —> Start WebLogic Server.

If WebLogic Server is running, the following indicator is visible in the status bar at the bottom of the WebLogic Workshop visual development environment:

4. From the WebLogic Workshop menu, click Build —> Build Application. WebLogic Workshop builds your application.
5. When the build is complete, click the Start button on the menu bar to run your business process. If the build is successful, the Workshop Test Browser is launched, through which you can test your business process using sample input values.

Note: If you completed Step 6 in the tutorial to replace the tax calculation Web Service with a Process control, you may get a build warning about the taxCalculation Web service when you run your process. You can ignore this warning. It occurs because you have an unused Web Service control (taxCalculation) in the RequestQuote.jpd. If you remove or comment out the declaration of taxCalculation in the RequestQuote.jpd, the business process builds without warnings. The following lines show the control declaration in your JPD file:

/**
* @common:control
*/
private requestquote.services.TaxCalcControl taxCalculation;

6. If the browser is not already open on the Test Form page, click the Test Form tab to open the Test Form page.

You can enter data that your business process can receive as part of a client request directly on the Test Form page. Alternatively, you can browse your file system and upload a file which contains your test data. In this case, test XML data are provided in the tutorial application for you to use.

7. Click Browse beside the xml requestXML (file value) field to open the file browser.
8. Select QuoteRequest.xml from the testxml folder, which is available at the following location in your file system:

myapplications\Tutorial_Process_Application\
Tutorial_Process_ApplicationWeb\requestquote\testxml\QuoteRequest.xml.
In the preceding line, myapplications represents the location in which you created your Tutorial_Process_Application application.

9. Click the button labeled with the method name on your business process (quoteRequest) to invoke the method and start the business process. The Test Form page refreshes to display a summary of your request parameters and the response from the external services in the Message Log:

For business processes that involve multiple communications with clients (as is the case in this scenario), or communications with resources such as other Web services, the Message Log at the left of the Test Form page displays an entry for each call to a method or a response from the service so that you can view the data for each.

Note that the sequence of calls displayed in the Message Log when you run your business process may be different from the sequence shown in the preceding figure. In your Message Log, you should see the following calls:

1. The quoteRequest call you made to invoke the business process.
2. A call to and a response from the tax calculation service.
3. Three sets of price request and responses and three sets of availability request and responses—a total of 12 messages. Because the requests to the price and availability services are made in parallel, the requests and responses can be in a different order each time you run your process. However, the For Each loop ensures that the processing for a given line item (in this case, for each widgetID) is completed before the next line item is processed.
4. The quoteResponse call from the business process to the client that invoked.

10. Click any log entry to see the details of that interaction. For example, if you click priceProcessor.returnPrice, the browser displays the message returned from the priceProcessor during one iteration through the For Each loop.
11. When the business process finishes, a message similar to the following is displayed in the Message Log:

    Instance instanceID is Completed.

where instanceID represents the ID generated when the quoteRequest method in your business process was called.

12. If you included a call to a File control in your business process, as described in Step 10: Write Quote to File System, a file containing the quote document is created in the location in your file system that you specified when you designed the interaction between your business process and the File control.

Note: If you are running the RequestQuote.jpd business process provided for you when you created your Tutorial_Process_Application application for the first time, the File control writes a file named quote.xml to your working directory. In this case, the working directory is the directory in which the integration server is running: BEA_HOME\weblogic81\samples\domains\integration.

13. To display a graphical representation of your running process, click Graph on the Message Log panel.
14. To stop the Test Browser, you can simply close it, or return to WebLogic Workshop and then click on the menu.

To Monitor Instances of Your Business Process

You can use the WebLogic Integration Administration Console to monitor running processes or view statistics for processes that already ran.

- Click Monitor to open the WebLogic Integration Administration Console in a Web Browser. Login using username = weblogic and password = weblogic. The WebLogic Integration Administration Console opens to the Process Instance Details page. The WebLogic Integration Administration Console allows you to administer and manage your WebLogic Integration applications. For example, if you click View Statistics on the Process Instances navigation pane, you access a Process Instance Statistics page. This page displays a summary of business process instances grouped by the process type. To view the instances of a process type that ran or are running on your server, click the process name. Processes instances are identified by their instanceID. Note that the instanceID displayed for your RequestQuote business process matches the instanceID displayed on the Message Log pane (see the preceding figures in this topic).
- Click Monitor all RequestQuote.jpd processes at the top of the Test Form to open the WebLogic Integration Administration Console. Login using the default username: weblogic and password: weblogic. When you use this link to open the Administration Console, it opens on the Process Instance Summary page, which displays a summary of all the instances of business processes that ran or are running. It 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.

- Other ways to invoke the WebLogic Integration Administration Console include the following:

- From the WebLogic Workshop Tools menu, select Tools —> WebLogic Integration —> WebLogic Integration Administration Console
- Entering the following URL in a Web browser: http://localhost:7001/wliconsole

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

To learn about using the WebLogic Integration Administration Console, see the console's online help and Managing WebLogic Integration Solutions at the following URL:

    http://edocs.bea.com/wli/docs81/manage/index.html

Related Topics

Managing WebLogic Integration Solutions at http://edocs.bea.com/wli/docs81/manage/index.html

Understanding the Service URL

Testing Your Application with Test View