To configure BAM, create a BAM database service endpoint:
In the left pane of the Process Administrator, click Service Endpoints.
On the Service Endpoints page, click Add.
On the Service Endpoints | Add Service Endpoint page, enter a Name for the BAM database, such as BAMdb.
In the Type drop-down list, select SQL Database.
In the Subtype drop-down list, select the JDBC connector type for the BAM database. The JDBC selected must be installed the computer that hosts the SQL database where the BAM database will be created.
Click Next.
On the Service Endpoints | Add Service Endpoint | Edit Service Endpoint page, enter the configuration Properties for the BAM database. The configuration properties will vary based on the type of JDBC selected. For an explanation of the properties required for each type of JDBC, refer to the Required Parameters for SQL Database JDBC Configuration.
Configure the Runtime options or accept the default settings.
Click Save.
Then configure the BAM settings:
In the left pane of Process Administrator, select Process Monitoring.
On the Process Data Mart page, BAM tab, configure the BAM Properties:
|
Property |
Description |
|
Enable Automatic Update |
Sets the BAM updater to run automatically based on the Update Frequency time setting. If this option is not selected, a manual update can be performed from the ptprocess\1.5\bin folder using fuegowarehouse.bat. |
|
Runtime Database Configuration |
The BAM database. The BAM database must be configured as a SQL Database business end point before it will appear in this drop-down list. |
|
Update Frequency (in minutes) |
The frequency with which the BAM updater will run and migrate events from the process execution engines to the BAM database. |
|
Data Availability Time (in hours) |
The length of time the BAM data will remain in the BAM database. The data will be disposed of after the number of hours set in this field and will then only be accessible from the data mart database. |
Note: The BAM log is created in the same directory as the process data mart log and cannot be configured separately. The process data mart Log Directory configuration setting must be saved before the BAM updater log file can be created. Log messages from the BAM updater will be written to the bam-dwupdater-service.log file in this directory. This directory must exist in order for the log file to be created by the BAM updater. The verbosity level can be set by configuring the wrapper.logfile.loglevel property in \conf\WarehouseService.conf. Acceptable values are: NONE, INFO, and DEBUG.
Click Save.
Click the BAM tab.
Click Manage Database.
On the BAM | Manage Database page, select the Create Database checkbox.
Select the Create Data Structure checkbox.
Enter a User Name and User Password with administrative write privileges for the host engine.
Click OK.
At the top of the Process Data Mart page, the Message(s) section should contain the following confirmation messages:
The database has been created.
The data structure has been created.
To verify the creation of the database and data structure, check the host engine to see if the new database is there.
Then install the data warehouse Process Monitoring service on the host computer for Process or BPM:
In the command prompt, change to the directory containing the albpmwarehouse.bat file that was included during installation.
In the correct directory, type:
albpmwarehouse.bat install
Note that the JAVA_HOME environment variable must be set.
In the Windows Services utility, start the data warehouse Process Monitoring service.
Note: Changes to the Process Data Mart and BAM configurations will only take effect if you stop and re-start the data warehouse Process Monitoring service.
Note: Installation of this service is not required for Unix. Start the service to use the Process Data Mart and BAM configurations. The Unix parameters for this service are: ./albpmwarehouse.sh { start | stop | dump }
Related Topics: