Before you can install IBM® Business Process Manager, you
must prepare your Solaris operating system.
About this task
Because certain steps are specific to a version of the
operating system, all steps might not apply to your environment. If
no qualifier is provided for a particular step, complete the step
for all versions of the operating system.
Procedure
Complete the following steps on your Solaris systems
before installing IBM Business Process Manager:
- Because WebSphere® Application
Server is
a prerequisite of IBM Business Process Manager, complete
the required preparation steps in the Preparing Solaris systems for installation topic
in the WebSphere Application
Server information
center.
- Increase the maximum number of open files.
The default setting is usually not enough. You can check your current
maximum number of open files by using ulimit -n.
The following example shows the maximum number of open files being
increased to 8800, which is large enough for most systems. The ulimit
requirement is dynamically calculated at installation time and might
need to be larger based on the options you select.
Before
installing, run the following command:
Alternatively, you can use the following steps to edit the
resource limits file:
- Open /etc/system
- Add the following line to the end of the file:
- Save and close the file.
- Log off from the operating system and log in again.
- Set the umask value to
077 using the following command:
The value 077 is the most restrictive value that
IBM Business Process Manager will
tolerate. You can optionally choose to set a less restrictive
umask value
for the following access levels:
- 037 for read-only access for a group of human administrators and
tools
- 027 for read and write access for a group of human administrators
and tools
- 007 for read, write, and execute access for a group of human administrators
and tools
- Complete the steps in Tuning Solaris systems.
- Ensure all servers involved are set to the same time. Use
the same network time protocol for all servers on all cluster nodes,
including application, support, and database clusters. A time mismatch
will cause erratic behavior, including duplicate system tasks.
