|
| |
| Sun Java Enterprise System 2005Q1 Installation Guide | |
Chapter 6
Preparing for InstallationThis chapter provides information that will help you prepare for your installation of Sun Java™ Enterprise System (Java ES) software.
This chapter contains the following sections:
Installation PrerequisitesThe following table lists the tasks that you should perform before beginning any type of installation. The left column lists the order in which you should perform the tasks, the middle column describes the action, and the right column contains the location of instructions and other useful information. Not all tasks are required for all installations.
Table 6-1 Preinstallation Checklist
Order
Task
Instructions and Helpful Information
1
Read the Java Enterprise System Release Notes.
Before performing any of the procedures described in the Installation Guide, you should read the Java Enterprise System Release Notes (http://docs.sun.com/doc/819-0057). They contain installation issues that might pertain to your scenario.
2
Plan your installation sequence for the Java ES components.
Chapter 2, "Developing Your Installation Sequence"
If installing Sun Cluster software (Solaris 8 and 9 only), see Sun Cluster Software Example.
3
Upgrade any existing components that are incompatible with Java ES 2005Q1.
Are Incompatible Components Installed?
prodreg, pkginfo, or rpm command
For usage information, refer to their man pages.Java Enterprise System Upgrade and Migration Guide, http://docs.sun.com/doc/819-0062
4
Verify that system requirements are met.
Java Enterprise System Release Notes, http://docs.sun.com/doc/819-0057
5
For a Configure Now installation, gather configuration information for components.
Chapter 4, "Configuration Information"
6
Make a copy of the product registry file. The backup copy is helpful in recovering from a failed installation.
On Solaris: /var/sadm/install/productregistry
On Linux: /var/opt/sun/install/productregistry7
For non-root, create the necessary system accounts.
To run as a non-root user for Directory Server, Directory Proxy Server, or Administration Server, you must create system accounts before configuring.
8
If installing components that depend on servers or services that are already installed, ensure that the existing servers and services are running and accessible.
For example, If you are installing a Portal Server Secure Remote Access subcomponent, the Secure Remote Access core must be running and accessible.
9
If installing Directory Server, verify that Perl is installed.
Solaris: Perl packages (SUNWpl5*) can be found on the Solaris media.
Linux: /usr/bin/perl must be present before installation.
If Perl is not present, use pkgadd or rmp -i to add the packages.
10
If installing Access Manager or Messaging Server, verify that the domain name of the host on which Access Manager will be installed is set.
To set the domain name, do one of the following:
# domainname domain_name
11
If installing Calendar Server or Messaging Server, verify that the second column in the /etc/hosts file contains the fully-qualified domain name (FQDN) rather than a simple host name.
For example:
192.18.99.999 mycomputer.company.com mycompany loghost
12
When installing the Load Balancing Plugin with Apache Web Server, install and configure Apache Web Server before beginning JES installation. (On Linux only, you must first install the Application Server, then install Apache Web Server, and finally install the Load Balancing Plugin.)
For more information, see Configuring Web Servers for HTTP Load Balancing in the Sun Java System Application Server Enterprise Edition 8.1 High Availability Administration Guide (http://docs.sun.com/doc/819-0216).
If installing Access Manager for deployment on a third-party web container, you must choose the Configure Later option and run a configuration script.
For more information, see Access Manager Sample Configuration Script Input File in the Sun Java System Access Manager Administration Guide (http://docs.sun.com/doc/817-7647).
13
If this is a reinstallation, verify that the Web Server installation directory does not exist. If it does, remove or rename the directory.
Default installation directory for Web Server:
On Solaris/opt/SUNWwbsvr
On Linux: /opt/sun/webserver14
If upgrading J2SE software, verify that you have stopped other products that depend on the J2SE component you are upgrading.
Refer to the Java Enterprise System Upgrade and Migration Guide (http://docs.sun.com/doc/819-0062).
15
If Directory Proxy Server will use a preinstalled Configuration Directory Server, ensure that the Configuration Directory Server is running before installing Directory Proxy Server.
If you are installing Directory Proxy Server and the Configuration Directory Server at the same time, you can skip this task.
Getting the Java ES SoftwareYou can get the Java ES software in the following ways:
You can get a media kit containing CDs or a DVD at http://wwws.sun.com/software/javaenterprisesystem/index.html or by contacting your Sun™ sales representative. Each CD contains the installation files for a single operating system, the Java ES installer program, and all the component packages. The DVD contains the installation files for the Solaris operating systems, the Java ES installer program, and all the component packages.
You can download Java ES software in several formats from the Sun Download Center at http://www.sun.com/download. These formats are available:
If you ordered a Sun hardware system with preloaded or preinstalled software, Java ES software might already be loaded on your system. If the following directory exists on your system, Java ES software is preinstalled:
/var/spool/stage/JES_05Q1_architecture/
where architecture is the system’s hardware architecture; for example, SPARC or x86.
Depending on the operations procedures at your company, the Java ES installation files might be available on your internal network. Contact your system operations or administration staff to find out if this is the case.
If you are responsible for making the Java ES installation files available, see Distribution Bundles.
Distribution BundlesThe following tables list the distribution bundles for the Java ES software. (An ISO distribution includes the designation iso in the bundle name. For example:
java_es_05Q1-ga-solaris-sparc-1-iso.zip
Making an Installation ImageThe Java ES distribution is designed so that you can easily put the installation files in a shared location. The benefit of this is that the installation files can then be run from this shared location as often as needed.
To Create an Image on Your Network
This section provides instructions for making an installation image available on your site network.
- Log in as root or become superuser.
- Create a shared directory on your network. For example:
mkdir java_ent_sys_2005Q1
- Access your installation files from the web site, the CD, or the DVD, then prepare the installation files to be shared.
For web download. After downloading the Java ES distribution bundle (CD image or compressed archive), extract the files in the shared location.
- The CD image is normally burned to a CD, but it can be mounted if needed. Example of mounting:
unzip java_es_05Q1-ga-solaris-sparc-iso.zip
lofiadm -a pathname/java_es_05Q1-ga-solaris-sparc.iso /dev/lofi/1
mkdir mountpoint
mount -F hsfs /dev/lofi/1 mountpoint
ls mountpoint
Copyright Docs README Solaris_sparc
cd mountpoint/Solaris_sparc
ls
Product installer- Copy the compressed archive to the shared location and unpack the files. For example:
unzip java_es_05Q1-ga-solaris-sparc.zip
For the CD or DVD. Copy the installation files to the shared location. For example:
mkdir shared-loc/java_ent_sys_2005Q1
cd /mnt/cdrom
find jes_05Q1_sparc | cpio -pdmu shared-loc/java_ent_sys_2005Q1