During the installation of NetWare 6 as a departmental administrator (an admin user with full rights to its container, but no rights at [root]) two eMFrame errors are produced.  These errors are evidence that iManager and RBS are not being installed and configured properly due to a bug in the installation script that is requiring more rights than departmental administrators have.

This document was written to walk you through the process of restoring iManager and RBS to its default configuration on your NetWare 6 servers.

There are two parts to this.
--WebAdmin/iManager interface
--RBS Collection

Part 1 - WebAdmin/iManager interface

We need to add the appropriate lines to the configuration files for the Apache web server and Tomcat application server so that we can run iManager and access through the WebAdmin interface (https://(servers_ip):2200 by default.)  Listed below are the files to edit and lines to add to them.

-Edit file sys:/apache/conf/adminserv.conf

Add these lines under the section of 'VirtualHost (YOURURL):2200':

Redirect /iManager/ https://(servers_ip):2200/eMFrame/iManager.html
Redirect /iManager https://(servers_ip):2200/eMFrame/iManager.html
Include "SYS:/webapps/eMFrame/WEB-INF/eMFrame-apache.conf"

Replace (servers_ip) with your server's IP address.

click here to see a sample file.

-Edit file sys:/webapps/webadmin/servers.xml

Add these lines to the bottom of the file, just above the </NovellWebMan:ServiceSelector> tag:

<NovellWebMan:Service
id='eMFrame'
title='eDirectory&amp;#8482; iManager'>
<NovellWebMan:ServiceInstance
AdminUrl='/eMFrame/iManager.html'>
SERVERNAME
</NovellWebMan:ServiceInstance>
</NovellWebMan:Service>

Replace SERVERNAME with your server's name.

The text is provided here to facilitate copy and paste, but it loses its formatting.  After you add the text to the file, change the format of it to look like the following:

click here to see a sample file.  Some browsers may alter the look of this file because it contains XML.  In these cases, open it with notepad or another text editor.

-Edit file sys:/tomcat/33/bin/tomcat33.ncf

Add this line after the last 'envset' line:

envset TOMCAT_CLASSPATH=$TOMCAT_CLASSPATH;SYS:\java\lib\jclient.jar

click here to see a sample file.

-Reboot your server

At this point, WebAdmin displays the iManager option, and clicking this option will present you with the iManager login.  You should be able to successfully login using your department admin user ID.  If this is not the first NetWare 6 server in this container, you should already have an RBS collection and this server will be able to use it.  If this is the case, you can skip the remainder of this document.  If this is the first NetWare 6 server in this container, you will see on the left menu that no roles or tasks have been assigned to this user.  Which brings us to Part 2. 

Part 2 -RBS Collection

Now that you are logged into iManager, we need to create the RBS Collection, install the Plug-Ins into that collection, and make user and scope assignments to those roles.

-Create the RBS Collection

Click on the Configure button in the toolbar (looks like a person behind a desk.)
Click on Role Based Services Setup menu item on the left and then Create rbsCollection below that.
In the Container: box, enter the servers' context.  Or use the magnifying glass icon to browse to it.
Click OK to create the collection, and OK again to acknowledge it.

-Install the Plug-ins

Click the Install Plug-in menu item on the left.  This will show a list of four available plug-ins.
Click on the first Plug-in in the list to select it and then fill in the Collection Container field with the name and context of your RBS Collection, or click the magnifying glass icon to search or browse for it.  Be sure you choose the Role Based Service container you just created, and not a one elsewhere in the tree.
Click OK to install the Plug-in, and OK again to acknowledge it.
Repeat these steps for each of the available Plug-ins.

-Make user and scope assignments

Click the Role Management menu item on the left and ten choose Modify Role below that.
You will see five roles listed, each having a Tasks icon and Members Icon to the left of them.
For each role, click the members icon to show the Modify Members page.
In the Name field, enter your container admin ID, including context. (ex. admin.test.umich)
In the Scope field, enter your container name, including context. (ex. test.umich)
Click the Add button.
Note:  If you used the magnifying glass icon to search for your admin object, it will add it to the list below with a Scope of No Scope.  You will need to make sure the box to the left is checked and click the Add Scope button above it.  this will allow you to browse your container object and select it as the scope.
Once the information is correct, click OK to add the member and OK again to acknowledge it.
Repeat these steps for each of the roles.

-Verify all is correct

Close all instances of your browser.
Launch the browser and log into iManager.  Verify that you have all 5 roles listed in the left hand menu.  This is the default configuration of iManager and RBS.  Once you know it is working, you can customize it to your liking. 

To offer constructive criticism, or provide other feedback about our site, click here.