Chapter 7. BPEL Console

Procedure 7.1. task

1. Launch a web browser and navigate to http://localhost:8080/bpel-console.
2. Enter your user name and password.
3. Click on the Runtime tab.
4. Select the Deployments option. You will now be able to see the version information and current status (active or retired) of each process definition.
5. Check if there is any active process consisting of any unfinished instances, retire the process.
6. Undeploy the process only when there is no active process instance.

Procedure 7.2. task

1. Launch a web browser and navigate to http://localhost:8080/bpel-console.
2. Enter your user name and password.
3. Click on the Managed Instances tab to see which BPEL processes are currently deployed. The process version information for each of these processes is also visible.
4. Only one version of a process can be active at a time. When you open a process definition, the active version is automatically selected.

Procedure 7.3. task

1. Launch a web browser and navigate to http://localhost:8080/bpel-console.
2. Enter your user name and password.
3. Click on the Managed Instances tab to see which BPEL processes are currently deployed. The process version information for each of these processes is also visible.
4. Select a process definition to open it.
5. Use the Execution History to produce a chart. Here you can specify a particular period of time to review and choose whether or not to include failed and terminated instances in the chart.

Procedure 7.4. task

1. Open the deploy.xml file in a text editor.

   Note

   deploy.xml file exists with every BPEL deployment unit.
2. Configure the deploy.xml file as follows:

   <deploy xmlns="schemas"
       xmlns:bpl="examples"
         xmlns:intf="examples/wsdl">
           <process name="bpl:HelloGoodbye">
              <active>true</active>
              <process-events generate="all"/>
              <provide partnerLink="helloGoodbyePartnerLink">
              <service name="intf:HelloGoodbyeService" port="HelloGoodbyePort"/> 
              </provide>
           </process>
   </deploy>

   Note

   Add the process-events element to generate all the events. For more information, navigate to the Apache ODE events http://ode.apache.org/ode-execution-events link.
3. Save the file and exit.

Procedure 7.5. task

1. Launch a web browser and navigate to http://localhost:8080/bpel-console.
2. Enter your user name and password.
3. Under the Managed Instances tab, select the Open Button list to view the deployed process definitions. When you select any one of the process, it displays the list of process definitions and version of that particular process.
4. Select a process instance to open it. You can see its details in the Execution Details panel.
5. Click the Instance Data button. It displays all the details about the process.
6. Click the Execution Path button. It opens the related instance execution graph.

   Note

   The instance execution graph is a visual representation of a running instance of a process. It tells the user about the process instance's performance over time.
7. The View tab shows the instance execution graph, while the Source tab below it shows all of the "activity" events.

Procedure 7.6. Task

1. Log into the BPEL Web Console.
2. Choose a process definition and a process status from the list box.
   You can also optionally choose to input the correlation key, the start time and the end time as search criteria.
3. Go to the History Instances List and double-click on a row. A window will pop up showing you all of the execution events that happened when that process ran.

Procedure 7.7. Task

1. Launch a web browser and go to http://localhost:8080/bpel-console.
2. Input your user name and password.
3. Click on the Runtime tab.
4. Select the Deployments option.
   You will now be able to see the version information and current status (active or retired) of each process definition.
5. Select the particular version of the process definition you want to retire and then press the Retire button.

   Note

   If you undeploy a process, its end-points will only deactivate if no previous versions of that process have ever existed.

Procedure 7.8. task

1. Open the deploy.xml file in a text editor.
2. Add <process-events generate="all"/> parameter in the deploy.xml file.