Meet the Service Manager Server requirements

Before you install the Service Manager Server, you should meet the following requirements.

For information about the supported operating systems and databases, refer to the Service Manager Support Matrix on the HPE Support matrices web site.

Meet the requirements for a Windows system

1. Make sure that you have a compatible operating system with the current updates.

2. The Service Manager Server requires the following database resources.

   Requirement	Resources needed
   RDBMS server	Oracle database MS SQL Server
   RDBMS client	Oracle client Windows ODBC DSN defined for SQL Server

3. Have 1 GB RAM minimum. For production purposes, RAM is based on the expected user load.

   Note To avoid potential out-of-memory issues, we recommend that you run the ulimit -d unlimited command to set the heap size to unlimited before starting the Service Manager Server.

4. Create a local administrator account on the Windows server.
5. Have 1 GB of disk space.
6. Have a valid TCP/IP port that is greater than 1024.

7. Specify the appropriate number of processes. The system starts one process for each sm command line in the sm.cfg file. By default, each process is limited to 50 concurrent user sessions. The system assigns each user session or background process a dedicated thread.

   Note If you start background processes by using the sm system start command in the sm.cfg file, then the sm processes own the background process threads. If you start the background processes from a user session inside Service Manager, then the thread controller process that owns the user session also owns the background process threads.

8. Specify the amount of shared memory that you want the system to allocate. A server uses approximately 50 MB of base shared memory and requires an additional 5 MB of shared memory for every 50 users. You can specify the amount of shared memory the system allocates by using the shared_memory parameter in the sm.ini file.

9. For an Oracle database, update your system's PATH variable to include the path to the 32-bit versions of your RDBMS client. Refer to your operating system documentation for information on setting variables.

   For a Microsoft SQL Server database, configure ODBC DSN.

Meet the requirements for a Linux system

1. Make sure that you have a compatible operating system with the current updates.

2. The Service Manager Server requires the following database resources.

   Requirement	Resources needed
   RDBMS server	Oracle database
   RDBMS client	Oracle database client

3. Have 1 GB of disk space.
4. Have a valid TCP/IP port that is greater than 1024.

5. Specify the appropriate number of processes. The system starts one process for each sm command line in the sm.cfg file. By default, each process is limited to 50 concurrent user sessions. The system assigns each user session or background process a dedicated thread.

   Note If you start background processes by using the sm system start command in the sm.cfg file, then the sm processes own the background process threads. If you start the background processes from a user session inside Service Manager, then the thread controller process that owns the user session also owns the background process threads.

6. Create a separate user ID that owns Service Manager. Service Manager will not run from a root account. You only need root access to modify the system kernel, and mount the Service Manager DVD.
7. Run the installation script from an ANSI terminal to avoid rendering errors. Non-ANSI terminals such as hpterm may produce unreadable results.

8. Update your system's LD_LIBRARY_PATH variable to include the path to the 32-bit versions of your RDBMS client. Refer to your operating system documentation for information on setting variables.

9. Adjust kernel resources. A server uses approximately 50 MB of base shared memory and requires an additional 5 MB of shared memory for every 50 users. You can specify the amount of shared memory the system allocates by using the shared_memory parameter in the sm.ini file.

   The following kernel resource requirements are the minimum values required to run a Service Manager server. If you run other programs that require kernel resources on the same system as Service Manager, then add the Service Manager kernel resource requirements to the existing resources. For example, if the existing system requires 100 MB in kernel resources, and Service Manager requires an additional 50 MB, then update the kernel resources to 150 MB.

   To configure kernel IPC parameters:

   The default shared memory limit (both SHMMAX and SHMALL) is 32 MB, but you can change it from the proc file system without restarting the system. For example, to specify 128 MB:

   # echo 134217728 >/proc/sys/kernel/shmall
# echo 134217728 >/proc/sys/kernel/shmmax

   You can use sysctl.conf to control these parameters. Add the following to the /etc/sysctl.conf file:

   kernel.shmall = 134217728
kernel.shmmax = 134217728

   sysctl.conf is usually processed at startup but can be called later.

   • Modify the kernel parameters as needed:
     • shmmax: This parameter enables you to allocate shared memory. A server uses approximately 50 MB of base shared memory and requires an additional 5 MB of shared memory for every 50 users. Allocate more shared memory than what you specify in the sm.ini file.

     • shmmni: This kernel parameter enables you to set the maximum number of shared memory segments system-wide.

     Note Service Manager uses 12 semaphores, regardless of the number of users logged on to the system.

   • Make sure that the upper limit (ulimit -n size) for file descriptors is at least 1024.

   • Adjust the UDP buffer size to 20MB or higher. For better performance, if there is enough memory available on the server, choose a value larger than 20MB. Linux may generate warnings if the UDP buffer sizing set in the configuration files surpasses kernel limits. For example, a warning might look like the following:

     23966( 23966) 08/11/2009 15:38:33 receive buffer of socket java.net.DatagramSocket@c9d92c was set to 20MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)

     A superuser can change 0 kernel limits to enhance performance of UDP communication. To retrieve the UDP buffer sizing setting, use the sysctl -w net.core.rmem_max command. To change the setting, use the sysctl -w net.core.rmem_max=8388608 command.

10. Make sure that the user running the installation script has permission to create new directories in the chosen installation path.

11. For 64-bit Linux, install the required libraries to support 32-bit Java on a 64-bit system by running the following command as “root”:

    Tip This step is required only when you are using an Oracle jre.

    yum -y install glibc.i686

    You may need to update /etc/yum.repos.d with the working links for the required package if necessary.

    Caution If the required 32-bit libraries are missing from the system, an “Unsupported java version” error will occur later when you configure or start the server by running the configure or smstart script. As a result, you will not be able to configure or start the server.

Next, install and configure the Service Manager Server. See Install the Service Manager Server.