Novell is now a part of Micro Focus

iManager Configuration - Part 2

Novell Cool Solutions: Feature

Digg This - Slashdot This

Posted: 2 Nov 2005

Object Creation List

The Object Creation List contains the list of object classes available to create from the eDirectory Administration > Create Object task in iManager. The classes are stored in various XML files on the file system of the Web server. If a new Class definition is added to eDirectory, it must be added to this list in order to be available from the Create Object task in iManager. You may also delete Class names from this list.

Adding Object Classes

To add Object Classes to the list,
  1. In iManager, select the Configure View.
  2. Select Object Creation List > Add Object Class To Creation List.
  3. Select an object class from the Available object class list.
  4. Click Next.

Deleting Object Classes

Note: There is no confirm for the delete operation, and there is no way to reset the list to default values. To delete object classes from the list,
  1. In iManager, select the Configure View.
  2. Select Object Creation List > Delete Object Class From Creation List.
  3. Select an object class from the Available object classes for the creation list.
  4. Click Delete.


Preferences are user-specific for the currently logged-in iManager user, and they are unique per login DN and tree. Configuration is done through the Preferences view.

Preferences are stored on the file system of the iManager Web Server; they are only for this installation of iManager and are not automatically updated between iManager servers. Some preferences may require re-login in to take effect.

The Preferences screen is shown below.

Figure 1 - Preferences screen

Manage Favorites

Setting this preference displays the tasks you perform most frequently on the Favorites View. It shows all tasks according to what you have been assigned in RBS. You can manually sort the order in which the tasks will appear, and you can choose to make Favorites your initial view after login.

Object Selector

You can set your Object Selector preferences for the following features. These are default values when no specific values are specified by the plug-in.

  • Window Size - Window width, Window height, and left column width measured in pixels
  • User-Specified Defaults - Startup Mode (Browse or Search), Results per Page (Single and Multiple-select Modes), Starting Context (Last used or specific), and Search on Startup (Apply button or Automatic)

Object View

You can set your Object View preferences for the following features:

  • Column Width (Measured in pixels)
  • Startup Mode (Browse or Search)
  • Selection Mode (Single or Multiple)
  • Results per Page (Single-select and Multiple Select Modes)
  • Starting Context (Last used context or specific context)
  • Search on Startup (Apply button or Automatic)

Set Initial View

The initial view that you select determines what will appear after you log in to iManager. This is the Preference that is set from Manage Favorites > Make favorites my initial view option. The default is the Roles and Tasks view.


Select the display language you want for the iManager text. This affects the current iManager browser session only. It is not saved anywhere or across any session.

  • German
  • English
  • Spanish
  • French
  • Italian
  • Japanese
  • Portuguese
  • Russian
  • Polish

Tips and Tricks

Tip 1: Create custom plug-in pages

In the Plug-in Studio you can create custom plug-in pages by assigning access rights through RBS. Attributes can be defined on the page and assigned to categories.

Note that plug-ins do not synchronize between iManager instances, and the plug-ins must be installed separately on all iManager installations. Also, installing NPM?s in iManager may not give you visual indication that the NPM is installing. Please wait for the confirmation summary.

Each product group is responsible for releasing their plug-ins on the download page: manager&families=2611

Also, watch for Plug-in updates here:

Figure 2 - Plug-in updates

Tip 2: Enable browser pop-ups

Browser pop-ups must be allowed for full iManager functionality.

Tip 3: Acquire a valid certificate

On all platforms except NetWare, if iManager installed Apache, Apache uses a temporary self-signed cert that expires in one year. Be sure to replace the temporary certificate with a valid certificate generated by a trusted Certificate Authority.

Tip 4: Watch for 2.0.2 vs 2.5 versions of a plug-in

An example of this would be Password Management.

Tip 5: Use the "Known URL" feature

The Known URL feature helps you automate iManager tasks. It hides the authentication page and lets you jump directly to the specified iManager task This is very helpful with common tasks such as Set Password.

To use the Known URL feature,

1. Locate the URL for the task in question.

2. Locate the taskID in the URL (base.SetPassword in this case).

3. Add the taskID into the URL example below:
4. Add credentials to the end of the URL: &username=&password=<pwd>&tree=<ipaddress>

Here is a sample URL to set the user password:

Tip 6: Use the forceMaster switch

