Device Manager 2.0.0.2 Fix Pack 2 README


Last updated: May 21, 2008

This document contains information for Device Manager Version 2.0.0.2 Fix Pack 2.

 

This Readme includes the following information:


Updates included with this Fix Pack

This Fix Pack includes corrections for the following problems:


 

Return to top


Installing the Product Update tool

Device Manager Fix Pack 2 requires the Product Update tool, which is included with the Device Manager Fix Pack.

The Product Update tool creates a backup of your configuration in case you need to remove the Fix Pack later. Before you install this Fix Pack, verify that you installed TPM 5.1

To install the Product Update tool, complete the following steps:

  1. Open a command prompt and create a new directory (update_home) for the Product Update tool. Use the following directory locations for the update_home directory:

    Windows:

    C:\Program Files\IBM\Updatertool

    AIX or Linux:

    /usr/IBM/Updatertool

    Solaris:

    /opt/IBM/Updatertool

  2. Copy the Product Update tool ZIP file, ProductUpdateInstaller60.zip, to the directory (update_home) you just created.

  3. Unzip the ProductUpdateInstaller60.zip file.

 

Return to top


Installing Device Manager 2.0.0.2 Fix Pack 2

Fix Pack 2 requires that you install the Product Update tool.

The Fix Pack should be applied where the Device Manager product root was installed and configured. If Device Manager was installed to the Deployment Manager, then you install the Fix Pack at the Deployment Manager.

Before you install this Fix Pack, verify you have enough disk space:

Installing the Fix Pack

To install the Fix Pack, complete the following steps:

  1. Open a command prompt and change to the update_home directory, such as:

    Windows:

    C:\Program Files\IBM\Updatertool

    AIX or Linux:

    /usr/IBM/Updatertool

    Solaris:

    /opt/IBM/Updatertool

  2. AIX, Linux, or Solaris only:   Use the following command to change the file permissions of the scripts:
    chmod +x update*.sh

  3. Copy the Fix Pack JAR file, DMS_PTF_2.0.0.2.jar, to the directory that contains the Product Update tool (update_home).

  4. Set the JAVA_HOME environment variable.

    Each time you open a new command prompt, you need to set the JAVA_HOME environment, so if you are performing these steps on multiple computers, make sure to set the JAVA_HOME variable.

    1. Open a command prompt window.

    2. Change directory to the was_home/bin directory, where was_home is the installation directory of the WebSphere Application Server on the computer.

    3. Issue the appropriate command:

      Windows:

      setupCmdLine.bat

      AIX, Linux, or Solaris:

      . ./setupCmdLine.sh
      

      Note: When running this command in a AIX, Linux, or Solaris shell, be sure to use the syntax " . ./setupCmdLine.sh ". If you do not precede the command with the period and space, the Java environment will not be properly set for the active shell.

  5. Run the preUpdate command.

    Navigate to the dms_home/bin directory and run the following command, where was_username is the WebSphere Application Server administrator ID and was_password is the password for the administrator ID:

    Windows:

    preUpdate -user was_username -password was_password

    AIX, Linux, or Solaris:

    ./preUpdate.sh -user was_username -password was_password

  6. Open a command prompt and change to the update_home directory, such as:

    Windows:

    C:\Program Files\IBM\Updatertool

    AIX or Linux:

    /usr/IBM/Updatertool

    Solaris:

    /opt/IBM/Updatertool

  7. Install the Fix Pack files using the Product Update tool. You can use the GUI version, "UpdateProductWizard", or the following command line Version.

    Note: The commands shown below spans multiple lines for clarity, but the command begins with updateProduct and must be entered on a single line.

    For example:

    updateProduct -fixpack -installDir "dms_home"
    -fixpackDir "update_home"
    -install -fixpackID DMS_PTF_2002
    -productID DMS -productVersion 2.0.0.1

    Where dms_home represents the full path to the installation directory of Device Manager server.

    Windows example:

    updateProduct -fixpack -installDir "C:\Program Files\IBM\DeviceManager" 
    -fixpackDir "C:\Program Files\IBM\Updatertool" 
    -install -fixpackID DMS_PTF_2002
    -productID DMS -productVersion 2.0.0.1

    AIX or Linux example:

    ./updateProduct.sh -fixpack -installDir "/usr/IBM/DeviceManager" 
    -fixpackDir "/usr/IBM/Updatertool" 
    -install -fixpackID DMS_PTF_2002
    -productID DMS -productVersion 2.0.0.1

    Solaris example:

    ./updateProduct.sh -fixpack -installDir "/opt/IBM/DeviceManager" 
    -fixpackDir "/opt/IBM/Updatertool" 
    -install -fixpackID DMS_PTF_2002
    -productID DMS -productVersion 2.0.0.1

  8. Run the postUpdate command.

    Change to the dms_home/bin directory and run the following command, where was_username is the WebSphere Application Server administrator ID and was_password is the password for the administrator ID:

    Windows:

    postUpdate -user was_username -password was_password

    AIX, Linux, or Solaris:

    ./postUpdate.sh -user was_username -password was_password

  9. Stop and Start Server1.

 

