You must create and enable a Case Analyzer store if you
want to use IBM Case Monitor Dashboard. The createCaseAnalyzerStore command
creates and enables the event export store for the IBM Case Monitor Dashboard.
About this task
You must specify a case management target object store to associate with the Case Analyzer store.
In addition, you must specify the name of the schema to use for the Case Analyzer store. This schema must be present in the database that the
Case Analyzer store will use before you create and enable the
store.
You can specify a database connection. If you do not specify a database connection, IBM® Business Automation
Workflow uses the database connection for the target object store.
Procedure
To create and enable a Case Analyzer
store:
-
Prepare the database for the Case Analyzer store.
-
Create JDBC data sources. Run the Configure JDBC Data Sources task by using the IBM
FileNet® P8 Configuration Manager.
-
Create a database connection.
For more information, see
Creating a database connection. Based on performance
considerations, you might want to share data sources. For more information, see
Sharing data sources. You enter the database schema name when
you configure and enable the
Case Analyzer store by using the
Case administration client.
- Change the current directory
to the
install_root/CaseManagement/configure directory.
Where
install_root is the location where IBM Business Automation
Workflow is
installed.
-
Create and enable a Case Analyzer store by running the
following command. Do not enter any line breaks when you enter the command.
configmgr_cl createCaseAnalyzerStore
-profile myprofile
-cmtos target_object_store
-schemaName schema_name
-dbConnName database_connection
-eventPruneSchedule pruning_time
-publishInterval update_interval
[-silent][-force][-help]
- -profile myprofile
- Specifies the profile to use. The myprofile value
can be one of the following items:
- The name of the profile, such as develop1. The profile is located
in the
install_root/CaseManagement/configure/profiles directory.
install_root is the location where IBM Business Automation
Workflow is
installed.
- The full path to the profile directory, such as "install_root\CaseManagement\configure\profiles\develop1" or /install_root/CaseManagement/configure/profiles/develop1.
- The full path to the profile input file, such as "install_root\CaseManagement\configure\profiles\develop1\develop1.cfgp" or /install_root/CaseManagement/configure/profiles/develop1/develop1.cfgp.
- -cmtos target_object_store
- Specifies the display name for a case management target object
store.
- -schemaName schema_name
- Specifies the name of the schema to use for the Case Analyzer
store.
- -dbConnName database_connection
- Specifies the display name of the database connection. You can
view and define database connections by using the Administration Console for Content Platform
Engine.
- -eventPruneSchedule pruning_time
- Specifies the time each day when unneeded data is to be pruned from the database. Enter the time
in the following format: HH:MM:SS
If you do not specify a time, pruning is
disabled.
- -publishInterval update_interval
- Specifies the interval in minutes when the IBM Case Monitor Dashboard data is to be updated. If
you do not specify an interval, the data is updated every 5 minutes.
- -silent
- Optional: When you specify the -silent parameter,
no prompts or informational messages are shown in the console, but
the errors are written to the log. Failure messages and validation
error messages are shown as needed, such as messages about missing
passwords or invalid port numbers. If you run the execute command
to run all the activities in a profile and you specify the -silent parameter,
you must also specify the
-force parameter.
- -force
- Optional and applies only when the -silent parameter
is used. When you specify the -force parameter,
the activity is run without pausing for required responses to validation
error messages, such as messages about missing passwords or invalid
port numbers.
- -help
- Optional: Shows a brief message on the command syntax instead
of running the command.