Configuring a vertical scaling environment

This configuration is intended for customers who:

• Want to maximize the number of client connections supported on a single host
• Have a host with enough system resources to manage all concurrent client connections

Terminology

• Group: A group of Service Manager server processes running on one or more hosts and connecting to one database to serve Service Manager server processes within a group.
• Node: A Service Manager server process within a group.
• Service Manager servlet process: A Service Manager server process that embeds the Tomcat application server and serves Service Manager Windows clients and Web clients, as well as Web Services requests. It is also generally referred to as a Service Manager process.
• Service Manager background process: Background processes that wake up periodically to execute a particular RAD application, or Service Manager runtime environment routine. For example: sm -que:ir.
• Service Manager transient process: A Service Manager server process that executes a RAD application or Service Manager runtime environment routine only once, not periodically. For example: sm -reportlbstatus.

Commands required in sm.cfg

You must set the following configuration commands.

sm -loadBalancer -httpPort:<value>
sm -httpPort:<value> -httpsPort:<value>
sm system.start

• sm -loadBalancer -httpPort:<value> – Is a special Service Manager servlet process that redirects client connections requests to other available Service Manager processes.
• sm -httpPort:<value> -httpsPort:<value> – Specifies the HTTP or HTTPS communications port for one Service Manager servlet process. Each Service Manager process by default can host 50 users. You can start as many Service Manager servlet processes as you want, as long as your server has enough physical memory and resources to start the processes. You can also change the number of users hosted on one Service Manager servlet process by setting the "threadsperprocess" parameter.

Optional parameters in sm.ini

The following initialization parameters are optional.

threadsperprocess:<value>
preferredFQHN:<value>
groupbindaddress:<value>

• threadsperprocess – Defines the maximum number of concurrent user sessions per Service Manager servlet process. Use a value that maximizes the system resources of your Service Manager host. The recommended maximum value for the parameter threadsperprocess is 60. Usually the value of this parameter should be below 50.
• preferredFQHN – Specifies the fully qualified host name you want Service Manager clients to use when communicating with the server. Service Manager loadBalancer redirects client requests to the target host with the target host's "preferredFQHN." You only need to set this parameter if your Service Manager host is identified by multiple names in the network.
• groupbindaddress – Defines the TCP/IP address of the network adapter you want Service Manager processes to use to communicate with other processes in the group.

Memory requirements

We recommend around 1.5 GB RAM per Service Manager process. This is based on the expected user load. For example, if you have 10 processes each running with a 50-user load, the minimum required RAM would be 1.5 GB per Service Manager process, 10x1.5 GB RAM. For information on sizing, refer to the Service Manager 7 Reference Configurations sizing guide in the Micro Focus online support knowledge documents at the following URL: https://softwaresupport.softwaregrp.com.

Licensing requirements

Obtain an AutoPass license for your vertical scaling environment. On Windows platforms, AutoPass installs as part of the server installation. On Unix platforms, you must install it manually before you can run Service Manager. For more information, see Service Manager Installation in the related topics. AutoPass includes this host's IP address in the LicFile.txt file.

Do the following:

• Get the license from the Micro Focus Web site.
• Copy the primary server's IP address to get the license and save it as the primary server's LicFile.txt file. The default directory for this file is as follows:
  • On Windows: C:\Program Files\Common Files\Hewlett-Packard\HPOvLIC\data\LicFile.txt
  • On Unix: /var/opt/OV/HPOvLIC/LicFile.txt

Related topics