The BMC PATROL Agent configuration is saved in a set of configuration variables that are stored in the agent's configuration database. You can control the BMC PATROL Agent configuration by changing the values of these configuration variables. You can use the Configuration Variable option on the Add Policy window to configure the Knowledge Modules (KMs) that are not supported by Central Monitoring Administration or update the existing configuration variables.
Also, you can define a configuration variable, and the definitions are set on BMC PATROL Agent when the policy is applied.
To view configuration variables available in previous BMC PATROL Agent versions, use the Query Agent functionality available in the BMC ProactiveNet Operations Console or Central Monitoring Administration. To edit the configuration variables available in the previous versions, see To edit a configuration variable.
If you have not done so already, perform the steps provided under the following sections:
Perform the following procedure to create or edit a configuration variable.
If you are modifying the Default account configuration, you must restart the BMC PATROL Agent to reflect the changes.
In the Variable box, specify a name for the configuration variable.
The variable names are case sensitive and must start with slash (/). You must enter the complete path for the variable, not just the name. If the intermediate variables do not exist, the variables are created.
defaultAccountconfiguration variable, specify the value in the userName/password format. Note that the password can be a plain text or a BMC PATROL Agent-encrypted string.
SecureStoreconfiguration variable, specify the value in the context/data format. Note that the context and data can be a plain text or a BMC PATROL Agent-encrypted string.
“EDC10278901F8CB04CF927C82828595B62D25EC355D0AF38589CE4235A246F8C63F24575073E4ECD”is the encrypted form of "MY_KM1;MY_KM2;MY_KM3/mysecretdata"
BMC recommends that you do not create a policy with both monitoring configuration and a configuration variable. You can create separate policies for monitoring configuration and configuration variables. See also Configuring a monitor.
To keep the BMC PATROL Agent in sync with the policy configuration, change an existing configuration variable's operation to DELVAR, instead of deleting it.
Once a configuration variable is deleted from the policy, it is not possible to perform actions on it through Central Monitoring Administration.
You can import a configuration variable from a ruleset file (.cfg). The import operation supports only REPLACE, DELETE, and DELVAR operators. If the .cfg file contains the MERGE or APPEND operators, the file cannot be imported, and you must delete the operators before importing the file.
If the ruleset file is in a non-English language, ensure that the file is encoded in the UTF-8 format. The import process does not support the non-English ruleset files that are encoded in the ANSI format.
Perform the following steps to import the configuration variable:
Navigate to the location of the .cfg file, select the file, and click Open.