This section provides an overview of the BPEL Console. The console provides the ability to view:

The BPEL console can be located using the URL: http://localhost:8080/bpel-console.

The first screen that is presented is the login screen:

The default username is admin with password password.

The Access Control mechanism used by the admin console is configured in the $deployFolder/bpel-console/bpel-identity.sar/META-INF/jboss-service.xml. The JAAS login module is initially set to use a property file based access mechanism, but can be replaced to use any appropriate alternative implementation.

The users for the default mechanism are configured in the property file $deployFolder/bpel-console/bpel-identity.sar/bpel-users.properties. The entries in this file represent username=password.

The user roles for the default mechanism are configured in the property file $deployFolder/bpel-console/bpel-identity.sar/bpel-roles.properties. The entries in this file represent username=role. The only role of interest currently is administrator.

Once logged in, the 'Manage Instances' tab shows the currently deployed BPEL processes and their versions.

When a process definition is selected (Open), the list of active process instances for that process definition (and version) will be displayed in the bottom panel.

There is only one active version at a time. If you open a process definition the active version will be chosen by default. Sometimes you need to manage instancs of a retired version (i.e. to terminate running instances). In that case the button More - Change Version allows you to select a different version of that process.

The Execution History allows you to inspect the BPAF history data associated with a process. You can specify a timespan and wether or not you'd like to see failed/terminated instances included in the chart.

The chart has various keyboard bindings to browse through the displayed execution data:

Keyboard and Mouse Commands
Up Arrow	Zoom In	Down Arrow	Zoom Out
Left Arrow	Half-Page Left	Right Arrow	Half-Page Right
Page-Up	Page Left	Page-Down	Page Right
TAB	Next Focus	Shift-TAB	Previous Focus
HOME	Max Zoom Out	ENTER	Max Zoom In to Focus
Mouse Drag	Scroll Chart	Shift Mouse Drag	Drag Select/Zoom
Mouse Wheel Up/Z	Zoom In	Mouse Wheel Down/X	Zoom Out
Backspace/Back Button	Back	Right Mouse Button	Context Menu
Left Click	Set Focus	Double Click	Max Zoom In to Focus

<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>   

When a process instance is selected, its details will be displayed in the Execution Details panel. The Instance Data button will also become enabled, allowing further detail about the process to be displayed. Likewise the Execution Path button opens the related instance execution graph.

When a process definition is initially deployed (i.e. the first version of the process), it automatically becomes the active process definition. If that BPEL process definition is subsequently change and redeployed, then the previous version is retired, and the new version becomes the active version.

The only difference between an active and retired process definition is that a retired process definition can no longer create new process instances. However if there are current process instances associated with the retired process definition version, then these will continue to execute.

On some occasions, the administrator may wish to change which version of a process definition is considered the active version. Or they may simply want to retire the currently active process definition, so that no more process instances can be created, only allowing the already running process instances to continue until completed.

To change the status of a process definition, the administrator should select the Runtime tab from the lefthand panel, and then select the Deployments option. This will show the process definitions, their versions and their current status (active or retired).

To change a particular version from retired to active, simply select the retired version and press the Activate button in the bottom right.

To retire a currently active process definition, simply select the particular version and then press the Retire button in the bottom right.

Note

If you deploy a process definition version into RiftSaw server, the previous version of that process definition will go to 'retire' process automatically. Also please noted that if you undeploy a process, the associated endpoints get deactivated only if it doesn't have any previous version of that process.