The following prerequisites apply to all platforms. Additional platform-specific prerequisites are listed in the next section by platform.
Note: If you want to use your 1.x collections and roles with this version of iManager, they will need to be updated through the iManager 2.x Configuration Wizard.
Prerequisites
In addition to the general prerequisites listed in General Prerequisites, the following prerequisites apply to iManager on NetWare 6.0:
Procedure
For detailed iManager installation instructions, see the Novell iManager 2.0.x Administration Guide.
To install iManager on NetWare 6.0:
Determine the ports that Apache is listening on. Open the sys:\Apache\conf\adminserv.conf file and find the following line:
# Start Apache Services Port Configuration
Note the ports for both HTTP and HTTPS (Listen and SecureListen directives).
Open a Web browser and connect to iManager at the port discovered in Step 6. For example:
https://IP:SecureListen port/nps/iManager.html
Prerequisites
In addition to the general prerequisites listed in General Prerequisites, the following prerequisites apply to iManager on Windows:
Web servicesWindows servers can use 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.
IMPORTANT: iManager 2.0.2 does not support IIS 6 on Windows 2003 Server. Apache 2 is supported on Windows 2003 Server.
The iManager 2.0.2 installation program installs and configures the following items if it does not detect a compatible version:
If you are installing iManager on the same machine as eDirectory, verify that you have Require TLS for Simple Binds with Password checked on the LDAP Group object for the server that you are using to set up iManager. If this check box is not checked, iManager is installed in non-secure mode and plug-ins that require secure mode will fail.
Procedure
For detailed iManager installation instructions, see the Novell iManager 2.0.x Administration Guide.
To install iManager on Windows:
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.
Extract the iMan_202_linux.tgz file to a directory on your server. Use the following command:
tar -zxvf iMan_202_linux.tgz
Prerequisites
In addition to the general prerequisites listed in General Prerequisites, the following prerequisites apply to iManager on Linux:
eDirectory setup
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.
Port setup
Be aware of possible port conflicts. Apache, Tomcat, and a JVM are installed with the iManager installation program, which determines whether port 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 prompts you for different ports for Apache to run on. Tomcat ports are not detected. Tomcat uses ports 8080, 8005, and 8009. If another version of Tomcat is running, it is not detected, and a port conflict might occur.
Make sure you have a recent version of gettext on your server. To check if you have gettext, enter the following command from a shell:
gettext -V
If gettext exists, the command displays the version number.
If you do not have gettext, you must obtain it from the vendor of your Linux distribution and install it before installing iManager.
IMPORTANT: On Linux, iManager only works with the versions of Apache and Tomcat that are installed with iManager.
Procedure
For detailed iManager installation instructions, see the Novell iManager 2.0.x Administration Guide.
To install iManager on Linux:
Enter the following command:
./install.sh
Launch a supported browser and go to:
https://server_ip_address:port_number/nps/iManager.html
IMPORTANT: This URL is case sensitive. The server IP address can also be a DNS name.
Extract the iMan_202_sol.tgz file to a directory on your server. Use the following command:
gzip -dc iMan_202_sol.tgz | tar xvf -
Prerequisites
In addition to the general prerequisites listed in General Prerequisites, the following prerequisites apply to iManager on Solaris:
Sun* Solaris 8 or 9 (SPARC* processors only) with the latest patches installed from the SunSolve Web site
IMPORTANT: If you are using Solaris 8, make sure that you have installed patch 112438.02 and that the OS version is dated October 2001 or later.
eDirectory setup
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.
Port setup
Be aware of possible port conflicts. Apache, Tomcat, and a JVM are installed with the iManager installation program, which determines whether port 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 prompts you for different ports for Apache to run on. Tomcat ports are not detected. Tomcat uses ports 8080, 8005, and 8009. If another version of Tomcat is running, it is not detected, and a port conflict might occur.
Procedure
For detailed iManager installation instructions, see the Novell iManager 2.0.x Administration Guide.
To install iManager on Solaris:
Enter the following command:
./iManagerInstallSolaris.bin
For text only, enter the following command:
./iManagerInstallSolaris.bin -i console
Stop and re-start Tomcat, then Apache by entering the following commands:
/var/opt/novell/tomcat4/bin/shutdown.sh
/var/opt/novell/tomcat4/bin/startup.sh
/var/opt/novell/httpd/bin/apachectl stop
/var/opt/novell/httpd/bin/apachectl startssl
These services are not configured to start at boot-up.
Launch a suppored browser and go to:
https://server_ip_address:port_number/nps/iManager.html
IMPORTANT: This URL is case sensitive. The server IP address can also be a DNS name.
Prerequisites
In addition to the general prerequisites listed in General Prerequisites, the following prerequisites apply to iManager on HP-UX:
eDirectory setup
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.
Procedure
For detailed iManager installation instructions, see the Novell iManager 2.0.x Administration Guide.
To install iManager on HP-UX:
Install the HP-UX Web Server Suite version 1.0.06.01 from the HP Software Depot Web site. The suite contains the official versions of Apache and Tomcat that are supported for HP-UX. You can update to version 1.0.10.01 after you create a new Apache SSL certificate in Step 4.
NOTE: The version of openssl (0.9.7b) included with the HP-UX Web Server Suite versions A100901 and A101001 has problems generating certificates through Webmin. Install HP-UX Web Server Suite version A100601, which contains openssl version 0.9.6i, create a new SSL certificate for Apache through Webmin, and then update your HP-UX Web Server Suite to a newer version if you are installing iManager 2.0.2. If you would like to create certificates with openssl through Webmin in the future, back up /opt/hpws/Apache/bin/openssl before updating your HP-UX Web Server Suite from version A100601.
Select the download with all components:
Add and export the following environment variables in the environment setting for the user that will be running Tomcat (usually located in the .bashrc file): JAVA_HOME, CATALINA_HOME, APACHE_HOME, SHLIB_PATH.
For example:
JAVA_HOME=/opt/java
APACHE_HOME=/opt/hpws/apache
CATALINA_HOME=/opt/hpws/tomcat
SHLIB_PATH=/usr/lib:/usr/lib/nds-modules:$SHLIB_PATH
export JAVA_HOME APACHE_HOME CATALINA_HOME SHLIB_PATH
Install a new certificate for Apache. You must complete this step before continuing the installation. The certificate that is installed with Apache on HP-UX does not have the correct information for your server. You can install a certificate that you purchase from a trusted authority or a self-signed certificate.
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.
Copy the certificates to the Apache directory: /opt/hpws/apache/conf/ssl.crt/ and /opt/hpws/apache/conf/ssl.key/.
Extract the iMan_202_sol.tgz file to a directory on your server. Use the following command:
gzip -dc iMan_202_hp.tgz | tar xvf -
Type the following command:
./iManagerInstallHPUX.bin
or
sh iManagerInstallHPUX.bin
For text only, 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.
Start Tomcat and Apache. The command you use depends on your iManager configuration:
/opt/hpws/tomcat/bin/startup.sh
/opt/hpws/apache/bin/apachectl start
or
/opt/hpws/apache/bin/apachectl startssl
NOTE: Tomcat might take 60 seconds or longer to load before you can access iManager, depending on the performance of your server.
This option lets you download an exact copy of the Novell eDirectory 8.7.3 Web Applications distribution CD, which includes the following:
After you download the .iso file (eDir_873_webapps.iso) and burn the .iso image to CD, an exact duplicate of the original eDirectory 8.7.3 Web Applications CD is created. Neither iManager nor eGuide can be installed directly from the electronic .iso file. A CD image of the file MUST be created first. Create the installation CD according to the instructions for your CD imaging software.
Note: Do not burn the .iso file to CD. Burn the contents of the .iso file (the .iso image) to CD.
Select the desired platform:
Note: If you want to use your 1.x collections and roles with this version of iManager, they will need to be updated through the iManager 2.x Configuration Wizard.
Prerequisites
In addition to the general prerequisites listed in General Prerequisites, the following prerequisites apply to iManager on NetWare 6.0:
Procedure
For detailed iManager installation instructions, see the Novell iManager 2.0.x Administration Guide.
To install iManager on NetWare 6.0:
Determine the ports that Apache is listening on. Open the sys:\Apache\conf\adminserv.conf file and find the following line:
# Start Apache Services Port Configuration
Note the ports for both HTTP and HTTPS (Listen and SecureListen directives).
Open a Web browser and connect to iManager at the port discovered in Step 6. For example:
https://IP:SecureListen port/nps/iManager.html
Prerequisites
In addition to the general prerequisites listed in General Prerequisites, the following prerequisites apply to iManager on Windows:
Web servicesWindows servers can use 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.
IMPORTANT: iManager 2.0.2 does not support IIS 6 on Windows 2003 Server. Apache 2 is supported on Windows 2003 Server.
The iManager 2.0.2 installation program installs and configures the following items if it does not detect a compatible version:
If you are installing iManager on the same machine as eDirectory, verify that you have Require TLS for Simple Binds with Password checked on the LDAP Group object for the server that you are using to set up iManager. If this check box is not checked, iManager is installed in non-secure mode and plug-ins that require secure mode will fail.
Procedure
For detailed iManager installation instructions, see the Novell iManager 2.0.x Administration Guide.
To install iManager on Windows:
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.
Prerequisites
In addition to the general prerequisites listed in General Prerequisites, the following prerequisites apply to iManager on Linux:
eDirectory setup
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.
Port setup
Be aware of possible port conflicts. Apache, Tomcat, and a JVM are installed with the iManager installation program, which determines whether port 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 prompts you for different ports for Apache to run on. Tomcat ports are not detected. Tomcat uses ports 8080, 8005, and 8009. If another version of Tomcat is running, it is not detected, and a port conflict might occur.
Make sure you have a recent version of gettext on your server. To check if you have gettext, enter the following command from a shell:
gettext -V
If gettext exists, the command displays the version number.
If you do not have gettext, you must obtain it from the vendor of your Linux distribution and install it before installing iManager.
IMPORTANT: On Linux, iManager only works with the versions of Apache and Tomcat that are installed with iManager.
Procedure
For detailed iManager installation instructions, see the Novell iManager 2.0.x Administration Guide.
To install iManager on Linux:
Enter the following command:
./install.sh
Launch a supported browser and go to:
https://server_ip_address:port_number/nps/iManager.html
IMPORTANT: This URL is case sensitive. The server IP address can also be a DNS name.
Prerequisites
In addition to the general prerequisites listed in General Prerequisites, the following prerequisites apply to iManager on Solaris:
Sun* Solaris 8 or 9 (SPARC* processors only) with the latest patches installed from the SunSolve Web site
IMPORTANT: If you are using Solaris 8, make sure that you have installed patch 112438.02 and that the OS version is dated October 2001 or later.
eDirectory setup
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.
Port setup
Be aware of possible port conflicts. Apache, Tomcat, and a JVM are installed with the iManager installation program, which determines whether port 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 prompts you for different ports for Apache to run on. Tomcat ports are not detected. Tomcat uses ports 8080, 8005, and 8009. If another version of Tomcat is running, it is not detected, and a port conflict might occur.
Procedure
For detailed iManager installation instructions, see the Novell iManager 2.0.x Administration Guide.
To install iManager on Solaris:
Enter the following command:
./iManagerInstallSolaris.bin
For text only, enter the following command:
./iManagerInstallSolaris.bin -i console
Stop and re-start Tomcat, then Apache by entering the following commands:
/var/opt/novell/tomcat4/bin/shutdown.sh
/var/opt/novell/tomcat4/bin/startup.sh
/var/opt/novell/httpd/bin/apachectl stop
/var/opt/novell/httpd/bin/apachectl startssl
These services are not configured to start at boot-up.
Launch a suppored browser and go to:
https://server_ip_address:port_number/nps/iManager.html
IMPORTANT: This URL is case sensitive. The server IP address can also be a DNS name.
Prerequisites
In addition to the general prerequisites listed in General Prerequisites, the following prerequisites apply to iManager on HP-UX:
eDirectory setup
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.
Procedure
For detailed iManager installation instructions, see the Novell iManager 2.0.x Administration Guide.
To install iManager on HP-UX:
Install the HP-UX Web Server Suite version 1.0.06.01 from the HP Software Depot Web site. The suite contains the official versions of Apache and Tomcat that are supported for HP-UX. You can update to version 1.0.10.01 after you create a new Apache SSL certificate in Step 4.
NOTE: The version of openssl (0.9.7b) included with the HP-UX Web Server Suite versions A100901 and A101001 has problems generating certificates through Webmin. Install HP-UX Web Server Suite version A100601, which contains openssl version 0.9.6i, create a new SSL certificate for Apache through Webmin, and then update your HP-UX Web Server Suite to a newer version if you are installing iManager 2.0.2. If you would like to create certificates with openssl through Webmin in the future, back up /opt/hpws/Apache/bin/openssl before updating your HP-UX Web Server Suite from version A100601.
Select the download with all components:
Add and export the following environment variables in the environment setting for the user that will be running Tomcat (usually located in the .bashrc file): JAVA_HOME, CATALINA_HOME, APACHE_HOME, SHLIB_PATH.
For example:
JAVA_HOME=/opt/java
APACHE_HOME=/opt/hpws/apache
CATALINA_HOME=/opt/hpws/tomcat
SHLIB_PATH=/usr/lib:/usr/lib/nds-modules:$SHLIB_PATH
export JAVA_HOME APACHE_HOME CATALINA_HOME SHLIB_PATH
Install a new certificate for Apache. You must complete this step before continuing the installation. The certificate that is installed with Apache on HP-UX does not have the correct information for your server. You can install a certificate that you purchase from a trusted authority or a self-signed certificate.
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.
Copy the certificates to the Apache directory: /opt/hpws/apache/conf/ssl.crt/ and /opt/hpws/apache/conf/ssl.key/.
Type the following command:
./iManagerInstallHPUX.bin
or
sh iManagerInstallHPUX.bin
For text only, 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.
Start Tomcat and Apache. The command you use depends on your iManager configuration:
/opt/hpws/tomcat/bin/startup.sh
/opt/hpws/apache/bin/apachectl start
or
/opt/hpws/apache/bin/apachectl startssl
NOTE: Tomcat might take 60 seconds or longer to load before you can access iManager, depending on the performance of your server.
For information on additional issues for this release, see the Novell iManager 2.0.2 readme file.
For iManager documentation, see the Novell Product Documentation Web site.
Disclaimer, Export Notice, Copyright, and Patents
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.
Copyright © 2002-2004 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell Trademarks
Novell and NetWare are registered trademarks of Novell, Inc. in the United States and other countries.
eDirectory is a trademark of Novell, Inc.
Third-Party Trademarks
All third-party trademarks are the property of their respective owners.