The parameters in the FLOW_MONITORING section of the file govern InterChange Server's use of a database on behalf of the flow monitoring service. This service is not required unless you want to monitor collaborations registered with the IBM WebSphere Business Integration Monitor tool, where the source adapter is the IBM WebSphere Business Integration Adapter for MQ Workflow.
Required
The name of an IBM-branded driver or DB2 JDBC type 2 driver data source where the flow monitoring service stores information about flows. For an explanation of the JDBC URL, refer to the System Administration Guide.
Example: DATA_SOURCE_NAME = jdbc:ibm-crossworlds:oracle:// @server:1521;SID=FlowDB
There is no default value for this parameter.
Specifies whether collaborations configured for flow monitoring log event records. Possible values are "TRUE" and "FALSE." If set to "TRUE," all collaborations which are configured for monitoring will log events. If set to "FALSE," no collaborations, even if configured, will log event records.
IS_SYSTEM_ACTIVE = FALSE
Specifies how many database connections InterChange Server can open on behalf of the flow monitoring service. Set this parameter only if you have partitioned InterChange Server work load across database servers.
Example: MAX_CONNECTIONS = 30
MAX_CONNECTIONS = 2147483647
Required
The name that InterChange Server uses to log in to the data source on behalf of the flow monitoring service. Use this parameter to specify a non-default login account.
In an environment where all services of InterChange Server are using the same DBMS, and where you have changed the user name and password of the login account, this value should be the same under Repository, Event Management, Transactions, and Flow Monitoring.
In an environment where you have partitioned InterChange Server's use of database resources across multiple DBMS servers, you can have a different user name for each DBMS server. In that case, this parameter specifies the user name that InterChange Server uses on behalf of the flow monitoring service. The account must have the privilege to create tables.
Example: USER_NAME = flowmon
There is no default value for this parameter.
Required
The encrypted password associated with the user name for the flow monitoring service.
Example: PASSWORD*=a6gefs
The name of the database schema where the flow monitoring event table resides. Use this configuration value if you want to manage flow monitoring event data under a schema different than the flow monitoring database login user (the user identified by the USER_NAME parameter).
Valid values for this field can contain up to 30 characters from the US-ASCII character set. The name must begin with a letter from A through Z and the first three characters cannot be SYS. Other characters in the name can include the letters A through Z and numbers 0 through 9. For information on the prerequisite software needed to utilize flow monitoring, as well as detailed explanations of flow-monitoring concepts, see the System Administration Guide.
The SCHEMA_NAME parameter defaults to the same value used for the USER_NAME parameter.
The maximum number of events allowed in memory (within the InterChange Server) before collaborations wait to enqueue additional events.
During flow monitoring, many events are recorded for every single flow in a traced collaboration, resulting in large amounts of database activity that can degrade performance. To prevent excessive performance degradation, the collaboration flows write monitor events to a memory queue within the InterChange Server. The contents of this in-memory queue are subsequently transferred to the database. To prevent the server from running out of memory, this queue is of a bounded size defined by the MAX_QUEUE_DEPTH parameter. If the queue depth does not permit a new monitor event to be logged, the corresponding collaboration flow waits to enqueue it before proceeding with the flow processing.
This parameter is configurable system-wide (not per collaboration) from the System Manager's "Edit configuration" editor, under the MISC tab. Each monitored collaboration maintains an independent queue, which holds the number of events specified by this parameter, to a maximum of 2147483647 events. When changes are made to this parameter, they are saved immediately to the InterchangeSystem.cfg file, but do not take effect until after the server is restarted. All configured collaborations will have the same maximum queue depth. For more information about this parameter, see the System Administration Guide.
MAX_QUEUE_DEPTH = 500
Specifies the maximum number of times that the server will try to reconnect to the database after the connection is found to be broken. The recommended retry count is 3. If the value is set to 0, this is equivalent to switching off the database connectivity resilience.
Use the DB_CONNECT_INTERVAL parameter to specify the time to wait between retries. The recommended time is 60 seconds.
The DB_CONNECT_RETRIES parameter and the DB_CONNECT_INTERVAL parameter in this section act upon the flow monitoring database. If database connectivity issues occur during communication between the server and the flow monitoring database, this pair of parameters controls how often and how frequently the server will try to reconnect to that database.
DB_CONNECT_RETRIES = 3
Specifies the time to wait between retries. The recommended time is 60 seconds. Setting the retry interval too high will slow the system down unnecessarily.
Set this value in the InterchangeSystem.cfg file in the [FLOW_MONITORING] section. The value you specify is in seconds.
DB_CONNECT_INTERVAL = 60