November 2, 2005
1.0 Issues
Resolved in Maintenance Update 3
2.0 Issues
Resolved in Maintenance Update 2
3.0 Issues
Resolved in Maintenance Update 1
4.0 Changed
Files
5.0 Downloading and Installing an
iManager Maintenance Update
6.0 Installing NetWare 6.5 SP4 (OES SP1) on a server with
iManager 2.5 Maintenance Update 3 installed.
7.0 Error
installing the Maintenance Update on HP-UX
8.0 Legal
Notices
The following issues were resolved in Maintenance Update 3:
Removed veto from deletor task for eDirectory cluster objects.
Fixed NullPointerException in Plug-in Studio after upgrade from iManager 2.0.2.
Fixed NullPointerException when target partition/server DN includes DBCS in changing replica type.
Fixed simple selection to use full name and/or last name in searches.
Added graphic for "Tree" object in rights management.
Changed Namespace exception for SINGLE_VALUED_ATTRIBUTE to be more descriptive.
Fixed a problem where password was displayed on the url after a login after the login had already expired.
The following issues were resolved in Maintenance Update 2:
Fixed creating users with null passwords; when creating a user, the end-user should be allowed to select an option of allowing the created user to log in without a password.
Fixed plug-in studio to allow creation of plug-ins with more than 16 input fields.
Fixed expired tasks showing up in object view.
The following issues were resolved in Maintenance Update 1:
Added the ability to perform searches on Boolean Syntax
Fixed the "Test" link on the list of Email Notification Events so that it now actually sends the test email. This link did not work previously.
Fixed when developing a custom plug-in with the plug-in studio, if the user selected to work on an aux class, an error occurred if the aux class did not have a naming attribute.
Fixed the iManager Views task not being secured to authorized users. Before, any user was able to configure which views were hidden. Now the iManager Views task only allows authorized users to configure the views.
Fixed the uniqueID for a user object so that it is set to the exact name of the user object including the escape characters. Linux management tools did not work with this and they did not want the escape characters in the uniqueID. Also Rename Object was fixed to set the uniqueID to the new name.
Fixed the NPM installer to check for the required-version key in the manifest. Code was added to check this key, if it is set in the NPM's manifest file. The major and minor has to be the same as the iManager major and minor.
Removed the link to RBS configuration after uninstall of an NPM; when the NPM files are removed RBS does not have the plugininstall.xml of the NPM to remove the RBS objects.
Fixed java.lang.NullPointerException error when accessing the RBS Configuration page as a collection owner.
Fixed so "DirXML-Associations" attribute would not be copied from a template to a new user. This attribute was added to the exclude list.
Fixed error when using plug-in studio property book MV Control (e.g. MVCheckbox)for Multiple Object editing
Fixed not able to set a simple password with the set password task.
Fixed setpassword task so logged in user can set their own password.
Added warning in setpassword task when setting NDS password to ""
Added language files for Modules to Install task help.
The following files have been changed in this maintenance update.
NOTE: File
paths are relative to the ".../Tomcat/webapps/nps/"
directory.
/WEB-INF/lib/eMFrame.jar version:
2.5.20051102
/WEB-INF/lib/nps.jar version:
4.2.2.20051102
/WEB-INF/lib/iManagerBase.jar version:
2.5.20051102
/WEB-INF/lib/NAuditPA.jar version:
2.5.20051102
/WEB-INF/lib/bcprov-jdk14-122.jar version:
2.5.20051102
/WEB-INF/lib/iManTagLibrary.jar version:
2.5.20051102
/WEB-INF/lib/WebServiceSDK.jar version:
2.5.20051102
/WEB-INF/lib/AdminNamespace.jar version:
2.5.20051102
/portal/modules/fw/skins/default/devices/default/About.jsp
/portal/modules/fw/skins/default/devices/default/ChangePassword.jsp
/portal/modules/fw/javascripts/UiHandlerTools.js
/portal/modules/base/skins/default/devices/default/SetPass.jsp
/portal/modules/fw/skins/default/devices/default/EmailNotifyConfigTask.jsp
/portal/modules/fw/skins/default/devices/default/InstalledNPM.jsp
/portal/modules/base/help/de/modulestoinstall.html
/portal/modules/base/help/es/modulestoinstall.html
/portal/modules/base/help/fr/modulestoinstall.html
/portal/modules/base/help/it/modulestoinstall.html
/portal/modules/base/help/ja/modulestoinstall.html
/portal/modules/base/help/pl/modulestoinstall.html
/portal/modules/base/help/pt/modulestoinstall.html
/portal/modules/base/help/ru/modulestoinstall.html
/portal/modules/base/help/de/installednpm.html
/portal/modules/base/help/es/installednpm.html
/portal/modules/base/help/fr/installednpm.html
/portal/modules/base/help/it/installednpm.html
/portal/modules/base/help/ja/installednpm.html
/portal/modules/base/help/pl/installednpm.html
/portal/modules/base/help/pt/installednpm.html
/portal/modules/base/help/ru/installednpm.html
/portal/modules/fw/skins/default/devices/default/ModulesToConfirm.jsp
/portal/modules/base/skins/default/devices/default/CrtUserAcct.jsp
/WEB-INF/lib/iManagerBaseExt.jar
version:
2.5.20051102
/WEB-INF/iman.tld
/portal/modules/fw/javascripts/iManDialogScripts.js
/portal/modules/fw/skins/default/devices/default/PageOrder.jsp
/portal/modules/fw/skins/default/devices/default/PrimaryViewManagment.jsp
/portal/modules/dev/skins/default/devices/default/TaskHeader_inc.jsp
/portal/modules/fw/plugins/deletor.xml
IMPORTANT: Various files in the ".../Tomcat/work/standalone/localhost/nps/" folder will be changed due to the application of the maintenance update, including many of the compiled JSPs. If you want to restore your system back to the pre-maintenance update state, do one of the following:
1) Backup the ".../Tomcat/work/standalone/localhost/nps/" folder before installing the maintenance update and restore it when removing the maintenance update.
2) Delete or rename this folder when removing the maintenance update, which will force the .JSPs to be compiled as needed.
IMPORTANT: iManager maintenance updates do not make a backup of files replaced. The only way to roll back to a previous state is to backup all modified files before applying the update and then manually restoring the backed up files.
Also, iManager maintenance updates must be installed on all iManager servers in your environment. Maintenance updates do not get automatically replicated to other iManager servers in your tree. To see if the maintenance update has been installed on the server, view the iManager information page by clicking on the words "Novell iManager" in the upper-left corner of the iManager application window.
NOTE: After you install the iManager maintenance
update, iManager will be non-functional until you restart Tomcat.
Do not install this maintenance update if you are unable to restart
Tomcat at the same time.
To download and install an iManager
maintenance update:
EXTRACT THE FILE
For Windows and
Netware servers use a windows decompression utility that supports
tgz, (i.e. WinZip) to extract iman25mu3.tgz to a temporary directory
either on the workstation or on the server.
For Unix servers,
use gzip and tar to decompress and extract the tarball to a temporary
directory on which the patch will be applied.
(i.e. gzip -d -c
iman25mu3.tgz | tar xvf - ). Linux users can use tar -zxvf
iman25mu3.tgz.
NOTE: Maintenance
update files, like plug-ins, are packaged in modules (NPMs). Those
modules are capable of containing one or more maintenance updates.
This Maintenance Update patch is a comprehensive patch and includes
all fixes from previous Maintenance Update patches.
Log in to iManager.
Click the Configure button.
Click Module Installation > Available Novell Plug-in Modules
Click New and browse to the iMan25_3.npm file, then click OK.
Verify that the Module is iMan25_3.npm and the Description reads "Maintenance Update 3 for iManager 2.5"
Select the checkbox next to the maintenance update file iMan25_3.npm and click Install.
This install may take a few minutes.
NOTE: Internet
Explorer may append a .ZIP extension to the .NPM when it is
downloaded. Do not unzip the file; the Plug-in Module file (npm) can
be successfully installed regardless of the extension on the file.
Click Close and Restart Tomcat.
NOTE: Tomcat sometimes requires several minutes to fully initialize. Wait a few minutes before trying to log into iManager after restarting Tomcat.
PLATFORM |
RESTART COMMAND |
NetWare® 6.5 |
Enter TC4STOP. Wait at least 1 minute, then enter TOMCAT4 to start the service again. |
Windows* |
Stop and start the Tomcat service. |
Solaris* |
Enter /var/opt/novell/tomcat4/bin/shutdown.sh, then enter /var/opt/novell/tomcat4/bin/startup.sh. |
HP-UX* |
Enter /opt/hpws/tomcat/bin/shutdown.sh, then enter /opt/hpws/tomcat/bin/startup.sh. |
Linux |
Enter /etc/init.d/novell-tomcat4 stop, then enter /etc/init.d/novell-tomcat4 start. |
Mobile iManager |
Close Mobile iManager and re-open Mobile iManager |
Verify that the new maintenance update has been installed.
This can be done by checking the log file located in the webapps/nps/WEB-INF/changelog directory or by viewing the list located on the iManager information screen (click "Novell iManager" in the upper-left corner of the application window).
Installing
SP4 for NetWare 6.5 on a server that has iManager 2.5 Maintenance
Update 3 installed will overwrite the following files with the
Maintenance Update files that ship with NetWare 6.5 SP4 (Maintenance
Update
2)
SYS:SYSTEM\Tomcat\4\webapps\nps\WEB-INF\lib\AdminNamespace.jar
SYS:SYSTEM\Tomcat\4\webapps\nps\WEB-INF\lib\iManagerBase.jar
SYS:SYSTEM\Tomcat\4\webapps\nps\WEB-INF\lib\iManagerBaseExt.jar
SYS:SYSTEM\Tomcat\4\webapps\nps\WEB-INF\lib\iManTagLibrary.jar
SYS:SYSTEM\Tomcat\4\webapps\nps\WEB-INF\lib\nps.jar
SYS:SYSTEM\Tomcat\4\webapps\nps\WEB-INF\lib\WebServiceSDK.jar
If
this does happen, you can reinstall the Maintenance Update 3 npm. If
iManager doesn't give you the option to reinstall the npm, you will
need to manually overwrite the above files with the ones in the
Maintenance Update npm file. You can use any decompression utility
such as WinZip to extract the files from the iMan25_3.npm file. You
may also install NetWare 6.5 SP5 (OES SP2) which includes Maintenance
Update 3 by default.
If you install the Maintenance Update
on iManager 2.5 running on HP-UX, you will get a message that states
the installation completed, but the iMan25_<version>.npm stays
in the list of Available Plug-in Modules. If you look in
catalina.out it will report:
installing iMan25_<build
version>.npm...
launchExec command: /opt/java1.4/jre/bin/java
-Djava.awt.headless=true
-jar
/opt/hpws/tomcat/webapps/nps/WEB-INF/bin/iManagerModuleInstall.jar
-f
/opt/hpws/tomcat/webapps/nps/WEB-INF/bin/install.properties -i
silent
Error occurred during initialization of VM
java.lang.Error:
Properties init: Could not determine current working
directory.
launchExec: /opt/java1.4/jre/bin/java
-Djava.awt.headless=true
-jar
/opt/hpws/tomcat/webapps/nps/WEB-INF/bin/iManagerModuleInstall.jar
-f
/opt/hpws/tomcat/webapps/nps/WEB-INF/bin/install.properties -i
silent failed.
Return code = 1
To get around this issue, do
the following:
1. Shutdown Tomcat
su
root
/opt/hpws/tomcat/bin/shutdown.sh
2. Delete the
portal directory located in
/opt/hpws/tomcat/work/Standalone/localhost/nps/portal/
su
root
rm -r
/opt/hpws/tomcat/work/Standalone/localhost/nps/portal
3.
Start Tomcat as the www user
su www
/opt/hpws/tomcat/bin/startup.sh
4. Login to iManager
2.5 and follow the normal steps to install the iMan25_<version>.npm
patch.
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.
You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.
Copyright © 2005 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.
Novell is a registered trademark of Novell, Inc. in the United States and other countries.
All third-party trademarks (*) are the property of their respective owners.