Unsupported content


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Adding remote servers

To enable access to remote servers through the SOCKS proxy server, add a server object to the Servers folder for each remote server, as described in the following procedure. Remote servers are servers on a different network from your BMC Server Automation system or outside your network's firewall.

To add multiple servers to a server hierarchy, you can specify a text file that contains a list of server names and properties assigned to each server. For information, see the Import file topic.

To add a remote server

  1. In the BMC Server Automation Console, open the Servers folder.
  2. Right-click the Servers node (the top node in the Servers folder). Then select Add Server form the pop-up menu. The Add New Server wizard opens.
  3. For Name/IP Address, enter a host name or IP address (IPv4 or IPv6) that can be resolved by either the Application Server or the SOCKS proxy server.
    For Description, you can optionally provide descriptive text.
  4. Click Next.The Permissions panel shows the access control list and permissions for the server.
    If the Add New Server wizard displays the warning that an agent could not be detected on the server and asks if an agent is installed, click Yes. You will resolve this problem in the next few steps of this procedure.
  5. On the Permissions panel, you can add to the Access Control list or edit the existing permissions. To accept the permissions as defined, click Finish.
  6. Set the defined server as a SOCKS proxy server, as described in Creating SOCKS proxy server objects.
  7. Optionally, define routing rules, as described in Creating rules for routing to remote servers.


After creating several remote servers and defining them as SOCKS proxy servers, you might want to group them together in a smart group. To do this, you can define a special property, such as Location, through the Property Dictionary, for all servers in the group. This method is necessary because defining a smart group using IP Addresses does not work if the Application Server cannot resolve the IP address; this is the case where communication to remote servers takes place through SOCKS proxy servers.

Was this page helpful? Yes No Submitting... Thank you