The Cross-Enterprise_APM_Dynamic.properties file is the main configuration file, in that it allows you to specify these settings for CA Cross-Enterprise APM:
Determines whether metrics are collected from any CA Insight DPM instance running on the local system.
Specifies the TCP/IP port that the local Xnet agent subtask of CA Insight DPM uses to listen for query requests. This Xnet agent subtask must be enabled and configured for the Cross-Enterprise APM Agent to collect DB2-specific metrics. The value corresponds to the PORT parameter for Xnet. CA APM uses this property with the Insight.connection.hostname property to connect to Xnet.
Determines whether to use PassTickets when sending authentication information to the Xnet agent subtask of CA Insight DPM. To use the PassTicket authentication, you require the following conditions:
Important! When setting up PassTicket support for CA APM, be sure to complete the security product configuration and enable Xnet PassTicket support before setting this property to "yes". If Xnet PassTicket support is not enabled and CA APM generates a PassTicket, the connection request fails. After some number of failed attempts, the security product will suspend that user ID.
If this property is set to “yes”, PassTickets are used for the authentication instead of user passwords. If this property is set to “no”, specify a valid user password in the Insight.password configuration property.
If the Insight.passticket.support property is set to “yes”, use this property to specify the application name for the generation of PassTicket authentication tokens. The Xnet agent subtask of CA Insight DPM must be configured to use this application name by specifying the same value in the PASSNAME() configuration parameter.
Specifies the user name sent to the Xnet agent subtask of CA Insight DPM for authentication. This property must always be specified, regardless of whether PassTicket support is enabled.
Specifies the user password sent to the Xnet agent subtask of CA Insight DPM for authentication. If PassTicket support is not enabled, this property must be specified. If PassTicket support is enabled, this property is blank. For security reasons, always use the PassTicket authentication to avoid storing unencrypted passwords in the configuration file.
Specifies which local DB2 instances the Cross-Enterprise APM Agent monitors. A connection is established to each data collector instance of CA Insight DPM that is monitoring a DB2 subsystem in this comma-separated list. To collect metrics from all local CA Insight DPM data collector instances that are monitoring DB2 subsystems, specify the “*” wildcard character for this value of this property.
The following “Insight” configuration properties influence the collection performance of metrics from local DB2 subsystems:
Specifies how often the Cross-Enterprise APM Agent performs the following tasks:
The default value is adequate for most situations, but this value can be changed if necessary.
Default: Half the value of the Insight.update.interval parameter
Specifies how many operating system threads are used to process the tasks that are defined to run during the DB2 subsystem refresh interval. If you want the DB2 subsystem refresh interval to execute more quickly, increase the value. The increased value allows multiple tasks to execute simultaneously (at the cost of increased CPU consumption during the refresh interval).
Default: 1, which means a single thread is used to issue status queries to each configured DB2 subsystem
Specifies how often the Cross-Enterprise APM Agent retrieves updated metric values from each configured DB2 subsystem. The value can be increased, which decreases the rate configured DB2 subsystems have to process metric value queries.
Default: Value of the SYSVIEW.update.interval property
Specifies how many operating system threads are used to process the metric value queries for each configured DB2 subsystem. If you want the metric update interval to execute more quickly, increase the value. The increased value allows multiple queries to execute simultaneously (at the cost of increased CPU consumption during the metric update interval).
Default: 1, which means the same thread is used to process sequentially each configured DB2 subsystem query
The properties file contains explicit detail, examples, and lists the configuration options available to help you determine what best suits your environment.
Follow these steps:
The changes will be applied after the agent picks them up dynamically.
|
Copyright © 2013 CA.
All rights reserved.
|
|