Installing Novell iManager

Novell iManager is a browser-based alternative to ConsoleOne for administering, managing, and configuring Novell eDirectory objects. You can manage Tiered Electronic Distribution (TED) objects and agents using iManager.

Select the platform where you want to install the iManager and perform additional configuration as needed:

• Installing the iManager Files on NetWare 6
• Installing the iManager Files on Windows
• Configuring Tomcat and iManager to Meet Special Network Needs

Installing the iManager Files on NetWare 6

NetWare 6 includes iManager. In order to install the Policy and Distribution Services plug-in to iManager, you must use iManager 1.2, which is included on the ZENworks for Servers Companion CD.

IMPORTANT:  If you are using any of the Novell product plug-ins to iManager that were installed with NetWare 6, search the Knowledgebase at Novell Technical Services^SM for TID 2963651for instructions.

If you are not using any of the Novell product plug-ins to iManager that were installed with NetWare 6, follow the instructions below to install iManager 1.2 for use with the Policy and Distribution Services plug-in:

1. Edit the TOMCAT33.NCF file in the SYS:\TOMCAT\33\BIN directory:

   1. Scroll down to the last line of the file.

   2. Remove the following string:

      -f sys:/tomcat/33/conf/nwserver.xml

      IMPORTANT:  Be sure to leave the %1 at the end of the line.

   3. Save and exit the TOMCAT33.NCF file.

2. Edit the NWAPPS-EMFRAME.XML file in the SYS:\TOMCAT\33\CONF directory:

   1. Change:

      docBase="/webapps/eMFrame" 

      to:

      docBase="webapps/eMFrame" 

      That is, remove the slash (/) in front of WEBAPPS.

   2. Save and exit the NWAPPS-EMFRAME.XML file.

3. Stop Tomcat.

4. Rename or delete the SYS:\WEBAPPS directory.

5. From the ZENworks for Servers Companion CD:

   1. Copy the EMFRAME.WAR file from the EMFRAME subdirectory on the CD to the SYS:\TOMCAT\33\WEBAPPS subdirectory on the NetWare 6 server.

   2. Copy the JCLNT.NLM and JCLNTR.NLM files from the EMFRAME subdirectory on the CD to the SYS:\SYSTEM directory on the NetWare 6 server.

6. Start Tomcat.

   Tomcat then explodes the EMFRAME.WAR file into a new EMFRAME subdirectory under the SYS:\TOMCAT\33\WEBAPPS subdirectory.

7. To test the integration between iManager and Tomcat, display the following URL in your browser:

   http://server:8080/eMFrame

   where server is the IP address or DNS host name of the NetWare 6 server where you installed iManager. Port number 8080 is the Tomcat default.

   You should see a listing of the files in the eMFrame directory.

   If the listing does not appear, check how you typed the URL. Make sure that you typed eMFrame exactly as shown in the example; it is case sensitive. Also make sure that Tomcat is running without errors.

8. Continue with Configuring Tomcat and iManager to Meet Special Network Needs

Installing the iManager Files on Windows

To enable iManager functionality on a Windows server, you must add a customized file to your Tomcat installation:

To add the customized file:

1. Stop Tomcat.

2. From the ZENworks for Servers Companion CD:

   1. Copy the EMFRAME.WAR file from the EMFRAME subdirectory on the CD to the Tomcat WEBAPPS subdirectory on your Windows server.

   2. Copy the JCLIENT.DLL file from the EMFRAME subdirectory on the CD to the C:\WINNT\SYSTEM32 subdirectory on the Windows server.

3. Start Tomcat.

   Tomcat then explodes the EMFRAME.WAR file into a new EMFRAME subdirectory under the Tomcat WEBAPPS subdirectory.

4. To test the integration between iManager and Tomcat, display the following URL in your browser:

   http://server:8080/eMFrame

   where server is the IP address or DNS host name of the Windows server where you installed iManager. Port number 8080 is the Tomcat default.

   You should see a listing of the files in the eMFrame directory.

   If the listing does not appear, check how you typed the URL. Make sure that you typed eMFrame exactly as shown in the example; it is case sensitive. Also make sure that Tomcat is running without errors.

5. Continue with Configuring Tomcat and iManager to Meet Special Network Needs

Configuring Tomcat and iManager to Meet Special Network Needs

The following sections help you with specialized configuration needs:

• Allowing iManager Access across Your Firewall
• Limiting iManager Access to Specific Trees

If these needs do not exist on your network, return to and finish Meeting iManager Requirements .

Allowing iManager Access across Your Firewall

If you need to access iManager from outside your firewall, you have three alternatives:

• Modify your firewall to allow access through port 8080, which is the default Tomcat port number.
• Integrate Tomcat into a Web server, such as Apache, that uses port 80 to provide access across a firewall.
• Reconfigure Tomcat to use port 80.

To change the port number used by Tomcat:

1. Edit the SERVER.XML file in the Tomcat CONF subdirectory.

2. Change the following line:

   <Http10Connector port = "8080" ... >

   to

   <Http10Connector port = "80" ... >

3. Save the SERVER.XML file.

4. Stop Tomcat > start Tomcat.

   The new port number is now in effect.

5. Continue with Limiting iManager Access to Specific Trees for tight XMLRPC security.

   or

   Return to and finish Meeting iManager Requirements .

Limiting iManager Access to Specific Trees

To provide the tightest XMLRPC security, you can provide a list of trees where access from iManager will be permitted. For more information about using XMLRPC security with Policy and Distribution Services, see Security in Policy and Distribution Services in Policy and Distribution Services in the Administration guide.

To limit the accessible trees:

1. Edit the EMFRAME.CFG file in the Tomcat WEBAPPS\EMFRAME\WEB-INF subdirectory.

2. Change the following line:

   Provider.eMFrame.Authentication.Tree.mode=initial

   to

   Provider.eMFrame.Authentication.Tree.mode=constrain

3. Add a line for each tree that you want to be accessible from iManager, using the following format:

   Provider.eMFrame.Authentication.Tree.n.id=tree

   where n is an incrementing number starting with zero (0) and tree can be either a tree name or the IP address of a server where a replica of the tree is available.

   For example:

   Provider.eMFrame.Authentication.Tree.0.id=CORP-TREE
Provider.eMFrame.Authentication.Tree.1.id=123.45.67.89

4. Save the EMFRAME.CFG file.

5. Stop Tomcat > start Tomcat.

   Access to trees from iManager is now constrained to only those trees you have listed in the EMFRAME.CFG file.

6. Return to and finish Meeting iManager Requirements .