BMC PATROL for Sybase supports configuration of different Sybase environment such as Adaptive Server Enterprise (ASE), Replication Server, Adaptive Server IQ (IQ Server), and SQL AnyWhere without the usage of PATROL Console or CMA. This can be performed using PATROL Configuration Manager (PCM). This section describes how to configure Sybase environment using PATROL Configuration Manager.
You can use BMC PATROL Configuration Manager to configure Sybase environment by using the following methods:
Before using PATROL Configuration Manager to change the configuration of a Knowledge Module (KM), BMC recommends that you ensure that PATROL Configuration Manager is set up to save or back up the configuration.
To enable backups in PATROL Configuration Manager, perform the following steps:
You can configure the Sybase environment using the following template:
PATROL_CONFIG "/SYBASE/EnvList" = { REPLACE = "<input>INSTANCE_NAME</input>" }, "/SYBASE/<input>INSTANCE_NAME</input>/JAVA_HOME" = { REPLACE = "<input>JAVA_HOME</input>" }, "/SYBASE/<input>INSTANCE_NAME</input>/javaExecuteArguments" = { REPLACE = "<input>JAVA_ARGUMENTS</input>" }, "/SYBASE/<input>INSTANCE_NAME</input>/debugFlag" = { REPLACE = "<input>DEBUG_FLAG</input>" }, "/SYBASE/<input>INSTANCE_NAME</input>/CollectionDetails" = { REPLACE = "<input>COLLECTION_DETAILS</input>" }, "/SYBASE/<input>INSTANCE_NAME</input>/CustomAppList" = { REPLACE = "<input>CUSTOM_DETAILS</input>" }, "/SYBASE/<input>INSTANCE_NAME</input>/ServerName" = { REPLACE = "<input>SYBASE_SERVER_NAME</input>" }, "/SYBASE/<input>INSTANCE_NAME</input>/Port" = { REPLACE = "<input>SYBASE_PORT_NUM</input>" }, "/SYBASE/<input>INSTANCE_NAME</input>/UserName" = { REPLACE = "<input>SYBASE_USER_NAME</input>" }, "/SecureStore/SYBASE/<input>INSTANCE_NAME</input>/Password" = { REPLACE = "SYBASE;SYBASE_ANYWHERE;SYBRS_SERVER;SYBIQ_SERVER;SYBASE_SQL_SERVER;SYBASE_SQL_CONTAINER;SYABSE_CUSTOM_SQL/<input>PRIVILEGED_ACCOUNT_PASSWORD</input>" }, "/SYBASE/<input>INSTANCE_NAME</input>/Type" = { REPLACE = "<input>SYBASE_TYPE</input>" }, "/SYBASE/SQL/CMASQLList" = { REPLACE = "<input>QUERY_ID</input>" }, "/SYBASE/SQL/<input>INSTANCE_NAME</input>/<input>QUERY_ID</input>/cycle" = { REPLACE = "<input>CYCLE_MIN</input>" }, "/SYBASE/SQL/<input>INSTANCE_NAME</input>/<input>QUERY_ID</input>/dbName" = { REPLACE = "<input>DB_NAME</input>" }, "/SYBASE/SQL/<input>INSTANCE_NAME</input>/<input>QUERY_ID</input>/id" = { REPLACE = "<input>QUERY_ID</input>" }, "/SYBASE/SQL/<input>INSTANCE_NAME</input>/<input>QUERY_ID</input>/queryName" = { REPLACE = "<input>QUERY</input>" }
The following procedure explains how to use the PATROL Configuration Manager menu commands to configure Sybase environment.
Double-click the highlighted space in the Value column and enter the value of the variable.
Click OK.
Repeat the above steps for all the rules.
For more information about adding a variable or RuleSet by using PATROL Configuration Manager, see the PATROL Configuration Manager User Guide.
The PATROL Configuration Manager CLI processes a script file that contains commands regarding RuleSets.
To perform BMC PATROL for Sybase configuration using the PATROL Configuration Manager RuleSets, you must set values for the configuration variables in the PcmConfig.cfg file. After you provide values in the file for configuring Sybase environment, you can apply the configuration to the PATROL Agent using the PATROL Configuration Manager CLI. For a list of configuration variables that you can include in the .cfg file, see Configuration variables.
Store your .cfg files in any directory under the %BMC_ROOT%/pconfmgr/rulesets directory, and use the following command to apply the RuleSets:
pcm.cmd -f
scriptFileName
pcm.sh -f
scriptFileName
The scriptFileName variable represents the script file that contains commands to be executed for applying RuleSets. For example, to apply RuleSets for configuring custom monitor, enter the following command in the script file:
apply -a agentName ALL
Where, ALL is the name of the RuleSets file.
Note
In the preceding command:
For more information about the commands and options that can be used in a script file, see the PATROL Configuration Manager User Guide and Configuration variables.