Running Web Services on a dedicated port (servlet)

To create a separate servlet within a horizontally or vertically scaled Service Manager system, add the debugnode parameter to the dedicated servlet container. The debugnode parameter stops the load balancer from distributing client load to this node. This can be used to set up a dedicated servlet for tracing and logging without adding an uncontrollable amount of load to that servlet. Another use is to create a dedicated servlet for a special purpose within the scaled solution. As an example, refer to the following sm.cfg file:

#load Balancer Port
sm -loadBalancer -httpPort:13080
#Ports for loadBalanced Connections
sm -httpPort:13081 -httpsPort:13082 
sm -httpPort:13083 -httpsPort:13084
sm -httpPort:13085 -httpsPort:13086
#Port for Web Services 
sm -httpPort:13087 -debugnode
 

Current limitations of running Web Services through the load balancer:

  • The HTTP 307 redirect is not fully compliant with the specifications which can affect Web Services integrations through the Service Manager Load Balancer. The workaround is to connect directly to one of the Service Manager Application server servlets.
  • Web Services through the Service Manager Load Balancer are not possible when SSL is enabled on the server.
  • Web Services through the Service Manager Load Balancer are not possible for Web Services clients that can't handle a redirect.