Skip to Content
Information
Important

This KM is deprecated and will be replaced by the BMC Helix AIOps OTel Collector. For information about the BMC Helix AIOps OTel Collector, see the BMC Helix AIOps documentation at https://docs.bmc.com/xwiki/bin/view/IT-Operations-Management/Operations-Management/BMC-Helix-AIOps/aiops253/.

This documentation space contains information about PATROL Agents when deployed in a BMC Helix Operations Management environment. If you are a TrueSight Operations Management user, see PATROL Agent 24.3.01

Defining the PATROL cluster-specific environment variables for UNIX

In this task, you define the PATROL cluster-specific environment variables in the .profile (Korn and Bourne shell) or .cshrc file (for C shell) of the account used to start the agent. This action ensures that the agent reads configuration information and writes history information to the same set of files, regardless of which host it is running on.

Perform the following task on each node in the cluster.

For Korn and Bourne shells, use the following format:

 PATROL_VIRTUALNAME_<port>=<virtual server name>
PATROL_HISTORY_<port>=</History_Directory>
PATROL_CONFIG_<port>=</Config_Directory>

export PATROL_VIRTUALNAME_<port>
export PATROL_HISTORY_<port>
export PATROL_CONFIG_<port>

For C shell, use the following format:

setenv PATROL_VIRTUALNAME_<port> <virtual server name>
setenv PATROL_HISTORY_<port> </History_Directory>
setenv PATROL_CONFIG_<port> </Config_Directory>

For more information about specific variables, see PATROL cluster-specific environment variables for history and configuration.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL Agent for BMC Helix Operations Management 25.3.01