Before you can install IBM® Business Monitor, you
must prepare your Solaris operating system.
About this task
The HotSpot Java JVM was developed by Sun
Microsystems for the Solaris operating system. The
Java heap structure and management for the HotSpot JVM is different
from those of other JVMs. In your environment, you might need to tune
the heap management of the JVM to avoid any java.lang.OutOfMemoryError:
PermGen errors during profile creation or server runtime.
You might need to update the value for the MaxPermSize JVM
parameter.
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 Monitor:
- Because WebSphere® Application
Server is
a prerequisite of IBM Business Monitor, 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 ulimit requirement is dynamically calculated at installation time
and might need to be larger based on the options that you select.
The following example shows the maximum number of open
files being increased to 20000, which is the minimum value required
for creating IBM Business Monitor profiles.
Before installing, run the following command:
Alternatively, you can use the following steps
to edit the resource limits file:
- Open the /etc/system file.
- Add the following line to the end of the file:
where number is the maximum upper limit
on file descriptors, which a single process can have open. This value
can be equal to, or greater than, the ulimit value.
- 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 Monitor 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.
What to do next
Before creating or augmenting
IBM Business Monitor profiles
on your Solaris system, change the
MaxPermSize JVM
parameter, following the steps in
Eliminating profile creation OutOfMemoryErrors on Solaris