ITCAM for Microsoft Applications: Microsoft Active Directory Agent 6.3.1.20 Interim Fix 1readme

6.0 Installation instructions
============================

• Because there is no uninstall utility for this fix, make sure to perform a backup of your environment before installing this fix.
• The prerequisites listed under the Prerequisites for this fix section must be installed before this fix can be installed.
• For the purpose of this README, the symbol <CANDLEHOME> is the IBM Tivoli Monitoring installation directory. The default value for CANDLEHOME is the following.
  UNIX
  /opt/IBM/ITM
  Windows
  C:\IBM\ITM
• Before installing this fix on UNIX systems, set the environment variable CANDLEHOME to the IBM Tivoli Monitoring installation directory.
  For example: 

  > CANDLEHOME=/opt/IBM/ITM 
  > export CANDLEHOME

• Before installation, see the Known problems and workarounds section.

1. Transfer the appropriate archive file (6.3.1.20-TIV-ITM_ADO-IF0001.tar or .zip) to a temporary directory on the system that contains the agent code to be updated. For this README, the symbol <TEMP> represents the fully qualified path to this directory.
   Note: On Windows systems, this path includes the drive letter.
2. Expand the archive file using the "tar" command on UNIX systems or an extract utility on Windows systems. This step creates a directory structure that contains fixes for all of the supported platforms.
3. Use the "itmpatch" command to install the fix for that agent platform. 
   On Windows systems, if the fix was expanded to <TEMP>\6.3.1.20-TIV-ITM_ADO-IF0001, the install command for 64 bit is, 

   > itmpatch -h <CANDLEHOME>
              -i <TEMP>\6.3.1.20-TIV-ITM_ADO-IF0001\k3z_wix64_tema_if0001.cab

1. Transfer the appropriate archive file (6.3.1.20-TIV-ITM_ADO-IF0001.tar or .zip) to a temporary directory on the IBM Tivoli Enterprise Monitoring Server system. For this README, the symbol <TEMP> represents the fully qualified path to this directory.
   Note: On Windows systems, this path includes the drive letter.
2. Expand the archive file using the "tar" command on UNIX systems or an extract utility on Windows systems. This step creates a directory structure that contains fixes for all of the supported platforms.
3. To add the agent fix bundles into the remote deploy depot, use the "tacmd addBundles" command found in $CANDLEHOME/bin on UNIX systems or in %CANDLE_HOME%\bin on Windows systems. For more information on the "tacmd addBundles" command, see the IBM Tivoli Monitoring Administrator's Guide.
   1. Following is the command on the UNIX systems, if the fix was expanded to <TEMP>/6.3.1.20-TIV-ITM_ADO-IF0001.

      > $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.3.1.20-TIV-ITM_ADO-IF0001

   2. Following is the command on the Windows systems, if the fix was expanded to <TEMP>\6.3.1.20-TIV-ITM_ADO-IF0001.

      > %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.3.1.20-TIV-ITM_ADO-IF0001

      Where,
      -n indicates that prerequisite bundles are not automatically added. The -n parameter must be used because the fix directory does not contain any prerequisites that the fix might require. 
      -i is the directory that contains the deployment bundles to be added to the depot. 
4. To log in to the Tivoli Enterprise Monitoring server, and deploy the fix to the appropriate nodes where the agent is running, use the following "tacmd" commands. For more information on the "tacmd login" and "tacmd updateAgent" commands, see Appendix A. Commands reference of the IBM Tivoli Monitoring Administrator's Guide.
   1. ​​​​​​Following is the command on the UNIX systems, 

      > $CANDLEHOME/bin/tacmd login -s <server>
                                    -u <itmuser>
                                    -p <password>
      > $CANDLEHOME/bin/tacmd listSystems

      The output shows the Managed system nme for the OS agent on the remote system to be updated. Use this value as the target of the "tacmd updateAgent" command.

       

      > $CANDLEHOME/bin/tacmd updateAgent -t 3Z 
                                          -n <Managed system name> 
                                          -v 063120001

        ​​​​​Following is the command on the Windows systems,

      > %CANDLE_HOME%\bin\tacmd login -s <server> 
                                      -u <itmuser> 
                                      -p <password>
      > %CANDLE_HOME%\bin\tacmd listSystems

      The output shows the Managed system name for the OS agent on the remote system to be updated. Use this value as the target of the "tacmd updateAgent" command.

      > %CANDLE_HOME%\bin\tacmd updateAgent -t 3Z
                                            -n <Managed system name> 
                                            -v 063120001

      Note:

      • The component (-t) for the "tacmd updateAgent" command is specified as two characters (3Z), not three characters (K3Z).
      • The node (-n) for the "tacmd updateAgent" command is the managed system name of the operating system (OS) agent to be updated.
      • The target node for the "tacmd updateAgent" command is always an OS agent. 

