FileNet Business Activity Monitor (BAM) software provides pre-configured BAM objects to access the workflow and work item data stored on Process Analyzer, as well as additional objects for more advanced activity. To use these objects, you must first import them into FileNet Application Workbench. You can use them as-is or modify them.
The pre-configured objects are contained in three JAR files, OOTBConfiguration.jar, BucketExample.jar, and ThresholdExample.jar. Each file is self-contained, so some of the objects are duplicated in each project. If an object already exists, it will not be imported again.
To import pre-configured objects
See Basic BAM functionality for a description of the objects provided in this project, as well as an example of how to customize the basic objects to display user-defined fields.
CAUTION If you are using IBM WebSphere for BAM, see the instruction at the bottom of this page to Configure a context data source to access data from Process Analyzer.
BucketExample.jar: contains the objects necessary to monitor activity utilizing a "bucket" style of data collection.
ThresholdExample.jar: contains the objects necessary to monitor activity and specify rules for triggering alerts when certain data exceeds a specified threshold.
The Metadata Import/Export window will close when the import operation is complete.
For IBM WebSphere, after you import the OOTBConfiguration project (which contains a JDBC agent), you must configure a JDBC connection to use the URL-based method.
Use the following procedure to configure the JDBC connection
NOTE The VMAEDM_JDBC_AGENT is disabled by default.
jdbc:microsoft:sqlserver:// [Process Analyzer database server] : [Process Analyzer database server port] ;databaseName=VMAEDM;user=[ Process Analyzer database username] ;password= [Process Analyzer database password]
For example:
jdbc:microsoft:sqlserver://hqdaffodil:1433;databaseName=VMAEDM;user=sa;password=sa
com.microsoft.jdbc.sqlserver.SQLServerDriver