Run the sample

Client application

To run this sample, use the Business Process Choreographer Explorer.

Business Process Choreographer Explorer (BPC Explorer)

To start BPC Explorer in the integrated test environment of your WebSphere® Integration Developer, follow these steps:

  1. In WebSphere Integration Developer, switch to the Servers view.
  2. In the table, right-click WebSphere Process Server v7.0.
  3. From the pop-up menu, select Launch > Business Process Choreographer Explorer.

To start BPC Explorer on WebSphere Process Server, follow these steps:

  1. In a web browser, open URL http://yourhost:yourport/bpc.

    2. Note: Replace yourhost with your server's internet address and replace yourport with the port of your server's HTTP transport, for example

If security is enabled, the BPC Explorer opens with a login screen:

  1. Enter a valid User ID and Password. The default User ID is admin.
  2. Click Login.

The BPC Explorer opens:

Start the sample business process

To start the JMS invoker process, follow these steps:

  1. Switch to the BPC Explorer.
  2. In the Process Templates section, click Currently Valid.
  3. Select JMSInvokerProcess, then click Start Instance.

    4. The Process Input Message view opens:

  4. Optionally, enter a Process Name.
  5. In the miles field, enter 171.5.
  6. In the gallons field, enter 5.5.
  7. Click Submit.

Process output

Output message

Since the JMS invoker process is defined as long running flow, the process output message is not displayed immediately. To view the output message, follow these steps:

  1. Switch to the BPC Explorer.
  2. In the Process Instances section, click Started By Me.

  3. Select the most recent instance of the JMSInvokerProcess template. The process instance details are displayed.
  4. Proceed to the Process Output Message tab.

    5. The Process Output Message is displayed:

SystemOut.log file

Inspect the SystemOut.log of your WebSphere Process Server or the Console within WebSphere Integration Developer. The two processes prints statements similar to the following:

[12/11/08 17:13:36:125 CET] 0000016c SystemOut O >>> *PARENT* Input: 175.5 miles out of 5.5 gallons
[12/11/08 17:13:36:125 CET] 0000016c SystemOut O >>> *PARENT* ... simplified to 31.181818 mpg
[12/11/08 17:13:36:125 CET] 0000016c SystemOut O >>> *PARENT* ... now calling CHILD.
[12/11/08 17:13:36:812 CET] 000001c7 HTM I CWTKE0044I: Originator becomes administrator of task MPGConverterProcess.
[12/11/08 17:13:37:031 CET] 0000016c SystemOut O >>>>>> *CHILD* Input: 31.181818 milesPerGallon
[12/11/08 17:13:37:031 CET] 0000016c SystemOut O >>>>>> *CHILD* Output: 7.54334 litresPer100KM
[12/11/08 17:13:38:250 CET] 000001c7 SystemOut O >>> *PARENT* Output: 7.54334 liters per 100 kilometers
[12/11/08 17:13:38:250 CET] 000001c7 SystemOut O >>> *PARENT* ------------------------------------------