1.   Transfer the appropriate archive file 6.3.1.20-TIV-ITM_ADO-IF0001.tar or .zip) to the Tivoli Enterprise Monitoring Servers, Tivoli Enterprise Portal Servers, or Tivoli Enterprise Portal Desktops.
2. Expand the archive file using the "tar" command on UNIX systems or an extract utility on Windows systems. This step creates a directory structure that contains fixes for all of the supported platforms.
3. Expand the archive file (k3z_tems_teps_tepd_if0001.tar or .zip) that contains the updates for Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal Desktop using the "tar" command on UNIX systems or an extract utility on Windows systems. This step creates a directory structure that includes a subdirectory called CD-ROM, with the necessary updates.
4. For IBM Tivoli Monitoring Version 6.3 or above, one of the following additional steps must be performed.
   1. Acquire a platform-specific pre-packaged JRE version of the Application Support Installer (ASI). See IBM Tivoli Monitoring Application Support Installer, 6.2-tiv-itm_asi-if0001 at http://www-.ibm.com/support/docview.wss?uid=swg24024800 for download and installation instructions.
   2. Specify the '-j javahome' parameter with the path to a 32-bit java 1.5 or java 1.6 installation when running the itmasi.sh or itmasi.bat script described below.
5. Use the Application Support Installer script to launch either GUI installation or silent installation of the application support files.  
   GUI installation option
   The GUI can be started by using one of the following commands from within the CD-ROM directory where setup.jar is located. 
   UNIX

   > ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>] 

   Windows

   > itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>] 

   When prompted by the Application Support Installer for the installable media directory, select the CD-ROM directory, not the component directory. The installer can install updates for multiple components at the same time.
   Silent installation option
   To use the silent installation option, use one of the following commands from within the CD-ROM directory where setup.jar is located.      
   Note: Using the silent installation option for Linux and zLinux operating systems requires the following files contained in interim fix 6.2-TIV-ITM_ASI-IF0002:
   -  Linux: setupLinux.bin
   -  zLinux: setupLinux390.bin
   Follow the installation instructions contained in the "6.2-TIV-ITM_ASI-IF0001.README".
   UNIX

   >  ./itmasi.sh -h <CANDLEHOME>[-silent] 
                  [-r <response file>] 
                  [-j <JAVAHOME>] 

   
   Windows

   > itmasi -h <CANDLEHOME> [-silent] 
            [-r <response file>] 
            [-j <JAVAHOME>] 

   Where,
   -h <CANDLEHOME> - Required. The path to the IBM Tivoli Monitoring installation directory.
   r <response file> - Optional. Customized response file name. The default response file "response.txt" in the CD-ROM directory can be copied and modified for your environment. Do not update "response.txt". 
   -j <JAVAHOME> - Optional. The fully-qualified path to the "bin" directory where Java(R) is installed. The location of Java on your system might vary.
6. The next panel presented by the Application Support Installer asks for the selection of which Tivoli Monitoring components you want to add application support to. For this fix, check or clear the check boxes as follows
   1. Tivoli Enterprise Monitoring Server(TEMS) checkbox 
   2. Tivoli Enterprise Portal Server(TEPS) checkbox
   3. Tivoli Enterprise Desktop Client(TEPD) checkbox
7. Continue through the remaining GUI panels selecting the ADO 06.31.20.01 support to complete the installation.
8. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal Browser was running when the update was installed, it must be restarted.

7.1 Installation instructions for agent baroc file

7.2 Additional information on using "itmpatch" command

itmpatch -h <installation home> [OPTIONS]
itmpatch -h <installation home>
         -t { <patch_file_directory> | <patch_file> }
itmpatch -h <installation home> 
         -i { <patch_file_directory> | <patch_file> }

• -h  Specifies the IBM Tivoli Monitoring installation directory
• -i  Specifies the path to the directory or patch file to be installed
• -t  Generates a report of the actions to be taken by the patch.
  Example
  UNIX
  To preview the fix installation, use the "-t" option:

  > <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>

  To install the fix, use the "-i" option:

  > <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>

  Where,
  <CANDLEHOME> is the fully qualified IBM Tivoli Monitoring installation directory. On Windows systems, this path must include the drive letter.
  <TEMP> represents the fully qualified directory specification where the fix is located. On Windows systems, this must include the drive letter.

7.3 Verifying the update

7.4 Caching Configuration