Using the Installer to Survey Installed Software

You can use Solaris commands such as prodreg and pkginfo or the Linux rpm command to examine installed software. You can also use the installer itself to examine package-based software installations as described in the procedures in this section.

Do not rely only on the Java ES installer for information about installed software. You must also perform an independent survey of the host to determine what software is currently installed.

To Provide Access to Your Local Display for the Graphical Installer

Steps

1. Set your DISPLAY environment variable.

   If you are logging in to a remote host, make sure your DISPLAY environment variable is properly set to the local display. If the DISPLAY variable is not set properly, the installer runs in text-based mode.

   • Example for C Shell (host name myhost):

     setenv DISPLAY myhost:0.0

   • Example for Korn Shell (host name myhost):

     DISPLAY=myhost:0.0

2. Grant display authorization.

   You might need to grant display authorization to run the installer on your local display. For example, you can use the following command to grant display authority from myhost to the root user on serverhost:

   myhost\> xauth extract - myhost:0.0|rsh -l root serverhost xauth merge -

   ---

   Note –

   For full instructions on granting such authorization safely, refer to the “Manipulating Access to the Server” chapter in the Solaris X Window System Developer's Guide.

   ---

To Use the Installer for Identifying Upgrade Issues

Steps

1. On each host, start the installer using the -no option to indicate that this is not an active installation:

   For the graphical installer:

   ./installer -no

   For the text-based installer:

   ./installer -nodisplay -no

2. Proceed to component selection.

3. Select the components you are planning to install on this host.

   The Status column indicates products that are required for the components you have selected.

4. If an incompatible version of a selectable component is detected by the installer, you are prompted to upgrade or remove the incompatible version.

   After resolving the problem, you can refresh the selection list, make your selection, and then ask the installer to proceed.

5. If an incompatible version of a shared component is detected by the installer, the Shared Component Upgrades Required list is displayed.

   For each shared component listed, review the Installed Version against the Required Version to determine if any upgrading will need to be done. You must determine whether the newer Java ES versions of shared components are compatible with other installed applications on the host.

6. Exit the installer and do any upgrading necessary.

   • For selectable components, refer to the Sun Java Enterprise System 2005Q4 Upgrade Guide.

   • For shared components, most upgrading can be done during installation.

7. Repeat the procedure for each target host.

   ---

   Note –

   The installer detects the Directory Server version that is distributed with the Solaris OS and warns you that the Directory Server script belonging to the Solaris distribution will be renamed by the installer. No action is required.

   ---