This Readme contains the following sections:
iManager 2.7.4 includes the following product enhancement:
With the release of iManager 2.7.4 Patch 4, you can now use Firefox 9.0.1 for accessing iManager.
With the release of iManager 2.7.4 FTF 3, you can now use Firefox 4.0.1 and Internet Explorer 9 Web browsers for accessing iManager.
NOTE:iManager 2.7.4 is not supported on NetWare.
iManager support packs do not make a backup of the files that are replaced. The only way to roll back to a previous state is to back up all files before applying the support pack and then manually restore the backed up files.
Also, iManager support packs must be installed on all iManager servers in your environment. Support packs do not automatically replicate other iManager servers in your tree.
After you install the iManager support pack, iManager is non-functional until you restart Tomcat.
To download and install the iManager 2.7.4 support pack:
Download iman274.npm file from the Novell Download Web site to your local machine.
Log in to iManager.
Click .
Click , browse to and select the iman274.npm file, then click .
Verify that the module is iman274.npm and the description reads iManager 2.7.4.
Select the check box next to the iman274.npm field patch file and click .
The installation takes a few minutes.
Internet Explorer might append a .zip extension to the .npm when it is downloaded or it might actually remove the .npm extension, and replace it with .zip. The extension must be .npm. Otherwise, the installation does not upload the file.
Click , then restart Tomcat.
Tomcat sometimes requires several minutes to fully initialize. Wait a few minutes before trying to log into iManager after restarting Tomcat.
Verify that the new support pack has been installed.
Log in to iManager, then check whether the home page displays the 2..7.4 version.
Check the log file located in webapps/nps/WEB-INF/changelog.
Click in the upperleft corner of the iManager application window to view the iManager information page.
Log in to iManager.
Click .
Select the check box next to the support pack plug-in and click .
The installation takes a few minutes.
Click , then restart Tomcat.
Tomcat sometimes requires several minutes to fully initialize. Wait a few minutes before trying to log into iManager after restarting Tomcat.
NOTE:When you install iManager plug-ins, sometimes either the installation hangs or the plug-ins are not properly installed. To troubleshoot the issue, see iManager Plug-in Installation Hangs or Plug-ins Are Not Properly Installed
in the Novell iManager 2.7 Installation Guide.
The following issues are resolved in the iManager 2.7.4 Patch 4 release:
When logging in with the treename, iManager now first searches the local eDirectory server for object resolution.
All eDirectory objects with a slash (/) in the DN are now displayed in the list.
The time taken to fetch the attributes associated with an object when the user clicks the tab in task is now reduced.
The time taken to display the page of the NCP server object is now reduced.
iManager’s login performance has been improved by reducing the time taken to login.
The contextless login feature in iManager now works with the treename.
The following issues exist in iManager 2.7:
For a successful installation,
Manually install the dependant libraries from the XFree86-libs.rpm.
For a 64-bit RHEL: Install the following libraries:
compat-libstdc++-33-3.2.3-47.3.i386.rpm
compat-libstdc++-33-3.2.3-47.3.x86_64.rpm
libstdc++44-32bit-4.4.0_20090212-2.1.x86_64.rpm
For a 32-bit RHEL: Install the following library:
compat-libstdc++-33-3.2.3-47.3.i386.rpm
Invoke iManager installer.
You cannot log in to an iManager console on a SUSE Linux Enterprise Server (SLES) 11 machine. If you attempt to log in, an error message is displayed.
To work around this issue, install the libstdc++-43 and libstdc++-33 packages on SLES 11 (32-bit) and the libstdc++-43-32bit and libstdc++-33-32bit packages on SLES 11 (64-bit) machines.
An unexpected error is detected on iManager 2.7 Workstation with JRE V 1.6.0_18 and Tomcat V 5.5.28. An error report is created at /home/imanager/bin/hs_err_pid28757.log.
This issue is observed on the following platforms:
SUSE Linux Enterprise Desktop (SLED)10 SP2 (32-bit and 64-bit)
SLED 10 SP3 (32-bit and 64-bit)
SLED 11 (32-bit and 64-bit)
SLED 11 SP1 (32-bit and 64-bit)
The issue has no impact on the iManager functionality
If you install iManager 2.7 SP4 on the iManager 2.7 standalone version with JRE V 1.6.0_18 and Tomcat V 5.5.28 and restart the Tomcat server, an unexpected error is detected by the Java Runtime Environment. The error report is created at /var/opt/novell/novlwww/hs_err_pid24458.log.
This issue is observed on the following platforms:
SLES 10 SP3 (32-bit and 64-bit)
SLES 11 (32-bit and 64-bit)
SLES 11 SP1 (32-bit and 64-bit)
The issue has no impact on the iManager functionality
When you attempt to install the latest blind revision of iManager 2.7 on a SLES 9 machine, the installation option to install iManager is not displayed.
To work around this issue:
Rename the /etc/SuSE-release file.
For example:
etc/sles9
Back up this renamed file.
Download iManager from the Novell Download Web site and install it.
Ensure that the compat-libstdc++ libraries are installed.
IMPORTANT:If you do not install the compat-libstdc++ libraries, the AdminNameSpace Error can occur when you log in to iManager.
(Conditional) If the C++ libraries are not installed, install compat-libstdc++-lsb-4.0.2_20050901-0.4.i586.rpm.
Change the file you renamed in Step 1.
When you work with iManager through the Internet Explorer 8 browser and you click the tab, a security warning message appears asking Do you want to view only the webpage content that was delivered securely. This message comes from Internet Explorer.
To block this message from appearing, perform the following steps in the Internet Explorer 8 browser:
Click > .
The Internet Options window is displayed.
Click the tab. By default, the Internet option is selected.
Click .
The Security Settings window is displayed.
In the section, select the option for .
Click .
The following issues exist in the new tab of the Object View:
In the Object View’s tab, the effects of container actions are not immediately reflected in the Navigation frame’s object list. For example, adding a container or changing an existing container’s name, is not reflected in the Navigation frame until you manually refresh the view by closing the Tree view and then re-opening it.
The Tree view does not currently save its state, including the current position within the tree, when switching between the Tree view and the tabs.
If you inadvertently specify an invalid user name or scope when creating RBS Member Associations, iManager displays the following error when you try to save the changes:
The system encountered an unknown error. Please contact Novell Support.
This error prevents a successful save operation for any valid data that you might have entered. To avoid this problem, use the Object Selector to locate valid objects and scopes when configuring iManager RBS.
You might encounter the following error while authenticating iManager on a server with SLES 9 SP3 or later:
Unable to create AdminNamespace. java.lang.NoClassDefFoundError when authenticating on SLES 9.
To work around this issue, install compat-libstdc++-33-3.2.3-61.i386.rpm before installing iManager 2.7.
Because of changes to class structure and organization, iManager plug-ins must be recompiled to work with iManager 2.7. The iManager 2.7 Web site contains all currently available plug-ins, and the site is regularly updated with additional plug-ins when they are available. If you add an older plug-in by using the link, it does not display an error even though the plug-in is not added. You can view specific error information in the debug log.
Similarly, the Open Enterprise Server (OES) 2 download includes the currently available iManager 2.7 plug-ins.
NOTE:iManager 2.7 does not allow the user to install old plug-ins that iManager 2.6 supported.
Be aware of the following login-related issues with iManager 2.7:
The iChain Single Sign-On functionality (including Forward authentication, OLAC, and Form Fill) does not work in a multi-tree environment. iManager 2.7 requires a user name, password, and tree name for login, and iChain requires only the user name and password.
Form Fill from iChain also fails because the button in the iManager toolbar directs you back to the initial login form. When Form Fill is active, you are simply logged back in to iManager.
In a single-server environment, it is possible to use the iManager default settings and iChain works correctly.
If there are problems with the display of the characters during the installation, you might need to change the system's character encoding to UTF-8.
Installing remotely through an SSH client might also require UTF-8 character encoding on the client in order to display characters properly.
For example, set the system variable LC_ALL=de_DE.utf8, then try running the install again.
On Windows servers, if you want to install eDirectory and iManager on the same physical machine, you must install eDirectory before you install iManager. This allows eDirectory to perform the initial system configuration as required.
On Windows Server 2000 and Windows Server 2003 with IIS 5 or 6, installing Groupwise 7.0 WebAccess to IIS automatically installs Tomcat 5.5.
As the iManager installation begins, the iManager installer program detects that IIS and Tomcat are available for use. The installer reports the inability to stop the iisadmin service. Near the end of the install, the installer reports the inability to start Tomcat.
After the install is completed, GroupWise WebAccess still works, but iManager does not (HTTP 404: Page not found).
To work around this issue, do not install iManager and GroupWise on the same Windows server.
When you access different versions of iManager with the same browser, you might see a blank screen or missing roles and tasks. Resolve this problem by clearing the browser's stored cookies and cache and restarting the browser.
When the Time Out setting for dynamic groups is set to a value that can be exceeded, this occurs, the following message appears: Unknown meaning for error number - 6016; Please call a Novell provider, but the value is saved. When you access dynamic groups, another error message appears: The system encountered an unknown error. Please contact Novell support.
The workaround is to give the Time Out setting an adequate and reasonable value.
iManager does not escape special characters automatically. Using a special character in an object name causes an error unless you manually escape the character. More information about special characters is available in the iManager documentation.
Plug-In Studio can't find RBS Collections that have special characters in their names, so attempting to edit a plug-in that has been previously installed into an RBS Collection with special characters in its name causes the install to fail.
Creating a property book and using special characters in its name might cause a DNS Error 603 message. For more information about naming a Property Book, see “Creating a New Property Book” section in the iManager documentation.
To create a plug-in ID that includes extended characters, create the plug-in with standard characters, then use Advanced Properties to change the plug-in display name after it has been created.
Two instances in Firefox and Internet Explorer 8 tabbed views do not maintain connections to two different trees. Internet Explorer 6 maintains one session per instance, while Firefox uses the same session for all instances that use the same profile.
This difference in Web browser behavior gives the appearance that Firefox cannot support two different sessions and that connection information is crossing over. iManager can maintain a connection to two different trees at the same time in the Firefox browser, but only if each instance is using a different profile.
To work in different sessions simultaneously, use Firefox's Profile Manager to modify your profile. In Firefox 2.0 and 3.0, you can use the -no-remote option when launching Firefox to run multiple profiles simultaneously.
When you close iManager Workstation or SDK, you might encounter a javaw.exe application error. The error is benign and does not indicate any system problems or instabilities. You can safely close the error message box and continue working normally.
Using ASCII control characters in a login script might cause an Unhandled Exception Error in iManager. For this reason, Novell recommends using only the standard ASCII character set when creating login scripts.
iManager leverages Macrovision InstallAnywhere for its installation routine. Because of this, some of the language translation for the installation routine is provided by Macrovision. Novell has encountered a few errors in these Macrovision translations that it cannot access to correct. For example, when you are prompted to select a language for the installation, the language selection “Slovak” is translated to “Anglictina”, which means English rather than Slovak.
Novell is working with Macrovision to get these translation errors corrected.
The iManager Language Preferences setting does not change the language of eDirectory error messages, even though the language of the iManager Web interface is changed.
To work around this issue, change the operating system default language on the eDirectory server that iManager is using.
Novell iManager might not display the links or the third row of options in the Property Book, if the window size is minimized.
To work around this issue, expand the window or use a resolution greater than 1024 x 768.
When you try to access iManager from a browser, the Login page sometimes fails to load, and displays the following error message:
exception java.lang.NullPointerException com.novell.emframe.fw.servlet.AuthenticatorServlet.service(AuthenticatorServlet.java:334) javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
The browser cookies might be corrupted.
To work around the issue, clear the browser cookies, then try to access iManager.
You might encounter an error indicating the above Unable to CreatedminNamespace.java.lang.NoClassDefFoundError when authenticating to eDirectory with iManager 2.7 Workstation or SDK on SLED 10. This indicates a problem while updating NICI.
NICI 2.7.0 is installed with SLED 10 and the Open Desktop Edition add-on (ODE). iManager 2.7 requires NICI 2.7.3 and prompts you to install when you run iManager 2.7 Workstation or SDK for the first time. The issue happens because NICI 2.7.0 is not successfully upgraded to NICI 2.7.3. During the update, you get a message that priming NICI was not successful.
To work around the issue, remove both versions of NICI on the system, ignoring any dependencies. For example, the ODE add-on itself has a dependency on NICI. Re-install the NICI 2.7.3 that you got with iManager 2.7 Workstation. Before you install NICI 2.7.3, make sure that you delete the /var/novell/nici directory.
When you are doing RBS configuration in Internet Explorer, if you try to open a Data Table Element in a new window or a new tab, you cannot get the desired result. Instead, you should directly click the links.
After installing a plug-in such as, a service pack, if you immediately click s, a blank page appears. You should restart Tomcat:
For Windows: Restart Tomcat services from
For Linux: /etc/init.d/novell-tomcat5 restart
Internet Explorer 6.0 does not display tooltips for the items in a list, so the iManager mvStringEditor tag does not show tooltips for the values it contains. The issue is fixed in Internet Explorer 7.0 or later and it shows tooltips for the values in the iManager mvStringEditor tag.
If you are an Admin and you want to allow all the eDirectory users to access iManager, you should add (case sensitive) to the list in the Configure page.
If you add an invalid user such as to the list, you cannot modify the Configure page the next time you visit the page. A Current logged in user is not authorized to configure iManager message is displayed.
To work around the issue, open the Configiman.properties file, then modify the Alluser line to AllUser=true.
After authentication on iManager 2.7 workstation, the following Security Warning message is displayed:
The information you have entered is to be sent over an unencrypted connection and could easily be read by a third party. Are you sure you want to continue sending this information?
The message is also displayed many times when you go to the tree view, and the other parts of iManager.
To work around the issue:
Windows: Open the security-prefs.js file from <imanager workstation folder>/bin/windows/mozilla/greprefs.
or
Linux: Open the security-prefs.js file from <imanager workstation folder>/bin/linux/mozilla/greprefs.
Modify the following settings from true to false:
New downloads of Linux workstation have these flags set to false, by default.
iManager Workstation might not display error messages, pop-ups, and load pages like Tree View, Object Browse, and Create Objects. This happens when the XULRunner browser cache contains old data for the previous build of iManager 2.7 workstation.
As a workaround, you must manually clear the data from browser cache:
Exit iManager.
Go to:
Windows: C:\Users\<username>\AppData\<Profile>\Mozilla\eclipse\Cache (Windows XP)
C:\Users\<username>\AppData\Roaming\Mozilla\eclipse\Cache (Windows 7/Vista)
Linux: /home/<username>/.mozilla/eclipse/Cache
Delete the data in the Cache directory.
Restart iManager.
The Object Selector icons in the Group Member and Group Membership property book pages allow you to select the objects that have nestedGroupAux auxiliary class in their attributes. However, the design for adding such objects to the history requires nestedGroupAux to be an object type. Therefore, these objects are not added to the history.
You can make a nested grou into a dynamic group and vice versa by using the Object Extension task under the Schema role. However, as long as eDirectory allows the auxiliary classes to be added to the objects by using the Object Extension task, iManager does not check them. Therefore, if you make a group nested and dynamic, it might not properly function.
Changes to the page order of a Property Book through have higher precedence than reordering the for the same Property Book while modifying the through . This is because the latter action modifies the Property Book object in the eDirectory, but the former action is specific to a particular Property Book on a particular iManager server.
The user cannot select valued or unvalued attributes by using keyboard.
To work around the issue, in Firefox 3, press Scroll Lock + Up/Down arrow or Shift + Ctrl + Up/Down arrow.
In Internet Explorer 7, press Scroll Lock + Up/Down arrow.
When you log in as Administrator to iManager that is connected to eDirectory where a DSFW (Domain Service for Windows) server is installed, and try to modify the objects under a container such as , a few objects of type Users, Configuration, Computers appear as undefined. A question mark (?) is displayed next to the object types.
A DSFW administrator cannot configure RBS in iManager while modifying the ACL value. This is because the rights for the DSFW administrator are limited to the supervisor rights on the domain and subdomains that the administrator manages and do not include all rights as the Tree administrator.
After you upgrade iManager to 2.7.4, the custom plug-ins that are installed prior to 2.7.4 are shown as under column in the Plug-in Studio page.
As a workaround, select the plug-in, then click > . The plug-ins are installed with the features of iManager 2.7.4.
After you upgrade iManager to 2.7.4, newly added Property Book pages such as Nested Settings, Group Member, and Group Memberships do not appear while modifying a group by using the Modify Group task.
As a workaround, you should manually assign the pages to the Modify Group property book for the RBS Collection being used, or create a new RBS Collection.
To manually assign the pages to the Modify Group property book:
Click the tab.
Click > . The RBS Configuration page is displayed.
Click the existing RBS Collection. The Collection: <RBS Collection> page is displayed.
Click the tab, select the Modify Group, then click > . The Edit Page List page is displayed.
From the Available Pages list, select , , and , click the right-arrow so that the selected items are moved to the Assigned Pages list, then click .
The message The property book was successfully modified is displayed.
To create a new RBS Collection:
Click the tab.
Click > . The RBS Configuration page is displayed.
Click > to start the RBS Configuration Wizard.
This helps you to create a new RBS Collection with the newly added pages.
When the master or parent server is down, iManager users cannot find the tree root because the information of the tree root is available only with the master/parent server. Because the users cannot find the tree root, they cannot log in to the child server that has the replica.
When you uninstall iManager plug-ins on Windows Vista, the uninstallation does not work properly. Even though you get an uninstallation successful message, the plug-ins are still listed as installed in the list.
The problem occurs because .com.zerog.registry.xml file that is required for uninstallation might be hidden. You should make the file available for uninstallation by making it visible:
Click . The My Computer page is displayed.
Click . The Folder Options dialog box is displayed.
Click .
Under , select .
Click
When you install iManager (using any language) in a Portuguese-Brazilian locale, if you set the LANG environment variable to pt_BR.UTF-8, pt_BR.utf8, or pt_BR, the installer corrupts the gettingstarted.html file of the particular language.
As a workaround, before starting the iManager installation, set the LANG environment variable to pt_PT.UTF-8 by entering the following command at the terminal:
export LANG=pt_PT.UTF-8
If you have installed a plug-in through iManager 2.7.2 or earlier and if you try to uninstall this plug-in through an iManager 2.7.3 or later version, the plug-in is not uninstalled properly.
In this case, you must manually uninstall the plug-in by removing the following directories:
\<Tomcat>\work\Catalina\localhost\nps\org\apache\jsp\portal\modules\<plugin_name_dir>
\<TOMCAT>\webapps\nps\portal\modules\<plugin_name_dir>
\<TOMCAT>\webapps\nps\WEB-INF\modules\<plugin_name_dir> (The MANIFEST.MF file is present in this directory and must be deleted)
\<TOMCAT>\webapps\nps\WEB-INF\lib\<plugin_jar_file>
\<TOMCAT>\webapps\nps\WEB-INF\classes\com\novell\nps\modules\<plugin_name_dir>
You must also delete the UninstallerData directory for the plug-in that you want to delete. The UninstallerData directory is found in the following path:
Windows: C:\Program Files\Novell\Tomcat\webapps\nps\UninstallerData\Uninstall_<plugin_name>
Linux: /var/opt/novell/tomcat5/webapps/nps/UninstallerData/Uninstall_<plugin_name>
If you try to acces the Novell Certificate Server or Novell Certificate Access tasks through iManager, iManager throws a Java exception error indicatingjava.lang.NullPointerException\n at com.novell.admin.PKI.certificate.eDir.eDirCertificateManagerVariables.getNativeAPIVersion. This is because the Novell Certificate Server Plug-ins for iManager (PKI) have a dependency on the libstdc++-libc6.2-2.so.3 library.
To avoid this error, you must install the following RPMs on the iManager server:
32-bit: compat (compat-2006.1.25-11.2)
64-bit: compat-32bit (compat-32bit-2006.1.25-11.2)
32-bit: compat (compat-2009.1.19-2.1)
64-bit: compat-32bit (compat-32bit-2009.1.19-2.1)
You might encounter the following error while authenticating iManager on a Server with SLES 10 SP3 (64-bit):
Unable to create AdminNamespace. java.lang.NoClassDefFoundError when authenticating on SLES 10 SP3.
To work around the issue, install libstdc++33-32bit-3.3.3-7.8.1 before installing iManager 2.7.
On SLED 11 64-bit, the following error messages appear when you launch iManager Workstation:
Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: cannot open shared object file: No such file or directory
Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
You can ignore these messages and continue using the workstation.
Accented characters are not recognised in iManager plugin and hence are displayed incorrectly.
To workaround this issue, replace the accented character with the unicode escape sequence. For more information about the unicode escape sequence for various characters, see http://www.utf8-chartable.de/unicode-utf8-table.pl
By design, the tab is not available on OES.
To workaround this issue, manually change the cipher levels in the /etc/apache2/vhosts.d/vhost-ssl.conf file, then modify the SSLCipherSuite parameter based on your cipher level support.
For more information on iManager, see the iManager documentation Web site.
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.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2012 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.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.