Novell iManager 2.6 can be installed on the platforms listed below. In general, you should apply the latest Service Packs for your platform and meet the prerequisites listed in “Prerequisites” on page 10, before installing iManager.
Upgrades from iManager 2.0. x and 2.5 are supported by the installation program. When you run the iManager 2.6 installation program on a server that is running 2.0. x or 2.5, the existing directory structures are backed up to the TOMCAT_HOME directory. This assures the preservation of any custom content previously created.
To prepare for the installation, review the following checklist of prerequisites.
In addition to the general prerequisites listed in Section 1.2, Prerequisites, the following prerequisites also apply to iManager on Linux:
Required Linux Packages: If any of the following packages are not installed, you must obtain them from the vendor of your Linux distribution and install them before installing iManager. They should be on your installation CDs.
compat (SUSE)
compat-libstdc++-33 (Red Hat AS 4.0)
compat-libstdc++ 7.3 (Red Hat AS 3.0)
Previous Versions of iManager: If you have installed iManager 1.5. x on the server, you must uninstall this version before proceeding to install iManager 2.6. If you have installed iManager 2. x, you do not need to uninstall it. The iManager 2.6 installation can overwrite the files. The uninstall process does not remove custom-created content. For more information, see Section 4.0, Uninstalling iManager 2.6.
Processor: Pentium* III 600MHz or higher processor
Disk Space: 200 MB hard-disk space for a local installation
Memory: 512 MB RAM (1024 MB recommended)
Port Setup: Be aware of possible port conflicts. Tomcat is installed with the iManager installation program, which determines whether the default ports are in use. If they are in use, the install prompts you for different ports for Tomcat to run on. By default,Tomcat uses ports 8080, 8443, and 9009.
IMPORTANT:On Linux, iManager is supported only with the version of Tomcat that is installed with iManager. Apache is not installed.
iManager installs the following products during installation:
Tomcat 4.1.30
Sun* J2SDK 1.4.2.05
Novell International Cryptographic Infrastructure (NICI) 2.6.8
At the Novell download site, search for iManager products, select iManager 2.6, then download iMan_26_linux.tgz to a directory on your server.
Use the following command to extract to the iManager folder:
tar -zxvf iMan_26_linux.tgz
Open a shell and change to the extracted_directory /iManager/installs/linux directory.
This path is relative to the directory where you copied or extracted the iManager files.
Enter one of the following commands while logged in as root or root-equivalent.
For a console install, enter the following command:
./iManagerInstallLinux.bin
For a GUI install, enter the following command:
./iManagerInstallLinux.bin -i gui
After a successful install, the installer generates a configuration file ( /var/log/installer.properties) with values based upon the questions asked during the install. This file can then be modified and used for a silent install. See Section 1.6, Silent Installation of iManager.
On the opening iManager splash screen, select a language, then click .
Accept the license agreement and click .
To download and install plug-ins, click , then select the plug-ins to install.
For a console install, enter a comma-separated list of the plug-in numbers to download.
For a GUI install, select the check boxes. Default selections are already made.
If desired, you can specify an alternative URL. For more information, see Section 1.4, Downloading and Installing Plug-ins During Installation. When using an alternative URL for downloading plug-ins, it is solely your responsibility to verify the URL contents, and verify that the plug-in is appropriate for your use.
If the message No plug-ins found or server not available appears in the plug-in download area, either or both of the following conditions exist: There are no updated plug-ins available on the Novell download site, or connecting to the Novell Descriptor File was not successful. Verify your Internet connection.
To install plug-ins from a local directory, click and specify the directory path that contains the plug-in ( .npm) files.
The default path is / extracted location/iManager/installs/plug-ins , but you can specify any valid mount point here.
Click to configure iManager with an existing Apache Web server. Click to run iManager only through Tomcat.
The iManager 2.6 install on Linux no longer installs the Apache Web server. However, if you are upgrading from a previous version of iManager, you can use the Web server installed previously.
If you select , iManager 2.6 is configured to use a previously installed Apache Web server, if one exists on your server. Type the directory path that contains the httpd.conf file for the Apache HTTP Server. This server must be configured for SSL communication before iManager can configure to it. If SSL communication is not configured on the Apache server, you can continue the install to configure iManager to run only through Apache Tomcat only, or you can stop the installation.
Specify the ports on which you want Tomcat to run.
The defaults are 8080 for HTTP and 8443 for HTTPS.
If you are configuring without an Apache HTTP server, you must run iManager 2.6 via the Tomcat ports. For example, https:// server_IP:8443/iManager.html.
Type the authorized user's full context and the tree he or she will manage, then click .
This information is not used to authenticate to eDirectory during installation and the information is not validated in any way. Make sure you use the syntax required by the iManager login page (see Accessing iManager.)
Providing an Authorized User at this time during the install is optional, but leaving these fields blank causes iManager to allow all users the ability to install plug-ins and make changes to iManager server settings (not recommended long-term.) Specify an authorized user post-install from the
>
>
>
page in iManager. For more information, see
Authorized Users
in the
iManager 2.6 Administration Guide.
Read the Preinstallation summary page, then click . Information on this page includes the following:
Plug-ins to be copied rom the local directory specified during the install.
Existing plug-ins that are currently installed with a previous version of iManager, for which there are no newer versions available on the Novell download site.
Plug-ins not currently installed with a previous verions of iManager, for which there are newer versions available on the Novell download site.
During installation, iManager files are installed, plug-ins are downloaded, and configuration changes occur. Installation can take several minutes.
After the installation completes, wait several seconds for the Getting Started page to appear. To access iManager, see Section 3.0, Accessing iManager.
If you have installed a previous version of iManager and created RBS or custom content, you need to update the modules. See Section 2.0, Updating Role-Based Services.
WARNING:When re-installing iManager on Linux, make sure to go through the uninstall routine (see Uninstalling iManager 2.6) before re-running the install routine. Running the install without first uninstalling the previous installation can cause the Tomcat configuration to become corrupt and be unable to start.
To prepare for the installation, review the following checklist of prerequisites.
In addition to the general prerequisites listed in Section 1.2, Prerequisites, the following prerequisites also apply to iManager on NetWare 6.5:
Previous versions of iManager: If you installed a previous version of iManager, you do not need to uninstall it. The iManager installation can overwrite the files.The uninstall process does not remove custom-created content.
Processor: Pentium III 600 MHz or higher processor
Disk Space: 200 MB hard disk space for a local installation
Memory: 512 MB RAM required (1 GB recommended)
NOTE:The following Novell software products should not be installed on a server where you will be installing iManager:
Novell Virtual Office 1.3 or prior
exteNd Director™ 4.1.1 or prior
IMPORTANT:To install plug-ins from a local directory during the installation routine, copy the plug-in files ( .npm) to the extracted_install_directory\products\imanager\packages directory prior to running the iManager install on NetWare. Only one directory level is searched for .npm files. The installation program does not install plug-ins in subdirectories.
At the Novell download site, search for iManager products, select iManager 2.6, then download and extract iMan_26_NW65_Standalone.zip to the SYS volume.
In the NetWare 6.5 GUI, click the button, then click > .
Browse to the extracted location, select the product.ni file, then click .
Accept the license agreement and click .
Select the plug-ins to download and install.
If desired, you can type an alternative URL. For more information, see Section 1.4, Downloading and Installing Plug-ins During Installation. When using an alternative URL for downloading plug-ins, it is solely your responsibility to verify the URL contents, and verify that the plug-in is appropriate for your use.
If the message No plug-ins found or server not available appears in the plug-in download area, either or both of the following conditions exist: There are no updated plug-ins available on the Novell download site, or connecting to the Novell Descriptor File was not successful. Verify your Internet connection.
Read the Pre-installation summary page and click . Information on this page includes the following:
New plug-ins that were not installed with a previous version of iManager. These plug-ins are located in the extracted_install_directory\products\imanager\packages directory.
Existing plug-ins that were installed with a previous version of iManager and that do not have a newer version of the plug-in available on the Novell download site.
Updated plug-ins that were installed with a previous version of iManager and that do have newer version of the plug-in available on the Novell download site.
New download plug-ins that were not installed with a previous version of iManager and are not contained in the extracted_install_directory\products\imanager\packages directory.
During installation, iManager files are installed, plug-ins are downloaded, and configuration changes occur. Installation can take several minutes.
After the installation completes, wait several seconds for iManager to initialize before you access iManager. See Section 3.0, Accessing iManager.
If your server has previous versions of iManager installed and you created RBS or custom content, you must update the modules. See Section 2.0, Updating Role-Based Services.
To prepare for the installation, review the following checklist of prerequisites.
In addition to the general prerequisites listed in Section 1.2, Prerequisites, the following prerequisites also apply to iManager on Solaris:
Solaris Patch: Install Solaris Patch 112438, if it is not already installed.
Required Solaris Libraries: Solaris GUI libraries must be installed. The iManager installer for Solaris requires Solaris GUI libraries to function. It does not support command line or headless installation.
WARNING:Do not use the -i console (non-GUI) install option to install iManager 2.6 on Solaris. The only installation method supported for Solaris is a graphical (GUI) install. However, this does not preclude using a Silent Installation of iManager as long as the GUI libraries are installed.
Previous versions of iManager: If you have installed iManager 1.5. x on the server, you must uninstall this version before proceeding to install iManager 2.6. If you have installed iManager 2.5 or 2.6, you do not need to uninstall it; the iManager 2.6 installation can overwrite the files. The uninstall process does not remove custom-created content. For more information, see Section 4.0, Uninstalling iManager 2.6.
Port Setup: Be aware of possible port conflicts. Apache, Tomcat, and the JVM* (as part of the Sun JRE), are installed with the iManager installation program. The iManager installation program checks to see if ports 80 and 443 are in use. (For example, eDirectory uses port 80 by default with its HTTP stack.) If they are in use, the install automatically assigns alternative ports and allows you to change them.
Disk Space: 400 MB minimum
Memory: Minimum 512 MB RAM (1024 MB recommended)
iManager installs the following products during installation:
Tomcat 4.1.30
Apache 2.0.52
Sun JRE 1.4.2.06
Novell International Cryptographic Infrastructure (NICI) 2.6.8
At the Novell download site, search for iManager products, select iManager 2.6, then download iMan_26_sol.tzg.
Extract iMan_26_sol.tzg using the following command:
gzip -dc iMan_26_sol.tgz | tar xvf -
Open a shell and go to your_install_directory/installs/unix directory.
This path is relative to the directory where you copied or extracted the iManager files.
Enter the following command:
./iManagerInstallSolaris.bin
On the opening iManager 2.6 splash screen, select a language, then click .
On the introduction page, click .
Accept the license agreement, then click .
Read the Detection Summary page, then click .
The Detection Summary page lists what is installed and what is about to be installed. If necessary, you can add to the list of installed software in case the installer does not detect everything that is loaded.
Select the plug-ins to download and install, then click .
If desired, you can specify an alternative URL. For more information, see Section 1.4, Downloading and Installing Plug-ins During Installation. When using an alternative URL for downloading plug-ins, it is solely your responsibility to verify the URL contents, and verify that the plug-in is appropriate for your use.
If the message No plug-ins found or server not available appears in the plug-in download area, either or both of the following conditions exist: There are no updated plug-ins available on the Novell download site, or connecting to the Novell Descriptor File was not successful. Verify your Internet connection.
To install plug-ins from a local directory, browse to and select the desired plug-ins ( .npm), then click .
This lets you to install previously downloaded or custom plug-ins during the installation.
On the Authorized User Information page, type the authorized user's full context and the tree he or she will manage, then click .
This information is not used to authenticate to eDirectory during installation and the information is not validated in any way. Make sure you use the syntax required by the iManager login page (see Accessing iManager.)
Providing an Authorized User at this time during the install is optional, but leaving these fields blank causes iManager to allow all users the ability to install plug-ins and make changes to iManager server settings (not recommended long-term.) Specify an authorized user post-install from the
>
>
>
page in iManager. For more information, see
Authorized Users
in the
iManager 2.6 Administration Guide.
Read the Preinstallation summary page that gives the summation of what will occur during the installation, then click .
During installation, iManager files are installed, plug-ins are downloaded, and configuration changes occur. Installation can take several minutes.
After the installation completes, you might need to wait several seconds for iManager to initialize before you can access iManager. To access iManager after the install completes, see Section 3.0, Accessing iManager.
If you have installed a previous version of iManager and created RBS or custom content, you need to update the modules. See Section 2.0, Updating Role-Based Services.
To prepare for the installation, review the following checklist of prerequisites.
In addition to the general prerequisites listed in Section 1.2, Prerequisites, the following prerequisites also apply to iManager on HP-UX:
Required Patches: Confirm that HP-UX is updated with patch PHSS_26560. You can download this patch from the HP IT Resource Center Web site.
Required HP-UX Packages: The following HP-UX packages must be installed before installing iManager on HP-UX. If necessary, you can locate these packages with an Internet search.
gettext-0.12
libiconv-1.9
Java 2 SDK for HP-UX version 1.4.1.x as a minimum (1.4.2.x is recommended)
NOTE:Novell has tested iManager 2.6 only with the package versions noted here. Newer versions of these packages might or might not function properly with iManger 2.6.
Previous versions of iManager: If you have installed a previous version of iManager, you do not need to uninstall it. The iManager 2.6 installation can overwrite the files. The uninstall process does not remove custom-created content.
Processor: PA-RISC 2.0 processor
Disk Space: 400 MB of disk space. Make sure there is at least 50 MB free space on the HP-UX root partition so that the installer functions properly. Otherwise, the iManager installation might fail.
Install the HP-UX Web Server Suite version 2.11 from the HP Software Depot Web site.
The suite contains the official versions of Apache and Tomcat that are supported for HP-UX.
Select the download with all components:
HP-UX Apache-based Web Server
HP-UX Tomcat-based Servlet Engine
HP-UX Webmin-based Admin
Install Java 1.4.2_04 - 1.4.2_08 from the HP Java for HP-UX Web site, and update Java class path to find this version of Java.
Add the JAVA_HOME environment variable to Tomcat’s /opt/hpws/tomcat/bin/setenv.sh. For example:
JAVA_HOME=/opt/java
Install a new certificate for Apache and then copy it to /opt/hpws/apache/conf/ssl.crt/ and /opt/hpws/apache/conf/ssl.key/.
The certificate that is installed with Apache on HP-UX does not have the correct information for your server. You can install a self-signed certificate or a certificate that you purchase from a trusted authority.The Webmin administration tool can generate keys, certificates, and certificate requests for Apache. Webmin is installed with the HP-UX Web Server Suite. For more information, see the HP-UX Web Server Suite documentation, which is accessible from your HP-UX Apache installation (http://ip_address). Specific information on using Webmin to generate keys, certificates, and certificate requests is at http://ip_address/hp_docs/faq/#security11.
IMPORTANT:Make sure you use the correct DNS name or IP address for the common name when you create a new certificate.
At the Novell download Web site, search for iManager products, select iManager 2.6, and then download iMan_26_hp.tgz to a directory on the HP-UX server.
Extract the iMan_26_hp.tgz file. For example:
gzip -dc iMan_26_hp.tgz | tar xvf -
Log out or close the terminal session to load your PATH settings.
Use one of the following commands to install iManager at the location to which you extracted the install files:
For a regular install, enter one of the following commands:
./iManagerInstallHPUX.bin
or
sh iManagerInstallHPUX.bin
For a text-only install, enter the following command:
./iManagerInstallHPUX.bin -i console
IMPORTANT:The iManager installer detects the HP-UX Web Server Suite. Do not change the install path for iManager.
During installation, iManager files are installed, plug-ins are downloaded, and configuration changes occur. Installation can take several minutes.
After the installation completes, you might need to wait several seconds for iManager to initialize before you can access iManager. To access iManager after the install completes, see Section 3.0, Accessing iManager.
If you have installed a previous version of iManager and created RBS or custom content, you need to update the modules. See Section 2.0, Updating Role-Based Services.
To prepare for the installation, review the following checklist of prerequisites.
In addition to the general prerequisites listed in Section 1.2, Prerequisites, the following prerequisites also apply to iManager on Windows:
Previous versions of iManager: Previous versions do not need to be uninstalled. If iManager 2.6 detects version 1.5. x, it uninstalls it before proceeding. If iManager detects version 2.0. x, it overwrites the files. The uninstall process does not remove custom-created content.
Web Services: Windows servers can use either Apache and Tomcat, or Windows Internet Information Services (IIS) and Tomcat. The iManager installation program determines which Web services are already installed. If the Windows server is using IIS and you want to use Apache and Tomcat, you must remove IIS before installing Apache and Tomcat with the iManager installation program. The iManager installation program does not configure IIS to use SSL.
Processor: Pentium III 600 MHz or higher processor
Disk Space: 500 MB minimum for a local installation
Memory: 512 MB of RAM (1024 MB recommended)
iManager can install the following products during installation:
Tomcat 4.1.30
Apache 2.0.52
Sun JRE 1.4.2.06
Novell International Cryptographic Infrastructure (NICI) 2.6.8
For information about running iManager Server on the same machine as Novell eDirectory, see
Running eDirectory and iManager on the Same Machine (Windows only)
in the
iManager 2.6 Administration Guide.
At the Novell download site, search for iManager products, select iManager 2.6, then download it to a destination directory on your server.
Extract the file into the iManager folder.
Log in with Administrator privileges to install iManager.
Find and run destination_directory\iManager\installs\win\iManagerInstall.exe
You can view the debug output of the installation program by holding down the Ctrl key immediately after launching the installer. Continue to hold down the key until a console window appears. For more information on debugging, see
Troubleshooting
in the
iManager 2.6 Administration Guide.
On the opening iManager splash screen, select a language and click .
On the introduction page, click .
Accept the license agreement, then click .
Read the Detection Summary page, then click .
The Detection Summary pages tells what is installed and what is about to be installed. If necessary, you can add to the list of installed software in case the installer does not detect everything that is loaded.
Select the plug-ins to download and install, then click .
If desired, you can type an alternative URL. For more information, see Section 1.4, Downloading and Installing Plug-ins During Installation. When using an alternative URL for downloading plug-ins, it is solely your responsibility to verify the URL contents, and verify that the plug-in is appropriate for your use.
If the message No plug-ins found or server not available appears in the plug-in download area, either or both of the following conditions exist: There are no updated plug-ins available on the Novell download site, or connecting to the Novell Descriptor File was not successful. Verify your Internet connection.
To install plug-ins from a local directory, browse to and select the desired plug-ins ( .npm), then click .
This lets you to install previously downloaded or custom plug-ins during the installation.
On the Authorized User Information page, type the authorized user's full context and the tree he or she will manage, then click .
This information is not used to authenticate to eDirectory during installation and the information is not validated in any way. Make sure you use the syntax required by the iManager login page (see Accessing iManager.)
Providing an Authorized User at this time during the install is optional, but leaving these fields blank causes iManager to allow all users the ability to install plug-ins and make changes to iManager server settings (not recommended long-term.) Specify an authorized user post-install from the
>
>
>
page in iManager. For more information, see
Authorized Users
in the
iManager 2.6 Administration Guide.
Read the Pre-installation summary page, then click .
During installation, iManager files are installed, plug-ins are downloaded, and configuration changes occur. Installation can take several minutes.
After the installation completes, a browser window appears displaying the Gettting Started page. Wait for iManager to initialize before attempting access.
To access iManager, click the first link on the Getting Started page, then log in. For more information, see Section 3.0, Accessing iManager.
IMPORTANT:If you are using IIS and if you have multiple Web sites running on the server, see the Page Not Found Error for additional information.
If you have installed a previous version of iManager and created RBS or custom content, you need to update the modules. See Section 2.0, Updating Role-Based Services.
To prepare for the installation, review the following checklist of prerequisites.
In addition to the general prerequisites listed in Section 1.2, Prerequisites, the following prerequisites also apply to iManager Workstation on Linux Clients:
Required Linux Packages: If any of the following packages are not installed, you must obtain them from the vendor of your Linux distribution and install them before installing iManager. They should be on your installation CDs.
GTK2
GLIBC 2.3
Processor: Pentium III 600 MHz or higher processor
Disk Space: 200 MB minimum
Memory Requirements: 256 MB RAM (512 MB recommended)
IMPORTANT:Do not run Mobile iManager from a path that contains spaces.
iManager includes or installs the following products:
Tomcat 4.1.30
Sun J2SDK 1.4.2.05
Novell International Cryptographic Infrastructure (NICI) 2.6.8
At the Novell download site, search for iManager products, select iManager 2.6, then download iMan_26_Mobile_iManager_linux.tar.bz2 to a directory on your server.
Extract the file using the following command:
tar -xjvf iMan_26_Mobile_iManager_linux.tar.bz2
Install the Novell International Cryptography Infrastructure (NICI) software located in the NICI/Linux directory of the expanded iMan_26_Mobile_iManager_linux.tar directory. To do this, execute the following command from the NICI directory:
rpm -Uvh nici.i386.rpm
You must be logged in as root to install or upgrade NICI.
On desktops where NICI is not installed, this command installs NICI. On desktops where NICI is already installed, this command upgrades NICI.
Go to the imanager/bin directory.
cd ./imanager/bin
Execute the startup script.
./iManager.sh
When the iManager login screen appears, specify a username, password, and eDirectory tree.
To access iManager, see Section 3.0, Accessing iManager.
If you have installed a previous version of iManager and created RBS or custom content, you need to update the modules. See Section 2.0, Updating Role-Based Services.
To prepare for the installation, review the following checklist of prerequisites.
Additional Configuration: If you configure Internet Explorer to use a proxy server for your LAN, then you must also select the > > > > option.
Processor: Pentium III 600 MHz or higher processor
Disk Space: 200 MB minimum
Memory: 256 MB of RAM (512 MB recommended)
Do not run Mobile iManager from a path with spaces in it.
If you are running a Novell Client™ earlier than version 4.91, make sure that the NMAS™ client is already installed on the workstation before launching Mobile iManager.
Installing Mobile iManager to C:\temp is not supported. If you do this, the plug-ins won't install. Install Mobile iManager in C:\imanager or some other permanent directory, rather than c:\temp\imanager.
The first time you run Mobile iManager on a Windows workstation, you must do so as a user that is a member of the workstation's Administrators group.
iManager includes or installs the following products:
Tomcat 4.1.30
Sun JRE 1.4.2.06
Novell International Cryptographic Infrastructure (NICI) 2.6.8
At the Novell download site, search for iManager products, select iManager 2.6, then download iMan_26_Mobile_iManager_win.zip.
Using any ZIP program, extract the iMan_26_Mobile_iManager_win.zip file to a folder close to the system root with no more than 15 characters in the pathname.
Browse to the imanager\bin folder.
To execute the script, double-click the iManager.bat file.
When the iManager login page appears, enter your username, password, and tree.
To access iManager, see Section 3.0, Accessing iManager.
If you have installed a previous version of iManager and created RBS or custom content, you must update the modules. See Section 2.0, Updating Role-Based Services.