This readme contains the following sections:
Be aware of the following information as it relates to the iManager 2.7:
iManager 2.7 supports the following server platforms:
NetWare 6.5 Service Pack 7 (NW65SP7)
Red Hat* 4 (both 32-bit and 64-bit)
SLES 9, SLES 10, and SLES 10 SP1 (both 32-bit and 64-bit)
Open Enterprise Server 2
2000 Server SP4
2000 Advanced Server SP4
Server 2003 R2
NOTE:iManager 2.7 does not include Solaris as a supported platform. However, iManager can still manage and work with applications and resources, such as eDirectory, running on the Solaris platform.
Except for the Open Enterprise Server 2 (OES 2) platform (Linux and NetWare), iManager uses only Tomcat 5 for its Web Server requirements. On the OES 2 platform, iManager 2.7 uses both Tomcat 5 and Apache 2.2.3.
Because of this change, on platforms other than OES 2 you must specify the Tomcat port as part of the iManager URL. The default URL to start iManager 2.7 is as follows:
Secure URL: https://<server ip address>:8443/nps/iManager.html
iManager 2.7 on the OES 2 platform, both Linux and NetWare, use the following default iManager URL:
Secure URL: https://<server ip address>/nps/iManager.html
IE 6 (SP1 and later) or 7
Firefox* 1.5.x, or 2.x
IMPORTANT:Although you might be able to access iManager via a Web browser not listed, we do not guarantee full functionality.
iManager 2.7 does not support access through an iChain® server with a path-based multihoming accelerator, and with Remove Sub Path from URL enabled.
iManager Workstation supports the following desktop platforms:
Red Hat Enterprise Linux Work Station 4
SUSE Linux Enterprise Desktop 10 (SLED) and SLED 10 SP1 (both 32-bit and 64-bit)
Windows XP Professional SP2 or later
Windows 2000 Professional SP4 or later
Windows Vista (32-bit only)
iManager 2.7 includes the following product enhancements:
Except for the Open Enterprise Server 2 platform (both Linux and NetWare), iManager 2.7 now requires and installs only Tomcat 5 in support of its Web services. Apache is no longer installed or configured by iManager. However, iManager can co-exist with Apache or IIS if those are properly configured. For more information, consult your Apache or IIS documentation.
On the Open Enterprise Server 2 platform, iManager 2.7 utilizes both Tomcat 5 and Apache.
The iManager tree view approximates functionality available in ConsoleOne's Console View. The left-side navigation frame displays the tree structure of the current directory tree, and lets you navigate that tree structure, expanding and collapsing container objects as necessary. The right-side content frame displays contents and menu items for the object selected in the navigation frame.
iManager 2.7 lets you browse through an eDirectory Volume object into the physical NSS volume. Within the volume structure, you can select File and/or Directory objects.
File system browsing does not support accessing the file system through NCP Server objects or NSS junction point objects.
File system browsing is available from the Object Selector, Object View and Tree View, but is not available in Advanced Browsing mode. Also, file system browsing is not accessible from the Search or Advanced Search panes.
iManager 2.7 now provides access to additional Template object property pages that let you specify Volume space restrictions and specific file system rights assignments for new objects created through the template.
iManager 2.7 lists all the available iManager plug-ins contained in the packages directory/download site by default. You can download and install plug-ins from within iManager by querying the Novell download Web site. The previous versions of iManager listed only the updates to the installed plug-ins modules.
In iManager 2.7 both the Object View and Tree View offer the ability to list a subordinate object count next to each container object in the view.
The following issues exist in the iManager 2.7 environment:
The following issues exist in the new Tree tab of the Object View:
In the Object View’s Tree 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 leaving the Tree view and then re-opening it.
Tree View does not currently save its state, including current position within the tree, when switching between Tree View and the Browse/Search tabs.
If you inadvertently specify an invalid user name or scope when creating RBS Member Associations, when you try to save the changes iManager displays the following error:
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 when authenticating to iManager on a SLES 9 server with SP3 installed:
Unable to create AdminNamespace. java.lang.NoClassDefFoundError" when authenticating on SLES 9.
This indicates that the SLES 9 server isn’t fully patched. To resolve this issue, update the SLES 9 SP3 server with the latest YOU patches.
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 will be regularly updated with additional plug-ins as they become available. If you add an older plug-in using Add Plug-in 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 OES 2 download includes the currently available iManager 2.7 plug-ins.
WARNING:Do not install older plug-ins from a local drive into iManager 2.7. While the plug-in might install, it will not run and can be very difficult to remove.
iManager 2.7 does not automatically redirect to a secure port. You must specify the secure URL if you want a secure connection. iManager 2.7 URLs are listed in Section 2.1, Web Server Support.
If you create a policy when Universal Password is enabled, assign the policy to a user (or a user’s container), and then open the Modify User page for that user and click Restrictions > Set Password, the Set Password link does not open the new Universal Password Set page.
To get full Universal Password functionality, make sure NMAS™ 2.3 or later is present on your server and use the Set Universal Password task.
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 multitree environment. iManager 2.7 requires a username, password, and tree name for login, whereas iChain requires only a username and password.
Form Fill from iChain also fails because the Exit 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 will work correctly.
For the same reasons as iChain SSO, NetIdentity can cause problems with iManager login.
When using iManager 2.7 on a NetWare 6.5 SP3 server that was previously running iManager 2.x and Virtual Office, NetIdentity clients see a NetIdentity login dialog box that only requires a username and password, instead of the iManager login dialog box that requires a username, password, and tree name.
If, during the installation, there are problems with the display of the characters, you might need to change the system's character encoding to UTF-8.
Installing remotely via an ssh client might also require UTF-8 character encoding on the client to display characters properly.
For example, set the system variable LC_ALL=de_DE.utf8, then try running the install again.
If iManager 2.7 is installed before eDirectory 8.7.3, the iManager login might fail and Tomcat might crash. To work around this problem, do the following:
Restart Tomcat (/etc/init.d/novell-tomcat5 restart)
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 2000 and 2003 Server 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).
Workaround: Do not install iManager and GroupWise on the same Windows 2000 or Windows 2003 computer.
This most commonly occurs when accessing different versions of iManager with the same browser. Resolve this problem by clearing the browser's stored cookies and cache and restarting the browser.
When 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.
To workaround this issue, give the Timeout setting an adequate and reasonable value.
iManager does not escape special characters automatically. Using a special character in an object name will cause an error unless you manually escape the character. More information 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 naming it using special characters might cause a DNS Error 603 message. For more information about naming a Property Book, see “Creating a New Property Book” in the iManager documentation.
To create a plug-in ID that includes extended characters, create the plug-in using 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 7 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 can’t 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 different sessions simultaneously, modify your profile using Firefox's Profile Manager. In Firefox 2.0 you can use the -no-remote option when launching Firefox to run multiple profiles simultaneously.
You cannot edit a value in a control such as “Group Membership” or “Security Equal to” in Internet Explorer.
To work around this issue, highlight the value, press the Delete key, then add the correct value.
When closing 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 language of the message strings for Replica Type and Replica State.
To work around this issue, change the operating system default language where the iManager server is running.
The iManager Language Preferences setting does not change the language of eDirectory error messages, even though the language of iManager Web interface is changed.
To work around this issues, change the operating system default language on the eDirectory server that iManager is using.
Novell iManager might not display the links or third row of options in the Property Book, if the window size is minimized.
To work around this issue, expand the window or consider using a resolution greater than 1024 x 768.
When you try to access iManager from a browser, the Login page 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)
There is a possibility of browser cookies being corrupt. To work around this problem, clear the browser cookies and then retry.
During iManager 2.7 installation, you may not be able to change focus to the dialog that asks if you want to install iManager 2.7 plug-ins without using a mouse. This may prevent you to proceed with the install.
If you perform a non-English install of NetWare 6.5 SP 7, iManager 2.6 is displayed as the product in multiple places during the install. Also, the list of installed products will display a product of iManager 2.6 with a version of 2.7.0. Even though iManager 2.6 is displayed as the product, iManager 2.7 is the version that is installed..
This is the result of the iManager 2.0.2 uninstall not removing the line "Include sys:/tomcat/4/conf/nps-Apache.conf" from SYS:\Apache2\conf\httpd.conf. You will also see a Apache2 startup error in SYS:\Apache2\logs\startup.err.
Workaround: You must perform the following:
Remove the line "Include sys:/tomcat/4/conf/nps-Apache.conf" from the bottomof the file.
Save the changes.
Start Apache2, ap2webup.
You might encounter the above error when authenticating to eDirectory with iManager 2.7 Workstation or SDK on SLED 10. This indicates the problem while updating NICI. You may notice a message when you updated NICI that primenici was unsuccessful.
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 is due to NICI 2.7.0 not successfully upgraded to NICI 2.7.3. During the update you will get a message that primenici was not successful. The solution is to remove both versions of NICI on the system, ignoring any dependencies, and re-install the version that came with iManager 2.7 Workstation, NICI 2.7.3. The ODE add-on itself has a dependency on NICI. So remove NICI by telling Software Management to ignore the dependency. Before you install NICI 2.7.3 make sure you delete the /var/novell/nici directory.
For information on iManager 2.7 issues following this release, see Novell iManager 2.x Readme Addendumin the Novell Knowledge Base.
Portions of iManager 2.7 are copyrighted by third-parties. The relevant license agreements for this third-party software are provided below.
Copyright © 1999-2006, The Apache Software Foundation.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Copyright © 2000-2003 Jason Hunter & Brett McLaughlin. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the disclaimer that follows these conditions in the documentation and/or other materials provided with the distribution.
3. The name "JDOM" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact <license AT jdom DOT org>.
4. Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name, without prior written permission from the JDOM Project Management (firstname.lastname@example.org).
In addition, we request (but do not require) that you include in the end-user documentation provided with the redistribution and/or in the software itself an acknowledgement equivalent to the following:
"This product includes software developed by the JDOM Project (http://www.jdom.org/)."
Alternatively, the acknowledgment may be graphical using the logos available at http://www.jdom.org/images/logos.
THIS SOFTWARE IS PROVIDED ``AS IS’’ AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally created by Jason Hunter (email@example.com) and Brett McLaughlin (firstname.lastname@example.org). For more information on the JDOM Project, please see http://www.jdom.org/.
Copyright (c) 1997, 1998 James Clark
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ``Software’’), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL JAMES CLARK BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Except as contained in this notice, the name of James Clark shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from James Clark.
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 © 2010 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.