5.2 Installing on Linux

  1. Open a terminal window.

  2. Log in as the root user.

  3. Access the install script.

    1. Make sure you have downloaded the software or that you have the CD available.

      For software download instructions, see the “Novell Access Manager Readme”

    2. Do one of the following:

      • If you are installing from CD or DVD, insert the disc into the drive, then navigate to the device. The location might be /media/cdrom, /media/cdrecorder, or /media/dvdrecorder, depending on your hardware.

      • If you downloaded the tar.gz file, unpack the file by using the following command:

        tar -xzvf <filename>

    3. Change to the novell-access-manager-3.1.2-xxx directory.

  4. At the command prompt, run the following install script:

    ./install.sh

    NOTE: When you install Identity Server on a SLES 11 64-bit operating system, the following error message appears: 

    This version of Novell Access Manager supports SSL VPN installation only on Novell SUSE Linux Enterprise Server version 11 64-bit. If you are installing any other component, you are recommended to stop the installation now". Would you like to continue (y/n)? [n]:

    Ignore this error message and continue with the installation by specifying ‘y’.

  5. When you are prompted to install a product, type 2, Install Novell Identity Server, then press the Enter key.

    This selection is also used for installing additional Identity Servers for clustering behind an L4 switch. You need to run this install for each Identity Server you add to the cluster.

  6. If you are prompted, decide whether or not you want to continue the installation without a static IP address. In most production environments, you must establish a static IP address for your Identity Server to reliably connect with other Access Manager components. If the IP address changes, the Identity Server can no longer communicate with the Administration Console.

  7. Review and accept the License Agreement.

  8. Specify the IP address of the Administration Console, if you are not installing this Identity Server on the same machine where you installed the Administration Console.

  9. Specify the name of the administrator for the Administration Console.

    This is the name you recorded when you installed the Administration Console.

  10. Specify the password of the administrator.

    This is the password you recorded when you installed the Administration Console.

  11. Confirm the password, then wait as the system installs the components. (This takes several minutes.)

    If the installation program rejects the credentials and IP address, ensure that the correct ports are open on both the Administration Console and the Identity Server, as described in Section 5.1, Prerequisites.

    The following components are installed:

    • Novell Access Manager Server Communications: Enables network communications, including identifying devices, finding services, moving data packets, and maintaining data integrity.

    • Novell Identity Server: Provides authentication and identity services for the other Access Manager components and third-party service providers.

    • Novell Identity Server Configuration: Allows the Identity Server to be securely configured by the Administration Console.

      If the installation process terminates at this step, the probable cause is a failure to communicate with the Administration Console. Ensure that you entered the correct IP address.

    • Novell Access Manager Server Communications Configuration: Enables the Identity Server to auto-import itself into the Administration Console.

    This completes the Novell Identity Server installation. The install logs are located in /tmp/novell_access_manager/inst_lag.log. These logs are all dated and time-stamped.

  12. (Optional) To verify that the Identity Server installation was successful, log in to the Administration Console (see Section 4.3, Logging In to the Administration Console).

    After you log in to the Administration Console, click Devices > Identity Servers. The system displays the installed server, as shown in the following example:

    At this point the Identity Server is in an unconfigured state and is halted. It remains in this state and cannot function until you create an Identity Server configuration, which defines how an Identity Server or Identity Server cluster operates.

  13. Continue with one of the following: