19.4 Prerequisites and Considerations for Installing iManager

19.4.1 Considerations for Installing iManager

Before installing iManager, review the following considerations:

  • If you previously installed the Identity Vault as a root user, you must install iManager as a root user.

  • If you plan to have more than 10 administrators regularly working in iManager at the same time, do not install iManager on the same server as other Identity Manager components.

  • If you plan to have only one administrator, you can install iManager on the same server as the Identity Manager engine.

  • To install iManager on a server running a supported Open Enterprise Server platform, you must use the OES version’s patch channel to upgrade to the latest iManager version.

  • If the iManager 2.7.7 Server setup program detects a previously installed version of iManager 2.7.x, you can stop the installation process or remove the existing iManager, JRE, and Tomcat installations.

  • Because iManager Workstation is a self-contained environment, you can install multiple versions on the same workstation, including older versions of Mobile iManager. However, you should not attempt to run them simultaneously. If you need to use different versions, run one version, close it, and then run the other version.

  • You cannot run iManager Workstation from a path that includes spaces. For example, C:\NetIQ\iManager Workstation\working.

  • You must have root access rights for Linux servers or Administrator access for Windows servers.

  • To create a Role-Based Services (RBS) collection in the eDirectory tree, you must have admin-equivalent rights.

  • To run the iManager RBS Configuration Wizard, you must have admin-equivalent rights.

  • To manage the same eDirectory tree with multiple versions of iManager, you must update your RBS Collection(s) to the latest iManager version.

19.4.2 Considerations for Installing iManager on a Linux Platform

Your Linux server must have specific packages already installed before you install iManager. In general, you can download the .rpm files from a website such as http://rpmfind.net/linux.

Red Hat Enterprise Linux

You must install the following packages. When you install iManager on 64-bit version of RHEL, ensure that the 32-bit versions of the RHEL libraries are also installed.

  • compat-libstdc++-33-version.el6.i686.rpm (RHEL 6 or 7 32-bit)

  • compat-libstdc++-33-version.el6.i686.rpm (RHEL 6 or 7 64-bit)

  • compat-libstdc++-33-version.el6.x86_64.rpm (RHEL 6 or 7 64-bit)

  • libstdc++-4.4.version.el6.i686.rpm (RHEL 6 or 7 64-bit)

  • libstdc++-4.4.version.el6.x86_64.rpm (RHEL 6 or 7 64-bit for GUI installation mode)

  • glibc-2.12-version.el6.i686 (RHEL 6 or 7 64-bit)

  • libXau-version.el6.i686.rpm (RHEL 6 or 7 64-bit)

  • libxcb-version.el6.i686.rpm (RHEL 6 or 7 64-bit))

  • libX11-version.el6.i686.rpm (RHEL 6 or 7 64-bit)

  • libXext-version.el6.i686.rpm (RHEL 6 or 7 64-bit)

  • libXi-version.el6.i686.rpm (RHEL 6 or 7 64-bit)

  • libXtst-version.el6.i686.rpm (RHEL 6 or 7 64-bit)

  • libstdc++-version.el6.i686.rpm (RHEL 6 or 7 64-bit)

  • libgcc-version.el6.i686.rpm (RHEL 6 or 7 64-bit)

  • libXrender-0.9.5-1.el6.i686.rpm (RHEL 6 or 7 64-bit)

SUSE Linux Enterprise Server (64-bit)

You must install the following packages.

  • libstdc++33‐32bit

To use PKI plug-in, you must also install the following RPMs on the iManager server:

  • SLES 11 64-bit: compat-32bit (compat-32bit-2009.1.19-2.1)

  • SLES 11 32-bit: compat (compat-2009.1.19-2.1)

SUSE Linux Enterprise Server (32-bit)

You must install the following packages.

  • libstdc++33

  • libstdc++43

To use PKI plug-in, you must also install the following RPMs on the iManager server:

  • SLES 11 64-bit: compat-32bit (compat-32bit-2009.1.19-2.1)

  • SLES 11 32-bit: compat (compat-2009.1.19-2.1)

19.4.3 Considerations for Installing iManager on a Windows Platform

If you are using Microsoft Internet Information Services (IIS) or Apache HTTP Server for Windows, you must manually integrate iManager with these web server infrastructures. By default, iManager uses Tomcat on Windows servers.

19.4.4 Considerations for Installing iManager Workstation on Linux Clients

Your Linux clients must have the following packages already installed before you install iManager Workstation:

  • GTK2

  • GLIBC 2.3

  • libstdc++33

    • SUSE Linux Enterprise Desktop (SLED) 11 32-bit

    • SLED 11 SP1 32-bit

    • openSUSE 11.0 32-bit

    • openSUSE 11.1 32-bit

    • openSUSE 11.2 32-bit

    • openSUSE 11.3 32-bit

    • openSUSE 12.1

  • libstdc++33-32 bit

    • SLED 11 64-bit

    • SLED 11 SP1 64-bit

    • openSUSE 11.0 64-bit

    • openSUSE 11.1 64-bit

    • openSUSE 11.2 64-bit

    • openSUSE 11.3 64-bit

  • libgtk-2_0-0-32bit

    • openSUSE 12.2 (64-bit)

    • openSUSE 12.3 (64-bit)

  • libXt6-32bit

    • openSUSE 12.2 (64-bit)

    • openSUSE 12.3 (64-bit)

  • libgthread-2_0-0-32bit

    • openSUSE 12.2 (64-bit)

    • openSUSE 12.3 (64-bit)

  • libXtst6-32bit

    • openSUSE 12.2 (64-bit)

    • openSUSE 12.3 (64-bit)

19.4.5 Considerations for Installing iManager Workstation on Windows Clients

Before installing iManager Workstation on your Windows clients, NetIQ recommends that you review the following considerations:

  • To enable Internet Explorer to use a proxy server for your LAN, you must specify Bypass Proxy Server for Local Addresses under Tools > Internet Options > Connections > LAN Settings.

  • To run a Novell Client earlier than version 4.91, the NetIQ Modular Authentication Service (NMAS) client must be installed on the workstation before you launch iManager Workstation.

  • If you run iManager Workstation from a path where any directory contains temp or tmp in the name, such as c:\programs\temp\imanager, iManager plug-ins do not install. Instead, run iManager Workstation from C:\imanager or a non-temporary directory.

  • The first time that you run iManager Workstation on a Windows workstation, use an account that is a member of the workstation's Administrators group.