Novell iManager 2.0.2 can be installed on the platforms covered in this section. In general, you should apply the latest service packs for your platform and have met the prerequisites listed in the preceding section before installing iManager. This section provides instructions for installing iMangager on the following platforms:
IMPORTANT: The instructions in this guide do not apply when installing iManager with Novell NterpriseTM Linux Services. Please follow the prerequisites and installation instructions provided in the Novell Nterprise Linux Services Installation Guide.
You can install iManager 2.0.x from the NetWare® 6.5 product CD or from a standalone installation file.
In addition to the general prerequisites listed in Prerequisites, the following prerequisites apply to iManager on NetWare 6.5:
iManager 2.0.x is installed with the NetWare 6.5 installation program. For more information, see the NetWare 6.5 Overview and Installation Guide. If you have already installed NetWare 6.5 without iManager, you can install the program separately using the NetWare 6.5 product CD.
NOTE: The NetWare 6.5 SP1 CDs are required to install iManager 2.0.2.
To install iManager using the NetWare 6.5 product CD:
Verify that LDAP SSL is running. Run TCPCON from the NetWare console. Select Protocol Information > TCP > TCP Connections. Verify that port 636 is shown in the list of open ports.
Run PKI Diag Utility (PKIDIAG). For more information, see Technical Information Document #2963420.
Insert the Products CD (disk 2) from the NetWare 6.5 product CD set.
From the NetWare 6.5 GUI, click the Novell button, then select Install > Add.
Browse for the postinst.ni file located on the Products CD.
Select iManager 2.0.x.
Follow the on-screen instructions.
In addition to the general prerequisites listed in Prerequisites, the following prerequisites apply to iManager on NetWare 6.0:
NOTE: NetWare 5.1 is not supported.
Apache 1.3 HTTP server (installed with NetWare 6)
NOTE: Apache 2.0 is not supported.
Determine whether Tomcat 3.3 is listening on port 8080 (for Tomcat 3.3, this is disabled by default, but may have been enabled for debugging purposes). If the port is enabled, disable it by commenting out the Http10Interceptor tag in sys:\tomcat\33\nwserver.xml, then restart Tomcat 3.3 (at the command NetWare command prompt, type tomcat stop followed by tomcat33).
Verify that LDAP SSL is running. Run TCPCON from the NetWare console. Select Protocol Information > TCP > TCP Connections. Verify that port 636 is shown in the list of open ports.
Run PKI Diag Utility (PKIDIAG). For more information, see Technical Information Document #2963420.
Verify that there is adequate disk space on the volume. You will need approximately 200 MB of free disk space.
Verify that Tomcat 3.3 is installed. The server should have a sys:\tomcat\33\ folder, and when you type JAVA -SHOW at the NetWare command line, org.apache.tomcat.startup.Main should appear in the list of Java processes.
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).
Download the iMan_20x_NW60.exe file from Novell Product Downloads.
Create a directory on your server (for example, sys:\imanager202).
Run the iMan_20x_NW60.exe file and extract its contents to the directory you've created on the sys: volume on your NetWare 6 server.
From the NetWare 6 GUI, click the Novell button, then select Install > Add.
Select the product.ni file (that was copied to the directory on the sys: volume) for iManager 2.0.x and complete the installation program.
(iManager 2.0.1 only) Modify the sys:\tomcat\4\webapps\nps\WEB-INF\PortalServlet.properties file. Find the line Custom_Backend_Renderer_Portal_Location=http\://127.0.0.1/nps. Replace 127.0.0.1 with the actual IP address and non-secure HTTP port (see Step 6) of the Web server where iManager is running.
If there are problems with the back end renderer location, you might encounter a blank screen when attempting to access iManager. One troubleshooting technique that may be useful is to turn off XML rendering in the URL, for example:
https://IP:SecureListen port/nps/servlet/portal?render=off
For more information on the back end renderer blank screen condition, see Technical Information Document #10070553.
Modify the connector redirect ports in server.xml.
Open the sys:\tomcat\4\conf\server.xml file.
Find the Connector element that defines the HTTP/1.1 connector. The port is typically set to 8080. Change the redirectPort attribute from the default of 8443 to the port number you found in Step 6.
Find the Connector element that defines the AJP 1.3 connector. The port is typically set to 9009. Change the redirectPort attribute from the default of 8443 to the port number you found in Step 6.
Save your changes to server.xml and close the file.
Restart Tomcat 4. Type TC4STOP at the NetWare console and wait for Tomcat to stop (the logger screen shows "java: Class org.apache.catalina.startup.Bootstrap exited successfully" when Tomcat 4 is down). Type TOMCAT4 to restart Tomcat.
Open a Web browser and connect to iManager at the port discovered in Step 6. For example:
https://IP:SecureListen port/nps/iManager.html
In addition to the general prerequisites listed in Prerequisites, the following prerequisites apply to iManager on Windows:
Windows servers can use Tomcat, 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 either Apache and Tomcat or Tomcat only, you must remove IIS before installing Apache. Tomcat installs automatically 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.
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.
Download the iMan_20x_win.exe file from Novell Product Downloads.
Run the iMan_20x_win.exe file and extract its contents to a temporary directory.
Run iManagerInstall.exe.
Follow the on-screen instructions.
After the installation completes, your Web server is restarted. You might need to wait several seconds for the Web server to initialize before iManager will be available.
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.
IMPORTANT: The instructions in this guide do not apply when installing iManager with Novell NterpriseTM Linux Services. Please follow the prerequisites and installation instructions provided in the Novell Nterprise Linux Services Installation Guide.
In addition to the general prerequisites listed in Prerequisites, the following prerequisites apply to iManager on Linux:
If you are installing iManager on a server with eDirectory already installed on it, the eDirectory version needs to be 8.7.1 for iManager 2.0.1 and 8.7.3 for iManager 2.0.2 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. Tomcat and a JVM are installed with the iManager installation program that determines whether ports 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 Tomcat. Tomcat uses ports 8443 (default), 8080, 8005, or 8009.
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 version of Tomcat that installs with iManager.
Extract the iMan_20x_linux.tgz file to a directory on your server. Use the following command:
tar -zxvf iMan_202_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 the following command:
./install.sh
Follow the on-screen prompts. The text within the brackets at the prompt is the default selection. Press Enter to accept the default.
When prompted to enter the iManager server addresses or DNS host name, the IP address gets auto-detected.
For the admin name, you must use dot notation (for example, cn=admin.o=novell).
LDAP server IP address or DNS hostname defaults to the local machine. Make sure you use the IP address of eDirectory LDAP server in the eDirectory tree where you want to install iManager.
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.
In addition to the general prerequisites listed in Prerequisites, the following prerequisites apply to iManager on Solaris:
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.
If you are installing iManager on a server with eDirectory already installed on it, the eDirectory version needs to be 8.7.1 for iManager 2.0.1 and 8.7.3 for iManager 2.0.2 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. Tomcat and JVM are installed with the iManager installation program. The iManager installation program looks to see if port 8080 or 8443 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.
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
NOTE: iManager 2.0 does not support text-only install for the Solaris platform.
Follow the prompts.
Stop and re-start Tomcat using the following command:
/etc/init.d/
imgr stopstart
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.
Log in as someone with admin-equivalent rights to the eDirectory tree, because the schema will be extended at this time.
To access the Getting Started help screen, open the gettingstarted.html file located in the /var/opt/novell/tomcat4/webapps/nps/help/en/install directory.