Solaris cluster: Prepare the Solaris OS

you want to install for information.

Prerequisites

Prepare the primary node on Solaris
Tune the servers

To prepare OS:

1. To prepare Solaris kernel settings:
   Several Solaris kernel values are typically too small for the messaging requirements of WebSphere Portal. 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 installing WebSphere Portal, review the machine's configuration. The values described here are a starting point for messaging in WebSphere Portal only. If system has other applications installed, the value requirements will likely be different. For example, if values that are already set are higher than the settings listed here, the values should not be lowered. Be sure to check the requirements made on /etc/system by other already-installed applications before altering existing values.

   1. Type the sysdef -i command to review the configuration.

   2. Set shmsys:shminfo_shmmax (valid for Solaris Version 9 only) to 4294967295.

   3. Set shmsys:shminfo_shmmni (valid for Solaris Version 9 only) to 1024.

   4. Set semsys:seminfo_semaem (valid for Solaris Version 9 only) to 16384.

   5. Set semsys:seminfo_semmni (valid for Solaris Version 9 only) to 1024.

   6. Set semsys:seminfo_semmns (valid for Solaris Version 9 only) to 16384.

   7. Set semsys:seminfo_semmsl (valid for Solaris Version 9 only) to 100.

   8. Set semsys:seminfo_semopm (valid for Solaris Version 9 only) to 100.

   9. Set semsys:seminfo_semmnu (valid for Solaris Version 9 only) to 2048.

   10. Set semsys:seminfo_semume (valid for Solaris Version 9 only) to 256.

   11. Set msgsys:msginfo_msgmap (valid for Solaris Version 9 only) to 1026.

   12. Set msgsys:msginfo_msgmax (valid for Solaris Version 9 only) to 65535.

   13. Set rlim_fd_cur to 1024.

   14. Reboot the OS to apply the updates.

2. Web Content Manager only: Use the ulimit -f command to set the maximum size of files that can be created to be at least the size of the largest file you would need to upload to the content server.
   The command ulimit -f -1 removes any limit on file size.

3. Set the file descriptor limit to 10240; for example, ulimit -n 10240.

4. To prepare for non-global zone:

   1. Do not inherit package directories when you create the non-global zone because the inherited software packages will be read-only.

   2. Stop WebSphere Portal and all related processes before installing or uninstalling.

   3. Verify that the following processes are stopped:
      /opt/IBM/WebSphere/AppServer/java/bin/java

      /opt/IBM/WebSphere/AppServer/java/jre/bin/java

Parent

Set up a cluster on Solaris

Related tasks

Prepare the WAS Deployment Manager on Solaris
Prepare to create the cluster on Solaris
Prepare a remote Web server when portal is installed on Solaris in a clustered environment
Configure WebSphere Portal to use a user registry on Solaris in a clustered environment
Prepare additional nodes on Solaris
Configure search in a cluster on Solaris
Set up multiple clusters on Solaris
Share database domains between clusters on Solaris

  Added ulimit -n step.

+

Search Tips   |   Advanced Search