C H A P T E R 5 |
Installing Java Studio Enterprise (Solaris OS) |
This chapter describes how to install your Java Studio Enterprise software in the Solaris OS environment from the product physical media or from files downloaded from the web. Before installing, you may need to install the necessary Solaris OS patches.
The quickest way to determine if you need to install any patches to your Solaris OS is to start the Java Studio Enterprise installer and run it to the Systems Requirements Check step. At the conclusion of this step, the installer displays information regarding the Solaris patches that you need. If the installer does not indicate the need to install patches, then your system has the necessary patches installed. If you are unsure about installing Solaris patches in your Solaris environment, contact your system administrator. You need to have superuser privileges to install patches for the Solaris OS.
To review the list of required patches, see Appendix A.
Note - If you encounter errors at any point during the installation, refer to Chapter 15 for troubleshooting tips. |
1. Verify that you have properly prepared your machine for installation. See Chapter 2 for details.
a. Log in to your system as a superuser using your root password.
To use the CD-ROM (or DVD) and enable the autorun feature to work correctly, log in to your machine as root. Do not use the su command in a terminal window as this does not enable you to install correctly when the autorun feature launches the install process.
If the installer does not start or you do not see the File Manager window, follow these steps:
ii. Change to the CD-ROM directory and start the installation.
The Welcome page appears. Go to Step 3.
a. Download and unzip the Java Studio Enterprise software into your java-studio-download-dir.
b. Set the DISPLAY environment variable to display to your machine name.
c. Enable access to the X server.
e. Change to the subdirectory containing the installer.
The Welcome page displays. Proceed to Step 3.
3. From the Welcome page, click Next and follow the instructions on the installer wizard pages.
The installer asks a series of questions, installs the product you selected. When installation is complete, the Installation Complete page appears. If you have questions about the installer pages, refer to the following sections for more information:
Note - Create non-root server instances of Sun Java System Application Server 7 Standard Edition, Update 1 and Sun Java System Web Server 6.1, Service Pack 1 for use by a standard user account when prompted on this page titled "Enable product usage by a non-root user (by creating admin domain)". See Product Usage by Non-root User for details. |
4. Review the Installation Complete page.
a. Click on the View Summary button to view the installation summary information.
A new window opens and displays the Installation Summary Report. You see two buttons at the top: Install Summary and Configuration Data.
b. Click on the Configuration Data button to view the configuration data for the component products that you installed.
c. Close the Installation Summary Report window.
d. To view the installer logging messages, click View Log on the Installation Complete page.
A window opens and displays the Installation Log.
The log files can be found at /var/sadm/install/logs.
The log file names are of the following format:
5. Click Close to exit the installation wizard.
6. If you enabled client access, disable client access.
7. Exit from superuser privileges.
8. When installation is complete, proceed to validate the installation using the appropriate chapters:
Note - If you plan to use Sun Java System Application Server, read Chapter 9 before attempting to deploy your applications. |
On Solaris 9 OS update 5, the Message Queue packages are installed as part of the OS installation, therefore, since the installer detects that this component product is installed, the Installation Type page is not displayed. Use the Product Selection page to select the component products to install when installing on Solaris 9 OS update 5. For more details, see Installation Type Page.
Enter your installation directory on this page. The default installation directory is /opt/SUNWjstudio. Follow these guidelines if you specify a non-default installation directory:
The installer displays information about your system readiness on this page. If your machine does not meet requirements, the installer displays information describing the problem. Click on View Report for the details. The report is saved at /var/sadm/install/logs/SystemCheck_Report.timestamp.
The Administrator User ID and Administrator Password that you enter on this page are used to configure the various Java Studio Enterprise server products that you are installing. Use this ID and password to access the server administrative interfaces after installation. Write down the password that you choose. The password can not be retrieved after installation.
You can review the configuration data after installation in the following ways:
Use this installer page to enable usage of Application Server and Web Server from the IDE for a non-root user account. Usage of Application Server and Web Server as non-root is only for controlling domain and instances created for the non-root user account. It does not change how the software packages are installed. For example, you must still have root privileges to use the application server asadmin utility and to start Web Server admin server.
By default, the installer creates and configures an admin domain and an Application Server instance that is fully integrated for use within the Java Studio Enterprise IDE. The Web Server instance is also configured and integrated for use from within the IDE. These default instances are owned by the root user installing the software. If you installed Identity Server or Portal Server, these products are configured to run in the default root-owned instance of Web Server.
Entering information about the IDE user's standard account on this installer page, enables the installer to create instances of Application Server and Web Server that are owned by the standard user.
If you are unfamiliar with the Application Server concept of an admin domain, see Chapter 9 for more information. If you do not create the non-root server instances during installation, you can create them manually post-installation. See Chapter 9 and Chapter 10 for more information.
|
1. When prompted, verify that the appropriate check box is checked.
2. Enter the user ID and user group for the standard user that will be using the software.
This must be an existing account.
3. Click Next and continue normal installation.
When you select this option and provide the standard user account information, the installer does the following:
1. Creates a default Application Server instance and admin domain belonging to the non-root user.
The Application Server and admin domain created during installation belong to the non-root user account that you specify and can be started, stopped and used by that user. Further, when that user starts and uses the IDE, the Server Registry shows this default server instance and all actions from within the IDE manipulate this non-root user instance. See Chapter 9 for more information.
2. Creates two instances of Web Server: one belongs to root and one belongs to the non-root user account specified during installation.
The Web Server instance belonging to root is configured as the web container for Identity Server and Portal Server and can only be started, stopped and used by a user with root privileges. The root instance name is of the format:
The second instance belongs to the non-root (standard) user account and is fully integrated with the IDE. This non-root instance of Web Server appears in the IDE Server Registry and can be used for development purposes. See Chapter 10 for more information. The non-root instance name is https-jstudio.
Silent installation is useful for installing Java Studio Enterprise on multiple hosts that share similar configurations. Silent installation requires that you run the installer once to capture input values in a state file. The state file contains your responses as a list of parameters, each representing a single prompt or field. You can then run the installer on many hosts, using the state file as input after editing certain host-specific values. This process propagates one configuration across multiple hosts in your enterprise. See Chapter 7 for details.
1. You are not able to eject the product physical media after running the installer manually.
Reason: The CD-ROM is not ejecting because the system is detecting that the CD is being used.
Solution: After running the installer manually, change out of the CD-ROM directory before trying to eject the CD-ROM from the drive.
2. You specified a non-default installation directory, but the software was installed in /opt/SUNWjstudio, the default directory.
Reason: The installation directory you specified may be on a network- mounted filesystem. Installation to a directory that is not on the local machine is not supported in this version of the software.
Solution: Uninstall and reinstall using a directory on your local machine.
3. Trying to install the software from CD-ROM, the installer won't start even after trying all suggestions in section Using the GUI Installer, Step 2
Reason: The volume management system may be appending characters such as #1 to the volume label. If you see such characters at the end of the volume label, try the solution below. For example, the volume label for the CD-ROM for the Solaris Sparc OS is JSE_04Q1_SPARC, if you see JSE_04Q1_SPARC#1, try this solution.
Solution: Follow these steps to stop and restart the volume management process (vold) on your system, and run the installer again.
a. Ensure that CD-ROMs or floppy disks are not being used.
If you are not sure whether you have found all users of the media, run the fuser command.
b. Verify that you are superuser.
Copyright © 2004, Sun Microsystems, Inc. All rights reserved.