Before Installing

Before beginning the tasks in the chapter, you should have developed an installation sequence and ensured that any general installation requirements and prerequisites are met.

• Verifying Prerequisites and Requirements

• (Optional) Setting Your Local Display for a Remote Host

• Getting the Software

Verifying Prerequisites and Requirements

Refer to Verifying General Installation Prerequisites for specific information on prerequisites for this release of Communications Suite.

You can find system requirements for Communications Suite listed in the Sun Java Communications Suite 5 Release Notes. For Java ES, see Platform Requirements and Issues in Sun Java Enterprise System 5 Release Notes for UNIX.

You must use Access Manager Legacy (6.x) installation type if you are installing Access Manager with Messaging Server, Calendar Server, Delegated Administrator, or Instant Messaging. Access Manager Realm (7.x) installation type can only be used if you are not installing any of these product components.

• For Configure Now: On the Access Manager: Administration (1 of 7) page, select Legacy (version 6.x style). On the Access Manager: Web Container for running Access Manager (4 of 7) page. set the Console Deployment URI to amconsole (the default value).

• For Configure Later: As root, run the amconfig script to configure Access Manager after installation. To select the Legacy (6.x) installation type, set the following parameters in your configuration script input file, amsamplesilent:

  • AM_REALM=disabled

  • CONSOLE_DEPLOY_URI=/amconsole

(Optional) Setting Your Local Display for a Remote Host

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

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 -

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.

Getting the Software

• For Download. Navigate to the directory where you downloaded the Communications Suite installation bundle and expand the bundle. For example:

  unzip compressed-file.zip

  You will see a Copyright file, a README directory and the operating system directory, such as Solaris_sparc. In the operating system directory, you will see the Product directory, the release_info file, and the installer script.

• For CD. Navigate to a directory that is not on the CD so that you can switch CDs during the installation session. For example:

  cd /tmp

  You will run the installer command using the fully qualified path to the installer. For example:

  mountpoint/os_arch/installer

  In this example, mountpoint is where you mounted the CD and os_arch matches your platform, such as Solaris_sparc.

• For DVD. Navigate to the DVD directory whose name matches your platform.