About this task
The installation uses an InstallShield MultiPlatform (ISMP)
wizard. You can also install the product silently. Silent mode is
invoked at a command line with a parameter that identifies a response
file, which you edit before installing.
If
you encounter a problem such as needing more temporary space or missing
prerequisite packages on your operating system, cancel the installation,
make the required changes, and restart the installation.
Restriction: The Profile Management Tool is an Eclipse-based
application and 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 Tool and the Installation Factory.
With Cygwin/X on remote AIX®,
for example, a splash screen for the Profile Management Tool appears
but the Profile Management Tool never actually comes up. For details
of existing Bugzilla reports on these issues, see the information
at
Bugzilla – Bug 36806. If a different X server
(such as Hummingbird Exceed) is used, these problems do not occur.
Use
the following procedure to prepare the operating system for installation
of WebSphere ESB.
- Log on to the system. Your user ID does not
need to have root privileges.
- Select a umask that allows the owner to read and write
to the files, and allows others to access them according to the prevailing
system policy. For root users, a umask of 022 is recommended.
For non-root 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
- Select the Entire Group option on the Select Solaris
Software Group panel.
- Optional: Install the Mozilla browser if it
is not already installed. The Mozilla browser supports the launchpad
console. Download and install the Mozilla browser from Mozilla.
- Optional: Export the location of the supported
browser.
Export the location of the supported browser
using a command that identifies the location of the browser.
For
example, if the Mozilla package is in the
/usr/bin/mozilla directory,
use the following commands:
BROWSER=/usr/bin/mozilla
export BROWSER
- Optional: Configure Exceed to disable Automatic
Font Substitution. When you use the Hummingbird Exceed
package to connect to a workstation running the Solaris operating
system, and then invoke the Profile Management Tool, some font sizes
and styles display differently than they would when performing the
same operation from the native Solaris display. The font sizes and
style changes are based on the font selections in the bundled Java™ Runtime Environment (JRE).
To prevent the various font changes, configure Hummingbird Exceed
to disable Automatic Font Substitution:
- From the Hummingbird Exceed user interface, select Xconfig
> Font > Font Database > Disable (Automatic Font Substitution).
- Select OK.
- Restart the Hummingbird Exceed package.
- Stop all Java processes
related to WebSphere Application
Server, WebSphere Application
Server Network Deployment, WebSphere ESB, on the workstation on which you are installing the
product.
- Stop any Web server process such as the IBM® HTTP Server.
- Provide adequate disk space. For the space required to
install WebSphere ESB and
related products, see WebSphere ESB detailed
system requirements at http://www.ibm.com/support/docview.wss?uid=swg27006912 and select the link to your
version of the product.
- Set kernel values to support WebSphere ESB.
Several Solaris kernel values are typically too small for
the product. See Setting kernel values on Solaris systems for instructions on how to set kernel values.
- Verify that prerequisites and corequisites are at the required
release levels.
Although the installation wizard checks
for prerequisite operating system patches, review the prerequisite
supported hardware and software for WebSphere ESB if
you have not already done so. To access this information, see WebSphere ESB detailed
system requirements at http://www.ibm.com/support/docview.wss?uid=swg27006912 and select the link to your version of WebSphere ESB.
Refer
to the documentation for non-IBM prerequisite and corequisite products
to learn how to migrate to their supported versions.
- Verify that the system cp command is used, rather
than the cp command provided by emacs or other freeware.
If you install the product using a cp command that
is part of a freeware package, rather than with the system cp command,
the installation might appear to complete successfully, but the Java 2 SDK that the product installs
might have missing files in the install_root/java directory
(where install_root represents the installation
directory of WebSphere ESB).
Missing
files can destroy required symbolic links. You must remove the freeware cp command
from the PATH in order to install the WebSphere ESB product
successfully.
If you have emacs or other freeware installed
on your operating system, perform the following steps to identify
which cp command is being used by the system, and to deactivate
the freeware cp command if it is being used:
- Type which cp at the command prompt before
running the installation program for the WebSphere ESB product.
- If the resulting directory output includes freeware,
remove the freeware directory from your PATH. For
example, if the output is similar to .../freeware/bin/cp,
remove the directory from the PATH.
- Install WebSphere ESB.
- Add the freeware directory back to
the PATH.
- Verify that the Java 2
SDK on your copies of the product discs is functioning correctly.
If you created your own product DVD by copying the product
DVD, or if you created your own DVD from the electronic download image,
perform the following steps to verify that the Java 2 SDK is working correctly:
- On your created product disc, navigate to the /JDK/jre.pak/repository/package.java.jre/java/jre/bin directory. To do this, issue the following command:
cd /JDK/jre.pak/repository/package.java.jre/java/jre/bin
- Verify the Java 2
SDK version. To do this, issue the following command:
./java -version
The command
completes successfully with no errors when the Java 2 SDK is intact.
- Repeat this procedure on all other created product discs.
What to do next
After preparing the operating system, you can install WebSphere ESB. See Installing the software for
descriptions of the various installation alternatives available.