Novell iManager 2.5 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” before installing iManager.
Root access is required for installation.
In addition to the general prerequisites listed in Section 1.4, Prerequisites, the following prerequisites also apply to iManager on HP*-UX*:
Ensure that the OS is updated with patch PHSS_26560. You can download this patch from the HP IT Resource Center Web site.
If you have installed iManager 2.0.x, you do not need to uninstall it. The iManager 2.5 installation can overwrite the files. The uninstall process does not remove custom-created content such as tasks.
Install the HP-UX Web Server Suite version 2.08 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:
Install Java 1.4.2_04 or later from the HP Java for HP-UX Web site and update your path to find the new Java.
Add the JAVA_HOME environment variable to the Tomcat setenv.sh file located in /opt/hpws/tomcat/bin.
For example:
JAVA_HOME=/opt/java
Install a new certificate for Apache and then copy it to the following directories:
/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 Apache installation (http://ip_address). For information on using Webmin to generate keys, certificates, and certificate requests, go to 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 site, search for iManager products, select, and then download iMan_25_hp.tgz to a directory on your server.
Extract the iMan_25_hp.tgz file.
For example:
gzip -dc iMan_25_hp.tgz | tar xvf -
Log out or close the terminal session to load your PATH settings.
Use one of these commands to install iManager at the location you extracted the install files to:
For a regular install, enter the following command:
./iManagerInstallHPUX.bin
or
sh iManagerInstallHPUX.bin
For a text-only install, enter the following command:
./iManagerInstallHPUX.bin -i console
For a silent install, enter the following command:
./iManagerInstallHPUX.bin -i silent
IMPORTANT:The iManager installer detects the HP-UX Web Server Suite. Do not change the install path for iManager.
After the installation completes, wait several seconds for iManager to initialize before you can access iManager. 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 upgrade them to version 2.5. See Section 2.0, Upgrading to iManager 2.5.
Root access is required for installation.
In addition to the general prerequisites listed in Section 1.4, Prerequisites, the following prerequisites also apply to iManager on Linux:
If you are missing any of these packages, you must obtain them from the vendor of your Linux distribution and install them before installing iManager. They should be on your installation CDs.
If you have installed iManager 1.5.x on the server, you must uninstall this version before proceeding to install iManager 2.5. If you have installed iManager 2.0.x, you do not need to uninstall it. The iManager 2.5 installation can overwrite the files. The uninstall process does not remove custom-created content such as tasks.
If you are installing iManager on a server with eDirectory already installed on it, the eDirectory version needs to be 8.7.3 or later for iManager 2.5.
If you are installing iManager on a server without eDirectory, you must have eDirectory 8.6.2 or later installed on another available server.
Be aware of possible port conflicts. Apache, Tomcat, and JVM* are 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 Apache to run on. By default, Apache uses ports 80 and 443, and Tomcat uses ports 8080, 8005, and 9009.
IMPORTANT:On Linux, iManager is supported with the versions of Apache and Tomcat that are installed with iManager only.
At the Novell download site, search for iManager products, select, and then download iMan_25_linux.tgz to a directory on your server.
Extract the file using the following command:
tar -zxvf iMan_25_linux.tgz
Open a shell and change to the install_directory/iManager_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 regular install, enter the following command:
./install.sh
After a successful install, the installer generates a configuration file (/etc/opt/novell/ imanager_install.conf) with values based upon the questions asked during the install. This file can then be modified and used for a silent install.
To perform a silent install, enter the following command:
sh install.sh --silent --c-file=path_to_conf_file
To see a list of all the install options (local/remote) issue the following command:
sh install.sh --help
This command runs the pre-install and then touches the python script that displays the help menu.
Follow the on-screen prompts.
To accept the defaults, press Enter. The text within the brackets at the prompt is the default selection. To accept the default, press Enter.
After the installation completes, you might need to wait several seconds for iManager to initialize before you can access iManager. 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 upgrade them to version 2.5. See Section 2.0, Upgrading to iManager 2.5.
Root access is required for installation.
At the Novell download site, search for iManager products, select , and then download iMan_25_Mobile_iManager_linux.tar.bz2 to a directory on your server.
Extract the file using the following command:
tar -xjvf iMan_25_Mobile_iManager_linux.tar.bz2
Install the Novell International Cryptography Infrastructure (NICI) software located in the NICI directory of the expanded iMan_25_Mobile_iManager_linux.tar directory.
From the NICI directory, execute the following command.
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.
rpm -Uvh nici-2.6.4-0.05.i386.rpm
To access iManager after NICI is installed, see Section 3.0, Accessing iManager.
If you have installed a previous version of iManager and created RBS or custom content, you need to upgrade them to version 2.5. See Section 2.0, Upgrading to iManager 2.5.
Administrator access is required for installation.
In addition to the general prerequisites listed in Section 1.4, Prerequisites, the following prerequisites also apply to iManager on NetWare 6.5:
At the Novell download site, search for iManager products, select , and from the list, download and extract iMan_25_NW65_Standalone.zip to the sys volume.
In the NetWare 6.5 GUI, click the button, and then click > .
Browse to the extracted location, select the product.ini file, then click .
Follow the on-screen instructions.
After the installation completes, wait several seconds for iManager to initialize before you can access iManager. To access iManager, see Section 3.0, Accessing iManager.
If your server had iManager 2.0.x installed and you created RBS or custom content, you must upgrade them to version 2.5. See Section 2.0, Upgrading to iManager 2.5.
Root access is required for installation.
In addition to the general prerequisites listed in Section 1.4, Prerequisites, the following prerequisites also apply to iManager on Solaris*:
If you have installed iManager 1.5.x on the server, you must uninstall this version before proceeding to install iManager 2.5. If you have installed iManager 2.0.x, you do not need to uninstall it. The iManager 2.5 installation can overwrite the files. The uninstall process does not remove custom-created content such as tasks.
If you are installing iManager on a server with eDirectory already installed on it, the eDirectory version needs to be 8.7.3 or later to avoid conflicts with packages that are shared between both eDirectory and iManager.
If you are installing iManager on a server without eDirectory, you must have eDirectory 8.6.2 or later installed on another available server.
Be aware of possible port conflicts. Apache, Tomcat, and JVM are installed with the iManager installation program. The iManager installation program checks to see if port 80 or 443 are in use. (For example, eDirectory uses port 80 by default with its HTTP stack.) If they are in use, the install prompts you for different ports for Apache to run on.
At the Novell download site, search for iManager products, select , and then download iMan_25_sol.tzg.
Extract iMan_25_sol.tzg using the following command:
gzip -dc iMan_25_sol.tgz | tar xvf-
Open a shell and change to the 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
Follow the prompts.
After the installation completes, 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 must upgrade them to version 2.5. See Section 2.0, Upgrading to iManager 2.5.
You must log in as an administrator to install iManager.
In addition to the general prerequisites listed in Section 1.4, Prerequisites, the following prerequisites also apply to iManager on Windows:
Windows servers can use either Apache and Tomcat or Windows Web 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.
The iManager 2.5 installation program installs and configures the following items if it does not detect a compatible version:
IMPORTANT:If your system is preconfigured with Java/Apache/Tomcat/mod_jk2Tomcat, you might need to create the nps-apache.conf file with the following lines:
alias /nps <tomcatroot>/webapps/nps<LocationMatch "/nps/*.jsp"> JkUriSet worker ajp13:localhost:8009 </LocationMatch><LocationMatch "/nps/servlet/*"> JkUriSet worker ajp13:localhost:8009 </LocationMatch><LocationMatch "/nps/services/*"> JkUriSet worker ajp13:localhost:8009 </LocationMatch>
After you create this file, edit the apache configuration file in APACHE_HOME/conf/httpd.conf and append the following line to the end of the file:
Example: Include C:\Program Files\Novell\Apache\conf\nps-Apache.conf
At the Novell download site, search for iManager products, select, and then download iManagerInstall.exe to a directory on your server.
Run iManagerInstall.exe.
HINT: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.
Follow the on-screen instructions.
After the installation completes, you might need to wait several seconds for iManager to initialize before you can access iManager. To access iManager, see Section 3.0, Accessing iManager.
IMPORTANT:If multiple Web sites are running on the server, see "Page
not found" Error on a Windows Server
for additional
information.
If you have installed a previous version of iManager and created RBS or custom content, you need to upgrade them to version 2.5.
IMPORTANT:Mobile iManager requires that the NMAS client be installed on the workstation. If you are running a Novell Client™ earlier than version 4.9.1, you must make sure that the NMAS client is already installed on the workstation before launching Mobile iManager. If the 4.9.1 Client is already installed or if the Novell Client is not installed at all, Mobile iManager auto-installs the NMAS client for you.
At the Novell download site, search for iManager products, select, and then download iMan_25_Mobile_iManager_win.zip.
Extract the file.
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 upgrade them to version 2.5. See Section 2.0, Upgrading to iManager 2.5.