1.4 Prerequisites and Considerations for Installing iManager

1.4.1 Considerations for Installing iManager

Before installing iManager, review the following considerations:

  • If the iManager server setup program detects a previously installed version of iManager which is prior to 2.7.7.x, installation process stops automatically and you need to manually 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.

1.4.2 Considerations for Installing iManager Server on a Linux Server

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

Red Hat Enterprise Linux (RHEL)

  • compat‐libstdc++‐33 (RHEL 5)

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

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

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

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

  • glibc-2.12-*.el6.i686 (RHEL 7, RHEL 6 64-bit)

  • libXau-*.el6.i686.rpm (RHEL 7, RHEL 6 64-bit)

  • libxcb-*.el6.i686.rpm (RHEL 7, RHEL 6 64-bit)

  • libX11-*.el6.i686.rpm (RHEL 7, RHEL 6 64-bit)

  • libXext-*.el6.i686.rpm (RHEL 7, RHEL 6 64-bit)

  • libXi-*.el6.i686.rpm (RHEL 7, RHEL 6 64-bit)

  • libXtst-*.el6.i686.rpm (RHEL 7, RHEL 6 64-bit)

  • libstdc++-*.el6.i686.rpm (RHEL 7, RHEL 6 64-bit)

  • libgcc-*.el6.i686.rpm (RHEL 7, RHEL 6 64-bit)

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

SUSE Linux Enterprise Server (SLES) 64-bit

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

  • SLES 15 64-bit: libstdc++6-32bit and net-tools-deprecated package

    NOTE:Ensure to install net-tools deprecated package before installing iManager on SLES 15 otherwise the installation will fail.

1.4.3 Considerations for Installing iManager Server 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.

1.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 12 (32-bit)

    • SLED 11 SP1 (32-bit)

    • openSUSE 11.x (32-bit)

    • openSUSE 12.x (32-bit)

    • openSUSE 13.2 (32-bit)

  • NICI, OpenSSL RPMs and novell-libstdc

1.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.

  • 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.