As in ConsoleOne, modifications to eDirectory objects through iManager can happen on any writeable replica. To force iManager to write to the Master replica, enable the Authenticate.forceMaster option in the $TOMCAT_HOME\webapps\nps\WEBINF\config.xml file. Then restart Tomcat for changes to take effect. For example:

<![CDATA[ Authenticate.forceMaster ]]>
<![CDATA[ true ]]> 

If you don't want to enable the ForceMaster option for all users, simply add the &forceMaster=true parameter to the end of URL, reload the login page, and then log in to iManager. Note: This setting affects only NDAP connections using the NDSNameSpace.

Tip 7: Forcing Unrestricted Mode

(For details on this feature, see TID 10095953.) With iManager 2.0.2, you could switch between Collection Owner and Unrestricted Mode without deleting the RBS collection by deleting the bhCollectionList attribute on the PCO object. In iManager 2.5, the setting is now in the config.xml file.

To force Unrestricted Mode, go to the very bottom of the config.xml file, before the </config> ending tag, and enter the following:


Tip 8: Logging with Mobile iManager

The log file is located at imanager/bin/iManager.log. This is considered the Standard Output device in Mobile iManager. Increasing the logging level will increase the information generated in this log file. Every time you launch Mobile iManager, this log file is cleared.

Tip 9: Deleting a Collection

With iManager 2.0.2, deleting a collection would automatically return you to Unrestricted Mode. With iManager 2.5, there is one extra step.

After deleting a 2.x collection, if you log into iManager, no roles or tasks will be displayed, and the authentication mode will be Assigned Access. You must remove the tree name from the RBS Tree List, log out and then log in again.

To remove the tree name, click the minus (-) button as shown in the screen below.

Figure 3 - Removing the tree name

Tip 10: Uninstalling a plug-in module

The iManager plug-in uninstall uses InstallAnywhere. To successfully remove a plug-in, follow these steps:

  1. Remove the RBS module and tasks associated with the plug-in.
  2. Uninstall the plug-in through the Installed Novell Plug-in Modules task. When you uninstall an NPM, the file is moved to the /nps/packages/deleted directory.
  3. Restart Tomcat.
Important: Do not delete the RBS module for the given plug-in if there are still other iManager servers in the tree using that collection object.

Tip 11: Manually removing a plug-in module

If any of the files on disk have been manually removed or the uninstall registry has become corrupted, the uninstall may fail. To manually uninstall a plug-in, you must remove all files laid down by the plug-in installer.

Open the NPM file in a zip utility and look at the directory structure. InstallAnywhere uses symbolic links for directory structures:

? currentwebapp = TOMCAT_HOME\webapps 
? compiledjsps = TOMCAT_HOME\work\Standalone\localhost
MANIFEST.MF file is stored in \webapps\nps\WEB-INF\modules\\META-INF directory. Note: You may need to delete the files under the \webapps\nps\UninstallerData directory as well for the given plug-in.

Tip 12: Co-existence of iManager 2.0.2 and 2.5 in the same tree

(For details, read the Upgrading from iManager 2.0.x section in the Installation Guide.)

If you use iManager 2.5 to access a tree that has an RBS Collection from iManager 2.0.2, you might not see all of the roles and tasks that should display. The reason is that the RBS modules that contain the tasks need to be updated to 2.5. You do this in Configure > Role Based Services > RBS Configuration.

The main table of the RBS Configuration task shows modules that are out-of-date. These can then be updated by selecting the link in the Out-Of-Date column. Important: If you use both iManager 2.0.2 and 2.5 in the same eDirectory tree, it's recommended that you update all collections to iManager 2.5. Then plug-ins will be visible in both iManager 2.0.2 and 2.5.

Tip 13: Upgrading from 2.0.2 to 2.5

If you are installing iManager 2.5 on a 2.0.2 server, the nps directory is backed up to TOMCAT_HOME. All custom content is also backed up. Plug-ins from the old 2.0.2 directory are compared to those in the 2.5 directory and are copied into the 2.5 directory if they are newer or don't exist.

Most 2.0.2 plug-ins are fully compatible with iManager 2.5 except for IDM plug-ins (DirXML? management and Universal Password), NSS Management and Nsure Audit plug-ins. Upgraded 2.5 server may have more modules than a freshly installed 2.5 server.

Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions.

© Copyright Micro Focus or one of its affiliates