Installing ALBPM for Advanced Registration Flows

This section describes how to install the ALBPM Process Engine and deploy the Advanced Registration Flows both manually and by using the BEA Products installer.

Manually Configuring the ALBPM Database and Deploying the Advanced Registration Flows

The following steps describe how to manually install AquaLogic BPM Process Engine and deploy the Advanced Registration Flows without using the BEA Products installer. Follow the steps in this section if you:

Successfully installed ALER, but chose not to select the ALBPM option and now need to configure ALBPM and deploy the Advanced Registration Flows.
Attempted to install ALBPM, but the ALBPM deployment did not successfully complete. In which case, you may only need to verify existing information, and possibly make some minor changes, before manually running the ALBPM installation scripts.

Step 1: Copy the Build Properties File

Make a copy of the build.properties.bak file in the BEA_HOME\albpm57\FuegoSetupScript directory and rename it to build.properties in the same directory.

Step 2: Modify the Default Values In the Build Properties File

Common properties:

@BEAHOME — the path to the BEA_HOME directory where ALBPM is installed.
@ALBPM_INSTALL_DIR — the path to the ALBPM installation

Fuego Directory (FDI) properties:

@ALBPM_ADMIN_USER@ — the administrative user for logging into the directory service. (This user should not exist in the database.)
@ALBPM_ADMIN_PASSWORD@ — the password for the administrative user ID.

FDI database properties:

@DB_HOST@ — the hostname of the machine hosting the database.
@DB_PORT@ — the port number of the database service.
@DB_ADMIN_USER@ — the DBA (must already exist in the database).
@DB_ADMIN_PASSWORD@ — the password for the DBA.

If using SQL Server 2005 database:

Uncomment this line by removing the # character — #fuego.fdi.db.type=mssqlserver
Remove this line — fuego.fdi.db.type=@DB_TYPE@
@MSSQL_FDI_USER_ID@ — the FDI user (should not exist in the database).
@MSSQL_FDI_PASSWORD@ — the password for the FDI user.

If using Oracle database:

@DB_TYPE@ — replace with “oracle”.
@ORACLE_SID@ — the SID that the ALER schema was installed on. For Oracle, the default SID is orcl; for Oracle XE, the default SID is xe.
@ORACLE_FDI_USER_ID@ — the FDI user (should not exist in the database).
@ORACLE_FDI_PASSWORD@ — the password for FDI user.

Fuego Engine properties:

@DB_HOST@ — the hostname of the machine hosting the database.
@DB_PORT@ — the port number of the database service.
@DB_ADMIN_USER@ — the DBA (must already exist in the database).
@DB_ADMIN_PASSWORD@ — the password for the DBA.

If using SQL Server 2005 database:

Uncomment this line by removing the # pound character — #fuego.fdi.db.type=mssqlserver
Remove this line — fuego. server.db.type=@DB_TYPE@
@MSSQL_SERVER_USER_ID@ — the user for the ALBPM process engine (should not exist in the database).
@MSSQL_SERVER_PASSWORD@ — the password for ALBPM process engine user.

If using Oracle database:

DB_TYPE@ — replace with “oracle”.
@ORACLE_SID@ — the SID that the ALER schema was installed on. For Oracle, the default SID is orcl; for Oracle XE, the default SID is xe.
@ORACLE_SERVER_USER_ID@ — the user for the ALBPM process engine (should not exist in database).
@ORACLE_SERVER_PASSWORD@ — the password for the ALBPM process engine user.

Fuego project property:

@ALBPM_INSTALL_DIR — the ALBPM installation directory.

Step 3: Backup the Build Properties File

Make a backup copy of the build.properties file since the commands described in Step 7: Run the ALBPM Ant Scripts will delete this file, and you may need it to rerun the Ant scripts in case they fail.

Step 4: Copy the JDBC Drivers

Copy the JDBC driver for Oracle or for SQL Server 2005 into the BEA_HOME\albpm57FuegoSetupScript\ext directory.

Oracle – ojdbc14.jar
SQL Server 2005 – sqljdbc.jar

Step 5: Modify the Engine Properties File

Modify the aler_engine_props.exp file in the BEA_HOME\albpm57\FuegoSetupScript directory, as follows:

Search for the <node name="homeDir"> node and make sure that it points to the BEA_HOME/albpm57/enterprise/server/aler_engine directory.
Search for <node name="logDir"> node and make sure that it points to the BEA_HOME/albpm57/enterprise/server/aler_engine/log directory.
Search for <entry key="javaArguments" value="> and make sure that it points to the BEA_HOME directory.

Step 6: Set the ALBPM Install Environment

Modify the setenv.bat (Windows) or setenv.sh (UNIX) file by replacing the @<parameters> with the actual values, as follows:

@BEAHOME – the path to the ALBPM BEA_HOME directory.
@ALBPM_INSTALL_DIR – the path to the ALBPM installation.

From a command prompt, change to the BEA_HOME\albpm57\FuegoSetupScript directory and run either:

> setenv.bat (Windows)
> setenv.sh (UNIX)

Step 7: Run the ALBPM Ant Scripts

From a Windows or UNIX command prompt, run the following Ant scripts from within the BEA_HOME\albpm57FuegoSetupScript directory. (The Ant targets are in the build.xml file.)

> ant create-fdi (Windows)
> ant --noconfig create-fdi (UNIX)

After the script completes, then run either:

> ant install-workflow (Windows)
> ant --noconfig install-workflow (UNIX)

This will create a directory service, create an ALBPM process engine, and deploy workflows on that engine.

Step 8: Verify the Installation

Verify the installation by going in the ALBPM Process Administrator console and checking whether the process engine was created and that the workflow project was deployed. For more information, see Start the AquaLogic BPM Process Engine.

Step 9: What’s Next?

For more information on configuring ALER to use the ALBPM Process Engine, see the Configuring and Managing Advanced Registration Flows guide.

Using the BEA Installer to Configure the ALBPM Database and Deploy the Advanced Registration Flows

The following steps describe how to use the BEA Products installer to install the ALBPM Process Engine and deploy the Advanced Registration Flows without dropping the existing ALER database. Follow the steps in this section if you:

Successfully installed ALER but chose not to select the ALBPM option and now need to configure ALBPM and deploy the Advanced Registration Flows.
Attempted to install ALBPM, but the ALBPM deployment did not successfully complete. In which case, you may only need to verify existing information, and possibly make some minor changes.

Step 1: Verify the Installed ALER Web Application

Step 2: Re-run the BEA Products Installer for ALBPM

Step ?: Verify the Installation

Step ?: What’s Next?