Create dedicated Web Services listeners

An HPE Service Manager system configured for vertical or horizontal scaling uses a Load Balancer to redirect client connection requests to an available Service Manager process. A system that also has many Web Services may need a Load Balancer for multiple nodes. Service Manager's Web Services do not support http redirect, and will fail to clean up the resources on the Service Manager loadBalancer process, if the loadBalancer port is used as the endpoint URL. For this reason, HPE recommends creating one or more Service Manager processes dedicated to Web Services requests. You can then configure any external Web service clients to connect directly to the dedicated Service Manager processes. If your system needs a load balancer, use a hardware load balancer to balance between a set of servlets with the debugnode parameter.

  1. Log in to the host running Service Manager with an administrator account.
  2. Stop the Service Manager server.

    Note It is not necessary to stop and start the Service Manager server to add a new port. You can add the line to the sm.cfg file while the system is running and start that same port from a command prompt manually.

  3. Open the sm.cfg file, and create a dedicated Service Manager process to listen for Web Services requests using the -debugnode parameter. For example, the following entries create a dedicated process listening on ports 13085 and 13445.

    sm -httpPort:13080 -loadbalancer
    sm -httpPort:13081 -httpsPort:13443
    sm -httpPort:13083 -httpsPort:13444
    sm -httpPort:13085 -httpsPort:13445 -debugnode

    Note The debugnode parameter tells the Service Manager Load Balancer not to forward any client connection requests to this Service Manager process. Only clients that directly connect to the process can access it.

  4. Restart the Service Manager server.
  5. Configure any external web service clients to connect directly to the Service Manager processes running in debugnode. For example, set the endpoint URL to http://<fully qualified host name>:13085/SM/7/<Service Name> for normal connections and set the URL to https://<fully qualified host name>:13445/SM/7/<Service Name> for SSL-encrypted connections.