Return to top


Removing the Device Manager 2.0.0.2 Fix Pack 2

To remove Device Manager 2.0.0.2 Fix Pack 2, do the following steps:

  1. Set the JAVA_HOME environment variable.

    Each time you open a new command prompt, you need to set the JAVA_HOME environment, so if you are performing these steps on multiple computers, make sure to set the JAVA_HOME variable.

    1. Open a command prompt window.

    2. Change directory to the was_home/bin directory, where was_home is the installation directory of the WebSphere Application Server on the computer.

    3. Issue the appropriate command:

      Windows:

      setupCmdLine.bat

      AIX, Linux, or Solaris:

      . ./setupCmdLine.sh

      Note: When running this command in a AIX, Linux, or Solaris shell, be sure to use the syntax " . ./setupCmdLine.sh ". If you do not precede the command with the period and space, the Java environment will not be properly set for the active shell.

  2. Run the preUpdate command.

    Change to the dms_home/bin directory and run the following command, where was_username is the WebSphere Application Server administrator ID and was_password is the password for the administrator ID:

    Windows:

    preUpdate -user was_username -password was_password

    AIX, Linux, or Solaris:

    ./preUpdate.sh -user was_username -password was_password

  3. Open a command prompt and change to the update_home directory, such as:

    Windows:

    C:\Program Files\IBM\Updatertool

    AIX or Linux:

    /usr/IBM/Updatertool

    Solaris:

    /opt/IBM/Updatertool

  4. AIX, Linux, or Solaris only:   Use the following command to change the file permissions of the scripts:
    chmod +x update*.sh

  5. Remove the Fix Pack 2 files using the Product Update tool. You can use the GUI version, "UpdateProductWizard", or the following Command Line Version.

    Note: The command shown below spans multiple lines for clarity, but the command begins with updateProduct and must be entered on a single line.

    For example:

    updateProduct -installDir "dms_home"
    -fixpack -uninstall -fixpackID DMS_PTF_2002 
    -fixpackDetails

    Where dms_home represents the full path to the installation directory of Device Manager server.

    Windows example:

    updateProduct -installDir "C:\Program Files\IBM\DeviceManager" 
    -fixpack -uninstall -fixpackID DMS_PTF_2002
    -fixpackDetails
    

    AIX or Linux example:

    ./updateProduct.sh -installDir "/usr/IBM/DeviceManager" 
    -fixpack -uninstall -fixpackID DMS_PTF_2002
    -fixpackDetails

    Solaris example:

    ./updateProduct.sh -installDir "/opt/IBM/DeviceManager" 
    -fixpack -uninstall -fixpackID DMS_PTF_2002
    -fixpackDetails

  6. Run the postUpdate command.

    Change to the dms_home/bin directory and run the following command, where was_username is the WebSphere Application Server administrator ID and was_password is the password for the administrator ID:

    Windows:

    postUpdate -user was_username -password was_password

    AIX, Linux, or Solaris:

    ./postUpdate.sh -user was_username -password was_password

  7. Stop and Start server1.

 

Return to top


Trademarks

IBM, WebSphere are registered trademarks of the IBM Corporation in the United States, other countries, or both.

Microsoft, Active Directory, Exchange, Pocket PC, Internet Explorer, Windows, Windows 2003, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks of others.

 

Return to top


(c) Copyright International Business Machines Corporation 1994, 2005. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.