Performance information can begin to be collected after Enterprise Managers, Managers, Proxy Managers and Agents have been installed and a collection policy has been created and applied.
Note
When the following operation is done with the object server, re-creation of policy and collection of the configuration information on the Operation Management Client is required.
When the Information Collection Policy is changed
EXAMPLE:
Changing the collection template (template.dat)
Changing the response and managed object configuration information (ServiceConf.xml)
When the cooperate middleware is installed
EXAMPLE:
Installing the Symfoware Server
When the cooperate middleware is uninstalled
EXMPLE:
Uninstalling the Operation Manager
When the cooperate middleware settings are changed
EXAMPLE:
Changing the Interstage settings
Changing the Symfoware Server settings
Changing the Oracle settings
Changing Centric Manager linkage settings
When the hardware organization of the server is changed
EXAMPLE:
Changing the single/multi processor of the Linux server
When the environment of the OS is changed
EXAMPLE:
Changing host name
Changing sysatat's version by applying Linux patch
When the definition file is changed by changing IP address, user name, and/or password of the monitoring server for agents for Agentless Monitoring
EXAMPLE:
Changing the connection account configuration file (remoteAccount.txt)
Changing the remote monitoring configuration file (remoteAgent.txt)
When the definition file is changed by changing IP address of the monitored object for ECO information
EXAMPLE:
Changing the configuration information file of SNMP agents (ecoAgentInfo.txt)
Changing the ECO information collection definitions file (collectOID.txt)
Point
Broadly speaking, two types of information are collected:
Server resource information (information that can be collected by Enterprise Managers, Managers, Proxy Managers and Agents)
Response and operational information (information that can be collected by Managers and Proxy Managers)
A collection policy must first be created and then applied.
A policy that has been applied can be modified temporarily.
Commands are provided for each of these operations.
Information collection begins with the creation of a collection policy. Always create a collection policy before attempting to apply it.
Some of the policy commands explained in this manual run on a server and some run on an operation management client.
Execution environment | Command name | Use |
|---|---|---|
Enterprise Manager/Manager/Proxy Manager/Agent | 1.1.1 sqcRPolicy (Server Resource Information Collection Policy Creation Command) | These commands are used for collecting performance information. |
1.1.2 sqcAPolicy (Response / Operation Information Collection Policy Setup Command) | ||
This command temporarily changes (stops/starts) the collection operation. | ||
Operation management client | 1.1.5 sqcViewPolicy (Policy Definition Information Verification Command) | These commands are used when the policy distribution function is used. |
1.1.6 sqcSendPolicy (Policy Definition Information Distribution Command) | ||
Refer to "Policy Distribution" in the User's Guide for details on the policy distribution function.
Creating and applying a policy on the server from which performance information is to be collected
Using the policy distribution function
Point
The policy distribution function is particularly effective when distributing the same definitions to multiple servers. Use this function according to the number and status of the managed servers.
