[QP_Object_Manager_Service]

The [QP_Object_Manager_Service] stanza is used to configure the database type, database name, user name, and password that is used by the TrueSight Middleware and Transaction Monitor Management Console to connect to the database. Usually this section of the services.cfg file is empty.

Parameter

Description

db2_cur_commit_check

Default: on. DB2 CUR_COMMIT (currently committed, DB2 database wide parameter) check. If this DB2 parameter cannot be turned off as it is recommended for MainView Middleware Monitor 8.1 DB2 databases (for example, MainView Middleware Monitor shares the same database with other applications that require such database parameter to be turned on), the keyword can be used to disable the check: db2_cur_commit_check=off. When the database parameter (cur_commit) is turned on MainView Middleware Monitor services generates at least twice the transaction logging because of concurrent reads from MainView Middleware Monitor tables.

db_authentification

Defines the source MainView Middleware Monitor uses to authenticate the user name and password used to connect to the database. If this field is defined, then db_type= and db_name= must also be defined. Possible values: MainView Middleware Monitor uses the currently logged in TrueSight Middleware and Transaction Monitor user name and password.

db_clob_buffer_size

Defines the size of the buffer used by the database. Using this field makes your MainView Middleware Monitor database operate more efficiently by segmenting the buffer size. CLOB is a DB2 term. Below are the analogous terms for other databases.

Oracle: LONG
SQL Server: TEXT
DB2: CLOB

The db_clob_buffer_size is defined in bytes. Valid values are 0 to 8,500,000 (any number larger than 1000 should be typed without separating characters, for example, 8500000). Default value is 128000.

db_connect_pool_size

Default: 2. Defines the number of additional database connections used by the Topic Service. The minimum value is 0 and the maximum is 64. Regardless of the value you specify, one main database connection always exists. The recommended setting for this value is the number of demarshaller threads (demarshaller_threads under the Topic_Service section plus threads under BTM_Service) or the number of CPUs of your database machine, whichever is smaller.

db_connect_string

Defines the user name, password, and name of the database to which MainView Middleware Monitor connects. The syntax is: username/password@database_name.

In order to specify OS user credentials as database credentials, use the following database connect string: /@database_name.

db_name

Defines the name used to connect to the database. It is a TNS name for Oracle, local DB2 database alias (as defined in the local DB2 client configuration) for DB2, and an ODBC DSN for MS SQL Server.

db_password

Defines the password for the user account from the db_username= field. An encrypted password can be generated from plain text with mqusertool.

db_type

Defines the type and version of the database you are using with MainView Middleware Monitor. These values are not case-sensitive. The possible values are:

DB2
ORACLE
MSSQL

db_username

Defines the user name used to connect to the database.

db_version_check

Defaults to "true". If the database connect function detects an unsupported database server version, it logs an error message in the corresponding log file of the MVMM 9.0 service from which the database connect function is called (see Database server requirements for further information on the supported database server versions).

MVMM services will not start when db_version_check is set to "true" if the database connect function detects an unsupported database server version.

MVMM services can still tolerate older database server versions; below is the full list of database servers that can be tolerated (however, it is not recommended to use older database servers because MVMMhas limited test coverage for these servers, as well as performance issues):

  • SQL Server 2008 R2
  • DB2 9.7
  • DB2 10.1

In order to disable the database server version check, db_version_check should be set to "false".

db_watchdog_interval

Defaults to 300 seconds; Database API watchdog. This keyword applies to all services. The watchdog keeps track of the database API health as well as the total number of database connections. When a database bound call takes longer than a specified number of seconds,or the total number of database connection drops down to 0, the watchdog logs a statistical message (QP_LM_STAT) for the first specified number of times (see db_watchdog_max_tries for more detail) in the corresponding log file. After the specified number of tries is reached, the watchdog logs its messages as alert messages (LM_ALERT). If db_watchdog_exit_action is set to true, the service exits when the specified number tries is reached.

db_watchdog_exit_actionDefaults to false; Database API watchdog. If db_watchdog_exit_action is set to true, the service exits when the watchdog reaches db_watchdog_max_tries. If db_watchdog_exit_action is set to false, the watchdog does not force the service to exit, the watchdog just keeps logging its messages as alert messages (LM_ALERT) after db_watchdog_max_tries is reached (see db_watchdog_interval for more detail).
db_watchdog_max_tries

Defaults to 6; Database API watchdog. This keyword applies to all services. The watchdog logs statistical (QP_LM_STAT) messages in the corresponding log files when it finds hanging SQL statements, or when the total number of database connections drops down to 0. Hanging SQL statements are statements that execute longer than the number of seconds specified in db_watchdog_interval. This keyword specifies the maximum number of tries before the watchdog logs messages as alert messages (LM_ALERT).

event_journal_db_commit_delay

Default: 0 (seconds). Specifies the amount of time in seconds to delay before saving an event journal entry to the database. If the value is set to 0, the commit occurs immediately.

last_sample_data_age_threshold

Defaults to 300 seconds; Threshold for calculating last sample age. When LastSampleTimestamp is older than the current system time of the Topic Service host machine by the specified threshold number of seconds, the last sample age attribute gets set to current system time - last sample timestamp in seconds.

last_sample_data_sweep_period

Defaults to 120 seconds (2.5 times smaller than last_sample_data_age_threshold); Last Sample Data Sweep Period. The Topic Service makes last sample data sweeps at the specified frequency (period) in order to calculate last sample ages, which are used by the Management Console to display warnings about stale data.

mssql_letter_collation_check

Defaults to "true". If the database connect function for MS SQL detects a case sensitive letter collation, it logs an error message in the corresponding log file of the MVMM service from which the database connect function is called. For more information, seeDatabase server requirements.

MVMM services will not start when mssql_letter_collation_check is set to "true" if the database connect function detects a case insensitive letter collation.

In order to temporarily disable the MS SQL database letter collation check, mssql_letter_collation_check should be set to "false".

preload_volatiles

Defaults to on; Preloading of volatile attributes. Possible values are off/on/all. "All" means that all volatile attributes get preloaded by the Topic Service at startup. "On" means that the Topic Service preloads only volatile attributes that are associated with a history rule or template, and it preloads LastSampleAge, LastSampleTimestamp attributes for all objects that have such attributes. 

preload_logical_attributes

Defaults to "All". Preloading of logical attributes. Possible values are "NONE", "PA", "BTM" or "All". "NONE" indicates to not preload any logical attributes. "PA" means to preload only performance and avalability logical attributes. "BTM" indicates to preload only BTM related logical attributes. "ALL" indicates to preload them all.

This keyword is ignored for the Application Service.

seconds_between_db_pings

Default is 30 seconds. The range of valid values is 10 to 86400. MainView Middleware Monitor services will ping all of their database connections in order to keep the connections alive according to the value defined. This may be required if a firewall sets a timeout on idle TCP/IP connections, or if Oracle IDLE_TIME is used.

Was this page helpful? Yes No Submitting... Thank you

Comments