Chapter 16. Administering Your System with the BPEL Web Console
16.1. BPEL Web Console
- any process definitions you have deployed to the BPEL engine
- the process instances executing in the BPEL engine
- a process' execution history
- the query pertaining to the execution history
Important
16.2. Business Process Execution Language (BPEL)
16.3. Business Rule Orchestration
16.4. Process Definition
16.6. View Deployed Processes with the BPEL Web Console
Procedure 16.1. Task
- Launch a web browser and go to http://localhost:8080/bpel-console.
- Input your user name and password.
- Click on the Manage Instances tab to see which BPEL processes are currently deployed. You will also see version information for each of these processes.
- Select a process definition to open it. In the bottom panel you will see a list of process instances that are active for that particular definition.
Note
Only one version of a process can be active at a time. When you open a process definition, the active version is automatically selected. - Sometimes you will find that you need to manage a "retired" version (for example, in order to terminate running instances). In these cases, click - and then select the version you want.
Note
If there is no version for a particular process archive, (such asQuickstart_bpel_simple_invoke.jar), it is treated as version zero. (In this case,Quickstart_bpel_simple_invoke-1.jar,will be the next version deployed.)
16.7. Business Process Analytics Format (BPAF)
16.8. View BPAF Data with the BPEL Web Console
Procedure 16.2. Task
- Launch a web browser and go to http://localhost:8080/bpel-console.
- Input your user name and password.
- Click on the Manage Instances tab to see which BPEL processes are currently deployed. You will also see version information for each of these processes.
- Select a process definition to open it. In the bottom panel you will see a list of process instances that are active for that particular definition.
- 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.
16.10. Activate the BPEL Web Console's Logging Functionality
Procedure 16.3. Task
- Open the
deploy.xmlfile in a text editor (for the bpel_helloworld quick start, this would bevi SOA_ROOT/jboss-as/samples/quickstarts/bpel_hello_world/bpelContent/deploy.xml - Edit the file as follows:
<deploy xmlns="http://www.apache.org/ode/schemas/dd/2007/03" xmlns:bpl="http://www.jboss.org/bpel/examples" xmlns:intf="http://www.jboss.org/bpel/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> - Save the file and exit.
- Open the
bpel.propertiesfile in the text editor:vi SOA_ROOT/jboss-as/server/PROFILE/deploy/riftsaw.sar/bpel.properties - Switch on the process-events option for the particular process you want to log and make sure that org.jboss.soa.bpel.console.bpaf.BPAFLogAdapter is enabled.
- Save the file and exit.
16.11. View Instance Data with the BPEL Web Console
Procedure 16.4. Task
- Launch a web browser and go to http://localhost:8080/bpel-console.
- Input your user name and password.
- Click on the Manage Instances tab to see which BPEL processes are currently deployed. You will also see version information for each of these processes.
- Select a process definition to open it. In the bottom panel you will see a list of process instances that are active for that particular definition.
Note
Only one version of a process can be active at a time. When you open a process definition, the active version is automatically selected. - Click the button.
- The View tab shows the instance execution graph, while the Source tab below it shows all of the "activity" events.
16.12. Instance Execution Graph
16.13. View the Instance Execution Graph with the BPEL Web Console
Procedure 16.5. Task
- Launch a web browser and go to http://localhost:8080/bpel-console.
- Input your user name and password.
- Click on the Manage Instances tab to see which BPEL processes are currently deployed. You will also see version information for each of these processes.
- Select a process definition to open it. In the bottom panel you will see a list of process instances that are active for that particular definition.
Note
Only one version of a process can be active at a time. When you open a process definition, the active version is automatically selected. - Click on the button to see an instance execution graph for the process.
16.14. View a History Instance Query
Prerequisites
- History logging must be enabled.
Procedure 16.6. Task
- Log into the BPEL Web Console.
- 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.
- 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.
16.15. Active Process Definition
16.16. Retired Process Definition
16.17. Manually Retire an Active Process Definition
Procedure 16.7. Task
- Launch a web browser and go to http://localhost:8080/bpel-console.
- Input your user name and password.
- Click on the Runtime tab.
- Select the Deployments option.You will now be able to see the version information and current status (active or retired) of each process definition.
- Select the particular version of the process definition you want to retire and then press the button.
Note
If you undeploy a process, its end-points will only deactivate if no previous versions of that process have ever existed.
16.18. End-Point Reference
16.19. Manually Re-Activate a Retired Process Definition
Procedure 16.8. Task
- Launch a web browser and go to http://localhost:8080/bpel-console.
- Input your user name and password.
- Click on the Runtime tab.
- Select the Deployments option.You will now be able to see the version information and current status (active or retired) of each process definition.
- Select the retired version you want to reactivate and press the button (found on the bottom-right of screen.)
16.20. Enable UTF-8 Support for Processes or External Web Services
Procedure 16.9. Task
- Check your database to make sure UTF-8 encoding is being used by default.
- Launch a text editor and open the database's configuration file.
- Add these settings to the file:
hibernate.connection.useUnicode=true hibernate.connection.characterEncoding=UTF-8
- Save the file and exit.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.