Documentation and the latest Readme file for iManager 2.6 are available at the iManager 2.6 Web site.
Review the following suppport information before installing iManager 2.6.
The latest information on iManager 2.6 plug-ins is available in iManager 2.6 Plug-In Information in the Novell Knowledge Base.
iManager 2.6 supports installation on the following platforms:
NetWare® 6.5 SP3 and SP4
Open Enterprise Server (NetWare)
Windows*
2000 Advanced Server SP4
2000 Professional SP4
Server 2003
Linux*
Red Hat* Advanced Server 3.0, 4.0
SUSE® Linux Enterprise Server (SLES) 8, 9
Open Enterprise Server (SLES 9) SP1
Solaris*
Solaris 9
Solaris 10
HP-UX*
HP-UX 11i
Tomcat 4.1.30
Tomcat 4.1.29 (HP-UX only)
Apache 2.0.49 for OES Linux
Apache 2.0.52
Internet Information Services (IIS) 5 and 6
IE 6 SP1
Mozilla* 1.7.6
Mozilla Firefox* 1.0.6
eDirectory™ 8.7.3
eDirectory 8.8
Mobile iManager supports installation on the following platforms:
SUSE Linux Professional 9.1, 9.2, 9.3
Red Hat Enterprise Linux Work Station 3, 4
Novell® Linux Desktop (NLD) 9 SP1, SP2
Windows XP Professional SP2
Windows 2000 Professional SP4
iManager 2.6 is backward-compatible with iManager 2.0.2 and 2.5. It can coexist with either iManager 2.0.2 or 2.5, or both, on the same tree.
iManager 2.6 includes the following product enhancements:
The iManager 2.6 install queries a Web site for a list of plug-ins that are compatible with the iManager version and the operating system. The install presents a list of plug-ins that you can select to install, which are then downloaded and installed into the system.
Configure the query list from Configure > iManager Server > Configure iManager, then select the Plug-in Download tab. From this page, you can enable and disable Novell download site queries. When enabling plug-in queries, you can choose to query for updates only, or for every compatible plug-in.
The default setting, Show updates to Novell Plug-in Modules (NPM) installed on the server does not list available Field Patch (FP) updates in Available Novell Plug-in Modules. To see if an iManager 2.6 FP is available, select Select Show every available Novell Plug-in Module (NPM).
After enabling plug-in queries, you can search for and install plug-ins from Configure > Plug-in Installation > Available Novell Plug-in Modules.
The following issues exist in the iManager 2.6 environment:
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.
iManager 2.6 provides administrative functionality. Portal services such as eGuide, Universal Password Management, and Identity Manager Password Self-Service provide self-service functionality.
You can administer Universal Password Management and Identity Manager Password Self-Service from an iManager 2.6 server; however, you must provide an iManager 2.0.2 server for your users to access in order to change their passwords.
To configure iManager 2.0.2 to act as a user portal, run the password self-service installer on all iManager servers to install the service. You can download the plug-ins from the Novell download site.
You can also use Virtual Office.
Double-click the pwd_install.exe file.
Deselect iManager Plug-ins for Password Management on the Install Components page.
If a .npm file contains .npg files in the Packages directory, these .npg files are not uninstalled. All other files included in the .npm are uninstalled.
Be aware of the following login-related issues with iManager 2.6:
The iChain® Single Sign-On functionality (including Forward authentication, OLAC, and Form Fill) does not work in a multitree environment. iManager 2.6 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.6 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.
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.
iManager includes a self-signed certificate that you use when installing Apache with iManager on Windows, Linux, and Solaris. It has an expiration date of one year.
This was never intended to be a long-term implementation. It is a temporary solution to get your system up and running so you can use iManager securely immediately after installation. You must get a valid certificate from a Certificate Authority and replace this temporary one as soon as possible. OpenSSL does not recommend using self-signed certificates except for testing purposes.
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.6 is installed before eDirectory 8.7.3, the iManager login might fail and Tomcat might crash. To work around this problem, do one of the following:
Delete /var/novell/nici/100/
Restart Tomcat (/etc/init.d/novell-tomcat4 restart)
Delete /var/novell/nici/60001/
Stop Tomcat (/etc/init.d/imgr stop)
Start Tomcat (/etc/init.d/imgr start)
Delete /var/novell/nici/30/
Stop Tomcat (JAVA_HOME=/opt/java1.4 su www/opt/hpws/tomcat/bin/shutdown.sh)
Start Tomcat (JAVA_HOME=/opt/java1.4 su www/opt/hpws/tomcat/bin/startup.sh)
When re-installing iManager 2.6 on Linux, make sure to go through the uninstall routine before re-running the install routine. Running the install without first uninstalling the previous installation can cause the Tomcat configuration to become corrupt, and be unable to start.
This most commonly occurs when accessing iManager 2.0.x and iManager 2.6 with the same browser. Typically, you can resolve this issue by clearing the browser's cache and restarting the browser.
The server might abend while using iManager with products that use the Nsure® Audit 1.0.3 platform agent. To solve this problem:
Unload Java*.
Rename or delete the sys:\tomcat\4\webapps\nps\web-inf\lib\LogEvent.jar file.
Restart the server.
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 2.6 Administration Guide.
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 2.6 Administration Guide.
To create a plug-in ID that includes extended characters, create the plugin using standard characters, then use Advanced Properties to change the plug-in display name after it has been created.
After you upgrade to eDirectory 8.8 on NetWare, you are unable to log in to a remote tree through iManager. The following error is displayed when attempting to log in:
Login failed. The required dependencies were not found. Please reinstall this software from the original distribution to ensure the components are available. Refer to Novell documentation for the required prerequisites.
Workaround: Add the following to the beginning of the c:\nwserver\startup.ncf file, then restart the server:
env NDSD_TRY_NMASLOGIN_FIRST=true
After upgrading to eDirectory 8.8 on NetWare, iManager does not enforce password case-sensitivity. You can log in with an all-lowercase password, even when the original password is mixed case.
To work around this issue, add the following to the beginning of the c:\nwserver\startup.ncf file, then restart the server:
env NDSD_TRY_NMASLOGIN_FIRST=true
This is a ZeroG problem. Delete the .com.zerog.registry.xml file, then do a fresh install and uninstall of these NPMs. Registry file locations vary according to platform:
NetWare: sys:tomcat\4\webapps\nps\UninstallerData\specific_plugin/.com.zerog.registry.xml
Linux: /var/.com.zerog.registry.xml
Solaris: /var/opt/novell/tomcat4/webapps/nps/UninstallerData/specific_plugin/.com.zerog.registry.xml
HP-UX: /opt/hpws/tomcat/nps/webapps/nps/UninstallerData/specific_plugin/.com.zerog.registry.xml
Windows: \Program Files\Zero G Registry\.com.zerog.registry.xml
Internet Explorer maintains one session per instance, while Mozilla uses the same session for all instances that use the same profile.
This difference in Web browser behavior gives the appearance that Mozilla 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 Mozilla browser, but only if each instance is using a different profile.
To work different sessions simultaneously, modify your profile using Mozilla's Profile Manager.
If you are using iManager in Unrestricted mode, you see the following message on the iManager Home Page:
Notice: Some of the roles and tasks are not available
Clicking View Details might display a Not supported by current authenticators message for several of the tasks, even though the tasks work correctly. This message is misleading, and iManager removes these messages after you configure RBS.
After you upgrade or cancel a previous install (which means that you already have the NPMs on the Packages directory), a message appears: No plug-ins found or server not available. This message that displays during the install on the Select Plug-ins to Download window can be misleading.The reason that nothing appears on the list of NPMs is not that the plug-ins were not found, or even that the server is down. Rather, you already have them all in the packages directory.
When cancelling the install, you might not know that all or some of the plug-ins were indeed downloaded unto the box before the cancellation; the NPMs are still there.
When you are using NLD 9 SP2 and SUSE Linux 9.2 with the GNOME* desktop and try to open Mobile iManager, you see the following message at the command prompt:
:~/imanager/bin # ./iManager.sh./iManager.sh: line 154: 6180 Segmentation fault $JAVA_HOME/bin/java -server -cp $CPATH com.novell.emframe.bootstrap.iManagerBootstrap $1 $2 $3 $4 $5 $6 $7 $8 $9
To work around this issue, run Mobile iManager on NLD 9SP2 or SUSE Linux 9.2 using the KDE desktop.
JVM* 5.0 is not supported with iManager.
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.
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 a profile object is assigned to a user in the user login script settings, the profile object's rights are not updated as they should be, creating a situation in which the user does not have read rights to the profile’s login script.
Workaround: Manually grant the user read rights to execute the profile’s login script.
In the Roles and Tasks view, click Rights > Modify Trustee.
Browse to the profile object, then click OK.
Click Add Trustee.
Select the user that you want to assign this profile to, then click OK
Click Assigned Rights.
Check the All Attributes Rights and Entry Rights check boxes, then click Delete Property.
Click Add Property.
Select Login Script, then click OK.
Make sure Compare and Read are selected, click Done, then click OK.
When the confirmation window appears, click OK.
This grants the minimal rights necessary for the user to use the profile object.
When extracting the iMan_26_Mobile_iManager_linux.tar.bz2 file on some Linux distributions, the message "tar: A lone zero block at <number>" may appear. This message is caused by a defect in Ant, which was used to tar the iManager file. It is informational only, all iManager files extracted properly, and can be used without error.
For information on iManager 2.6 issues following this release, see TID #7006099, titled "Novell iManager 2.x Readme Addendum," in the Novell Knowledge Base.
Portions of iManager 2.6 are copyrighted by third-parties. The relevant license agreements for this third-party software are provided below.
Copyright 2005, 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 (C) 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 <pm AT jdom DOT 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 <jhunter AT jdom DOT org> and Brett McLaughlin <brett AT jdom DOT 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.