Access Service Manager on a Windows client through an F5 HWLB in HTTP mode

This deployment is suited to testing HPE Service Request Catalog and Service Manager in a development or non-production environment. As you can see from the figure in Access Service Manager through an F5 HWLB in HTTP mode, this configuration does not use HTTPS/SSL encrypted communication. This deployment should be used for sand box, development, or demonstration (proof of concept) purposes.

This section describes how to access Service Manager on a Windows client through an F5 HWLB in HTTP mode.

Step 1: Configure a Windows client to support an external hardware load balancer

To configure a Windows client to support an external hardware load balancer, follow these steps:

  1. Install a new Windows client.
  2. Start the Windows client, and then create a new network connection called hwlb_connect.
  3. Type the IP or host name of the virtual server as the connection's server address.
  4. Type the port of the HWLB virtual server as the connection's server port.
  5. On the Advanced tab, click to select the Connect to External Load Balancer option.

  6. Click Apply, and then click Connect.

Step 2: Enable an HWLB on a Service Manager server

To enable an HWLB on a Service Manager server, follow these steps:

  1. Add the external_lb attribute to the sm.ini file on the Service Manager server.

    Note The external_lb attribute is a system attribute, and every servlet node on the same host should use the same attribute setting. In most cases, this attribute needs to be configured in the sm.ini file when you start a servlet from the operating system command prompt.

    However, to prevent a servlet node from running in external load balancer mode, you can include -external_lb:0 in a command when you start a servlet from the operating system command prompt. As the servlet node does not work in external load balancer mode, it rejects any connections from a hardware load balancer.

    Only -external_lb:0 can be added to a command. -external_lb:1 and external_lb are not recognized in commands.

  2. Make sure that no Service Manager software load balancer  (for example, sm –loadBalancer) is configured or running on the Service Manager server.