Solaris: Preparing your operating system

Prepare the operating system to ensure a successful installation.

About this task

Several Solaris kernel values are typically too small for the messaging requirements of HCL. Starting the internal JMS server or client with insufficient kernel resources produces a First Failure Support Technology (FFST) file in the /var/errors directory. Before you install HCL, review the server configuration.


  1. These values are are a starting point for messaging in HCL only. If your system has other applications that are installed, the value requirements are likely different.
    For example, if values that are already set are higher than the settings listed here, do not change the values. Be sure to check the requirements that are made on /etc/system by other already-installed applications before you alter existing values.
    1. Type the sysdef -i command to review the configuration.
    2. Set shmsys:shminfo_shmmax to 4294967295 (valid for Solaris Version 9 only).
    3. Set shmsys:shminfo_shmmni to 1024 (valid for Solaris Version 9 only).
    4. Set semsys:seminfo_semaem to 16384 (valid for Solaris Version 9 only).
    5. Set semsys:seminfo_semmni to 1024 (valid for Solaris Version 9 only).
    6. Set semsys:seminfo_semmns to 16384 (valid for Solaris Version 9 only).
    7. Set semsys:seminfo_semmsl to 100 (valid for Solaris Version 9 only).
    8. Set semsys:seminfo_semopm to 100 (valid for Solaris Version 9 only).
    9. Set semsys:seminfo_semmnu to 2048 (valid for Solaris Version 9 only).
    10. Set semsys:seminfo_semume to 256 (valid for Solaris Version 9 only).
    11. Set msgsys:msginfo_msgmap to 1026 (valid for Solaris Version 9 only).
    12. Set msgsys:msginfo_msgmax to 65535 (valid for Solaris Version 9 only).
    13. Set rlim_fd_cur to 1024.
    14. Restart the operating system to apply the updates.
  2. Web Content Manager only: Complete the following steps to remove any file size limits:
    Use the ulimit -f command to set the maximum size of files that can be created. Set this value to at least the size of the largest file you would upload to the content server. The ulimit -f unlimited command removes any limit on file size.
    1. Open a command prompt.
    2. Run the ulimit -a command to get a list of all the ulimit settings.
    3. Find the -f parameter.
      If the value is unlimited, no further action is required.
    4. If the -f parameter is not unlimited, choose one of the following options:
      • Remove the file size limit permanently. For information about how to remove the file size limit see your system documentation.
      • Run the ulimit -f unlimited command for each session.
  3. Prepare for non-global zone:
    1. Do not inherit package directories when you create the non-global zone because the inherited software packages are read-only.
    2. Stop HCL and all related processes before you install or uninstall.
    3. Verify that the following processes are stopped:
      • /opt/IBM/WebSphere/AppServer/java/bin/java
      • /opt/IBM/WebSphere/AppServer/java/jre/bin/java