Administrating Oracle Business Process Management Processes

After the Event Manager is ready to send events, the Process Engine needs to be configured in order to be ready to process the Events. When Oracle Enterprise Repository is installed, it provides an option to install and configure the Oracle Business Process Management Process Engine. This section assumes that the Oracle Business Process Management Process Engine was successfully installed.

Administering Oracle Business Process Management Web Applications

To start the Oracle Business Process Management Process engine and define the participants, you must launch the Oracle Business Process Management Admin Center.

Starting the Oracle Business Process Management Admin Center

Follow these steps to launch the Oracle Business Process Management Admin Center:

Navigate to the <BEA_HOME>\albpm65\enterprise\bin directory and double-click one of the following files:

albpmadmcenter (Windows or UNIX GUI-based)
./startwebconsole.sh (UNIX console-based). Then point your browser to http://<host>:8585/webconsole (e.g., http://localhost:8585/webconsole).

On the Admin Center page, click the Start BPM Web Applications option.

Figure 4-1 Oracle Business Process Management Admin Center

Oracle Business Process Management Admin Center

When it becomes available, click the Launch Process Administrator option to launch the Process Administrator.
When prompted to enter the required credentials, enter the BPM admin user name and password that was used on the FDI User Credentials panel during the installation process. The recommended example for these credentials is bpm_admin for the user name and password.

Starting the Oracle Business Process Management Process Engine

Follow these steps to start the Oracle Business Process Management Process Engine.

On the Oracle Business Process Management Process Administrator page, open the aler_engine Process Engine by clicking the Engine link on the left side of the page.

Figure 4-2 Oracle Business Process Management Process Administrator - Start / Stop

Oracle Business Process Management Process Administrator - Start / Stop

Start the aler_engine by clicking the Start icon under Engine Actions on the right side of the page. Starting the engine may take several minutes to complete. Make sure that the status of the engine is Ready.

Once you the Oracle Business Process Management Process Engine is running, you can stop it and then restart it to load your latest workflow.xml changes.

Defining the Oracle Business Process Management Participants

This section explains how to define the Oracle Business Process Management Process Engine participants.

Oracle Business Process Management Administrators

Using the FDI User Credentials, Oracle Business Process Management Process Administrator can log into the Process Administrator, start/stop the process engine, and create other users.

Advanced Registration Flow Participant

When the Oracle Business Process Management Process Engine is installed by Oracle’s BEA Products installer, it creates aler_workflow_user as the Advanced Registration Flow user. By default, the password is also set as aler_workflow_user, but the password can be changed in the Process Administrator by selecting Participants in the navigator and clicking Change the password in the Advanced Properties section, as shown in Figure 4-3.

A new participant can also be created for the role of “administrator” and this new participant can be configured in the Event Manager’s Subscription Manager file. For more information, see Configuring the Subscription Manager.

Tuning the Oracle Business Process Management Process Engine

The following parameters need to be tuned using the Oracle Business Process Management Process Administrator.

Advanced Properties

Go to the Engines > <Engine Name> > Engine Nodes > Advanced Properties page.

Database Runtime Properties

Go to the Engines > <Engine Name> > Edit Engine Database Configuration page.

Memory and Execution Thread Properties

Configuring a Standalone Process Engine for Failover

To support failover of Oracle Business Process Management standalone process engines, you can configure a backup engine(s) in your environment. One of the engines in this federation is marked as PRIMARY and the others assume to be backups for this primary engine. Multiple engines can be configured to serve as backups. Any of these backup engines will take the role of the primary if the designated primary fails. When the server that has failed comes back online, it will join in as a backup to the one acting as primary.

Using The Oracle Business Process Management Log Viewer

The Oracle Business Process Management Log Viewer enables you to read information logged by the Process Execution Engine. A set of log files is created for each project you define. The Studio Log Viewer reads the files and displays them to help you monitor and trace Engine execution.

To launch the Log Viewer, double-click the albpmlogviewer file in the <Oracle Business Process Management Enterprise Home>\bin directory.

Filtering Event Log Messages for Oracle Enterprise Repository Flows

You can filter log messages so that the Advanced Registration Flows log Info, Debug, and Fatal messages.

Turn on the “Debug” level on the Log page of the Process Engine using the Process Administrator preference settings. By default, the level is set to “Warning”.

When you turn on the Debug level though you will notice that the Process Engine prints a lot of information, not just for the Oracle Enterprise Repository Advanced Registration Flows, but other Process Engine information as well. To filter the debug logging to show only the Oracle Enterprise Repository flow-related information, follow these steps:

Within the Log viewer, select Message in the left-most list box.
Select Begins With in the next list box.
Type ALER: in the text box
Click the Apply Filter button.

The Oracle Enterprise Repository Event Logging prints a prefix of ALER: for all logged event messages, as shown here.

Configuring and Managing Advanced Registration Flows