Before you begin
The installation uses Installation Manager. You can
use the graphical interface or use a response file in silent mode.
Restriction: There are known issues with using Cygwin/X to run
Eclipse-based applications on remote Solaris machines. This affects
your use of the Profile Management Yool. With Cygwin/X on remote Solaris,
for example, the Profile Management Tool welcome panel appears but
no keyboard or mouse input is accepted. For details of existing Bugzilla
reports on these issues, see the information at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=97808.
If a different X server (such as Hummingbird Exceed
®) is
used, these problems do not occur.
About this task
Preparing the operating
system involves such changes as allocating disk space and installing
patches to the operating system. IBM tests WebSphere Application Server
products on each operating system platform. Such tests verify whether
an operating system change is required for WebSphere Application Server products to
run correctly. Without the required changes, WebSphere Application Server products do
not run correctly.
- Log on to the operating system.
You
can log on as root or as a nonroot installer.
Select a umask
that allows the owner to read/write to the files, and allows others
to access them according to the prevailing system policy. For root,
a umask of 022 is recommended. For nonroot users a umask of 002 or
022 can be used, depending on whether the users share the group. To
verify the umask setting, issue the following command:
umask
To set the umask
setting to 022, issue the following command:
umask 022
- Make sure that you select the Entire Group option
on the Select Solaris Software Group panel when you set up
your system.
- Optional: Download
and install the Mozilla
Firefox web browser.
If you do not have the Mozilla
web browser, download and install the browser from http://www.mozilla.org/products/firefox.
- Optional: Export the location
of the supported browser.
Export the location of the
supported browser using a command that identifies the actual location
of the browser.
If the Mozilla Firefox package is in the
/opt/bin/firefox directory,
for example, use the following command:
export BROWSER=/opt/bin/firefox
- Optional: Configure Hummingbird Exceed to disable
Automatic Font Substitution.
Font changes occur when
using the Hummingbird Exceed package and invoke the Profile Management
Tool. When you use the Hummingbird Exceed package to connect to a
machine running the Solaris operating system, and then invoke the
Profile Management Tool, some font sizes and styles display differently
than when doing the same operation from the native Solaris display.
The
font sizes and style changes are based on the font selections in the
bundled Java SE Runtime Environment 6 (JRE
6).
To prevent the various font changes, configure Hummingbird
Exceed to disable Automatic Font Substitution:
- From the Hummingbird Exceed user interface, click Xconfig > Font > Font
Database > Disable ( Automatic Font Substitution).
- Click OK.
- Restart the Hummingbird Exceed package.
- Stop all Java processes
related to WebSphere Application
Server on the machine where you are installing the product.
- Stop any web server process such as the IBM HTTP Server.
- Provide adequate disk space.
The
amount of
disk space required varies with the number of features or products
installed. If you are installing the product using Installation Manager,
the installation summary panel indicates the approximate amount of
disk space required based on the features and products you have selected.
Installing
all features and products requires approximately 2 GB of disk space.
This estimate includes the following products, components, and features:- Main application server product installation
- Profiles
- Sample applications
- IBM HTTP Server
- Web Server
Plug-ins
- Application Client for WebSphere Application Server
If you plan to migrate applications and the configuration
from a previous version, verify that the application objects have
enough disk space. As a rough guideline, plan for space equal to 110
percent of the size of the applications.
- Set kernel values to support Application Server.
Several Solaris kernel values are typically too small.
The
instructions in this step apply to the Solaris SPARC (32-bit and
64-bit) operating system only. For Solaris x64 processor-based systems,
see How to Get Started with IBM WebSphere Application Server
on Solaris 10 and Zones. The article was written for Solaris
10 on SPARC but the principles apply equally to x64.
Before
installing, review the machine configuration:
sysdef -i
The kernel values are set in
the
/etc/system file, as shown in the following
example.
set shmsys:shminfo_shmmax = 4294967295
set shmsys:shminfo_shmseg = 1024
set shmsys:shminfo_shmmni = 1024
set semsys:seminfo_semaem = 16384
set semsys:seminfo_semmni = 1024
set semsys:seminfo_semmap = 1026
set semsys:seminfo_semmns = 16384
set semsys:seminfo_semmsl = 100
set semsys:seminfo_semopm = 100
set semsys:seminfo_semmnu = 2048
set semsys:seminfo_semume = 256
set msgsys:msginfo_msgmap = 1026
set msgsys:msginfo_msgmax = 65535
set rlim_fd_cur=1024
You can change kernel values by editing the /etc/system file
then rebooting the operating system. For more information about setting
up the Solaris system, see the Sun Microsystems documentation. For
example, the Solaris Tunable Parameters Reference Manual.
- Verify that prerequisites and corequisites are at
the required
release levels.
Although Installation Manager checks
for prerequisite operating system patches, review the prerequisites
on the Supported hardware and software website if
you have not done so already. Refer to the documentation for non-IBM
prerequisite and corequisite products to learn how to migrate to their
supported versions.
Note: If your Solaris system does not have
sufficient available memory as specified on the supported hardware
and software website, you might experience a prerequisite error during
installation: "A supported operating system architecture was not detected".
If you proceed to the end of the installation, you might also see
the following insufficient disk space error:
java.io.IOException: Cannot run program "sh": error=12, Not enough space
at java.lang.ProcessBuilder.start(ProcessBuilder.java:459)
at java.lang.Runtime.exec(Runtime.java:593)
at java.lang.Runtime.exec(Runtime.java:466)
Free up additional memory on the machine and retry the
installation.
- Verify the system cp command
when using emacs or other freeware.
If you have emacs
or other freeware installed on your operating system, verify that
the system
cp command is used.
- Type the following command prompt before running the installation
program for the WebSphere Application
Server product.
which cp
- Remove the freeware directory from your PATH
if the resulting directory output includes freeware.
For example, assume that the output is similar to the following message: .../freeware/bin/cp.
If so, remove the directory from the PATH.
- Install the WebSphere Application
Server product.
- Add the freeware directory back to the PATH.
If you install with a cp command that
is part of a freeware package, the installation might appear to complete
successfully, but the Java 2
SDK that the product installs might have missing files in the app_server_root/java directory.
Missing
files can destroy required symbolic links. If you remove the freeware cp command
from the PATH, you can install the application server product successfully.
- Verify that the Java SDK on the installation image disk is functioning
correctly if you created your own disk.
For example,
you might have downloaded an installation image from Passport Advantage®, or you might
have copied an installation image onto a backup disk. In either case,
perform the following steps to verify that the disk contains a valid Java software development kit (SDK).
- Change directories to the /JDK/jre.pak/repository/package.java.jre/java/jre/bin directory
on the product disk. For example:
cd /JDK/jre.pak/repository/package.java.jre/java/jre/bin
- Verify the Java version.
Type the following command:
./java -version
The
command completes successfully with no errors when the SDK is intact.