Creating rules for routing to remote servers

To create rules for routing communications to remote servers through a SOCKS proxy server, use the New Rule wizard. This wizard creates a default SOCKS proxy server routing policy and simple rules that the Application Server uses for routing to remote servers.

Note

  • To create the SOCKS Proxy Server routing policy, the default network routing policy is modified. Modifying the routing policy affects the entire BMC Server Automation system. Information you enter in the wizard should be in keeping with your team's strategy for routing to remote servers.
  • To create, modify, or delete routing rules, your role must be granted the RoutingPolicy.Modify and the BL_Administration.Read authorizations.
  • If you plan to provision a remote server that is accessed through a SOCKS proxy server, you must define the routing rule for the server before provisioning it.
  • If you set up routing rules based on intrinsic properties such as HOST, the rule no longer works if the property gets updated.

To create rules for routing communications to remote servers

  1. Select Configuration > Infrastructure Management.
  2. In the left pane of the Infrastructure Management window, right-click the Network Routing Rules node and select New Rule. The New Rule wizard opens.
  3. Complete the New Rule Wizard, as described in the following sections:

  4. Click Finish to close the New Rule wizard.
    The network routing policy is set to route through SOCKS proxy servers according to the rules you created. The Infrastructure Management window lists the rules under the Network Routing Rules node.

    Note

    The system detects communication requests to localhost and to IP address 127.0.01 (as in the case when the file server resides on the same host as the Application Server) and does not evaluate routing rules for these requests.

  5. Click Close to close the Infrastructure Management window.

 

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