Flow Monitoring

The parameters in the FLOW_MONITORING section of the file govern how collaboration event records are logged.The Flow Monitoring tables store event information for flows that are traced from IBM MQ Workflow (MQWF) through InterChange Server. Reserve at least 20 MB for this table space.

Note:
Flow Monitoring does not support the viewing of business data. It only tracks the flow of data throughout the ICS.

For complete information on this feature, please refer to the System Administration Guide.

IS_SYSTEM_ACTIVE

The parameter that specifies whether collaborations log event records.

If this parameter is set to true, all collaborations that are configured for monitoring logs event records.

If this parameter is set to false, no collaboration, even if it is configured, logs event records.

MAX_QUEUE_DEPTH

The maximum number of events allowed inmemory (within the Server) before collaborations blocked from queueing events.

All configured collaborations will have the same maximum queue depth.

All changes to this value are immediately saved in the InterchangeSystem.cfg file, but do not take effect until the server has been rebooted.

Default

IS_SYSTEM_ACTIVE = FALSE

DATA_SOURCE_NAME

The name of an IBM-branded driver or DB2 JDBC type 2 driver data source where the flow monitoring services stores information about flows. For further explanation of the JDBC URL, refer to the System Administration Guide.

Example: DATA_SOURCE_NAME = jdbc:ibm-crossworlds:oracle:\\@server : 1521 ; SID=FlowDB

Default

There is no default value for this parameter.

MAX_CONNECTIONS

The number of database connections InterChange Server can open on behalf of the flow monitoring service. Set this parameter only if you have partitioned the InterChange Server workload across databases.

Example: MAX_CONNECTIONS = 30

Default

MAX_CONNECTIONS = 2147483647

DB_CONNECT_RETRIES

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 amount of time to wait between retries.

Default

DB_CONNECT_RETRIES = 3

DB_CONNECT_INTERVAL

Specifies the amount of time to wait between database connection retries. The recommended time is 60 seconds. Setting the retry interval too high will slow the system down unnecessarily. Setting the retry interval too low might lead to ICS shutdowns for database connectivity issues.

Default

DB_CONNECT_INTERVAL = 60

SCHEMA_NAME

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.

Default

The SCHEMA_NAME parameter defaults to the same value used for the USER_NAME parameter.

USER_NAME

This parameter is 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 nondefault login account.

In an environment where all services of InterChange Server use the same DBMS, and where you have changed the user name and password of the login account, this value must be the same for Repository, Event Management, Transactions, and Flow Monitoring.

In an environment where you have partitioned InterChange Server 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 table creation privileges.

Example: USER_NAME = flowmon

PASSWORD

This parameter is required.

The encrypted password associated with the user name for the flow monitoring service.

Example: PASSWORD* = a6gefs

Note:
Do not attempt to change the encrypted password. See the "Encryption for Passwords" section in the System Administration Guide for more information about how password encryption works.

Copyright IBM Corp. 1997, 2004