iManager 2.6 Maintenance Update 1 Readme

March 15, 2006

1.0 Issues Resolved in Maintenance Update 1
2.0 Changed Files
3.0 Downloading and Installing an iManager Maintenance Update
4.0 Installing the Maintenance Update during the initial iManager 2.6 installation
5.0 Error installing the Maintenance Update on HP-UX
6.0 Legal Notices

1.0 Issues Resolved in Maintenance Update 1

The following issues were resolved in Maintenance Update 1:


2.0 Changed Files

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.20060310
/WEB-INF/lib/jclient.jar.20060310
/portal/modules/dev/javascripts/exchanger.js.20060310
/portal/modules/fw/javascripts/ObjectView.js.20060310
/portal/modules/fw/skins/default/devices/default/About.jsp.20060310
/portal/modules/fw/skins/default/devices/default/AsyncProgress.jsp.20060310
/portal/modules/base/skins/default/devices/default/pShared_IntruderLockout.jsp.20060310
/WEB-INF/bin/windows/jclient.dll.20060310
/WEB-INF/bin/windows/dclient.dll.20060310
/WEB-INF/bin/windows/sal.dll.20060310
/WEB-INF/bin/windows/spmdclnt.dll.20060310
/WEB-INF/bin/linux/libJClient.so.1.0.0.20060310
/WEB-INF/bin/linux/libndssdk.so.1.0.0.20060310
/WEB-INF/bin/linux/libsal.so.1.0.0.20060310
/WEB-INF/bin/linux/libsch.so.1.0.0.20060310
/WEB-INF/bin/linux/libspmclnt.so.20060310
/WEB-INF/bin/solaris/libJClient.so.1.0.0.20060310
/WEB-INF/bin/solaris/libndssdk.so.1.0.0.20060310
/WEB-INF/bin/solaris/libsal.so.1.0.0.20060310
/WEB-INF/bin/solaris/libsal_psr.so.1.0.0.20060310
/WEB-INF/bin/solaris/libsch.so.1.0.0.20060310
/WEB-INF/bin/solaris/libspmclnt.so.20060310
/WEB-INF/bin/hpux/libJClient.sl.1.0.20060310
/WEB-INF/bin/hpux/libndssdk.sl.1.0.20060310
/WEB-INF/bin/hpux/libsal.sl.1.0.20060310
/WEB-INF/bin/hpux/libsch.sl.1.0.20060310
/WEB-INF/bin/hpux/libspmclnt.sl.20060310

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.



3.0 Downloading and Installing an iManager Maintenance Update

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 iman26mu1.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 iman26mu1.tgz | tar xvf - ). Linux users can use tar -zxvf iman26mu1.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.

  1. Log in to iManager.

  2. Click the Configure button.

  3. Click Plug-in Installation > Available Novell Plug-in Modules

  4. Click Add and browse to the iMan26.npm file, then click OK.

  5. Verify that the Module is iMan26.npm and the Description reads "Maintenance Update 1 for iManager 2.6"

  6. Select the checkbox next to the maintenance update file iMan26.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. IE may actually remove the .npm extension and replaces it with .zip.  The extension must be .npm or the install will refuse to upload the file. 
     

  7. 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*

    As root enter /var/opt/novell/tomcat4/bin/shutdown.sh, then enter /var/opt/novell/tomcat4/bin/startup.sh.

    HP-UX*

    As root 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

     

  8. 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).



4.0 Installing the Maintenance Update during initial iManager 2.6 installation.

Although the maintenance update file will be listed as one of the available plug-ins to install during the intial iManager 2.6 installation, there is a possibility that the newer files copied from the maintenance update will be overwritten with the original iManager 2.6 files by the time the install completes.  It is NOT recommended to select the maintenance update during the initial installation.  Install the maintenance update as a POST plug-in install only.



5.0 Error Installing the Maintenance Update on HP-UX

If you install the Maintenance Update on iManager 2.6 running on HP-UX, you will get a message that states the installation completed, but the iMan26.npm stays in the list of Available Plug-in Modules.  If you look in catalina.out it will report:

installing iMan26.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.6 and follow the normal steps to install the iMan26_<version>.npm patch.
 
5. After the patch is installed. Shutdown Tomcat.

su root
/opt/hpws/tomcat/bin/shutdown.sh
 
6. Unzip the iMan26_<version>.npm file to a temporary directory of choice.

unzip iMan26_<version>.npm
 
7. Copy the <temporary_directory>/currentwebapp/WEB-INF/bin/hpux directory to /opt/hpws/tomcat/webapps/nps/WEB-INF/bin/

cp -Rp <temporary_directory>/currentwebapp/WEB-INF/bin/hpux /opt/hpws/tomcat/webapps/nps/WEB-INF/bin/
 
8. Change the ownership and permissions of the copied files.

chown www:other /opt/hpws/tomcat/webapps/nps/WEB-INF/bin/hpux/*
chmod +x /opt/hpws/tomcat/webapps/nps/WEB-INF/bin/hpux/*
 
9. Start Tomcat

su www /opt/hpws/tomcat/bin/startup.sh



6.0 Legal Notices

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 © 2006 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.