Configuring PATROL Agents to support a forward proxy server
This topic provides instructions to configure a PATROL Agent to communicate with the proxy server.
You can set up a proxy server in your infrastructure environment so that PATROL Agents can communicate with BMC Helix Operations Management via the proxy server to create an additional layer of security. Setting up a proxy server is optional. To understand how to create a proxy server as a docker container, see Installing-a-Squid-proxy-server.
PATROL Agent uses the following variables to configure the proxy server:
- /AgentSetup/integration/forwardProxyServer
- /AgentSetup/integration/forwardProxyUser
- /SecureStore/mca/tenant/forwardProxyPassword
You can configure the proxy server in one of the following ways:
- During the installation of PATROL Agents
- After the installation of PATROL Agents
To configure the proxy server during the installation of PATROL Agents
While installing a PATROL Agent, you can provide the proxy server details in the RunSilentInstall install command as shown in the following example:
For more information, see Installing-PATROL-Agents.
To configure the proxy server after the installation of PATROL Agents
After a PATROL Agent is installed, provide the proxy server details by configuring the following variables using the pconfig utility:
- /AgentSetup/integration/forwardProxyServer
- /AgentSetup/integration/forwardProxyUser
- /SecureStore/mca/tenant/forwardProxyPassword
The following example shows how to set these configuration variables:
PATROL_CONFIG "/AgentSetup/integration/forwardProxyUser" = {REPLACE = "user1"}
PATROL_CONFIG "/SecureStore/mca/tenant/forwardProxyPassword" = {REPLACE = "MCA/user123"}
Note: Restart the PATROL Agent for the forwardProxyPassword changes to take effect.
For more information about the pconfig utility, see Using-the-pconfig-utility-to-modify-PATROL-Agent-configuration-variables.