ITCAM for Microsoft(R) App: Active Directory Agent 6.3.1.2-TIV-ITM_ADO-IF0002

Download Description

Copyright International Business Machines Corporation 2015.
All rights reserved.

Component: IBM(R) Tivoli(R) Composite Application Manager for
Microsoft(R) Applications: Microsoft Active Directory
Agent, Version 6.3.1.2


Component ID: 5724C71AO

Interim Fix 0002, (6.3.1.2-TIV-ITM_ADO-IF0002)

Date: May 29, 2015

Contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Notices


1.0 General description
=======================
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below.

2.0 Problems fixed
==================
The following problems are addressed by this fix.

2.1 APARs:
----------
APAR: IV72817
Abstract:Agent shows wrong value for "DCA PDC Master","DCA RID Master"
and "DCA Infrastructure Master" attributes of DCA attribute
group.
Additional Information:Agent shows wrong values for FSMO role owners
in "Domain Controller Availability" attribute group.

2.2 Defects
-----------
None.

2.3 Enhancements
----------------
None.

2.4 Superseded fixes:
---------------------
6.3.1.2-TIV-ITM_ADO-IF0001

2.5 APARS and defects included from superseded fixes
----------------------------------------------------
RFE: 61487
Abstract: Timestamp comparison for "RPL Partner Last Success Time" and
"RPL Partner Last Attempt Time" attribute in situation formula.

Additional Information: timestamp datatype is added for "RPL Partner Last
Success Time" and "RPL Partner Last Attempt Time" attribute.
Now timestamp comparison can be done in the situation formula
for these attributes.


3.0 Architecture and prerequisites
==================================
This fix is supported on all operating systems listed in Chapter 2 of
the IBM Tivoli Monitoring: Active Directory Agent User's Guide,
version 6.3.1.2.

The following link is for the Tivoli operating system and application
support matrix. Please refer to this matrix for the latest
certification information.

http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

3.1 Prerequisites for this fix
------------------------------
The prerequisite level for this fix is as follows:
- IBM Tivoli Monitoring, Version V6.2.3 Fix Pack 3
- IBM Tivoli Composite Application Manager for Microsoft Applications:
Microsoft Active Directory agent, Version 6.3.1.2
As this fix is cumulative, it can be installed on any fix level
for this version, release and mod level above the prerequisite.


4.0 Image directory contents
============================
This fix image contains the following files:

- 6.3.1.2-TIV-ITM_ADO-IF0002.README - This README file
- 6.3.1.2-TIV-ITM_ADO-IF0002.tar - Fix archive .tar format
- 6.3.1.2-TIV-ITM_ADO-IF0002.zip - Fix archive .zip format.

NOTE: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a UNIX(R) environment; use the .zip file
if you are working in a Windows(R) environment.

The fix archive file contains the following files:
- 6.3.1.2-TIV-ITM_ADO-IF0002/k3z_tems_teps_tepd_if0002.tar
- 6.3.1.2-TIV-ITM_ADO-IF0002/k3z_tems_teps_tepd_if0002.zip
- 6.3.1.2-TIV-ITM_ADO-IF0002/k3z_winnt_tema_if0002.cab
- 6.3.1.2-TIV-ITM_ADO-IF0002/k3z_wix64_tema_if0002.cab
- 6.3.1.2-TIV-ITM_ADO-IF0002/K3ZWINNT.dsc
- 6.3.1.2-TIV-ITM_ADO-IF0002/K3ZWIX64.dsc
- 6.3.1.2-TIV-ITM_ADO-IF0002/K3ZCONF.txt
- 6.3.1.2-TIV-ITM_ADO-IF0002/3z_dd.properties
- 6.3.1.2-TIV-ITM_ADO-IF0002/3z_dd_063102002.xml.
- itmpatch.exe

5.0 Installation instructions
=============================
This fix can only be installed over an existing installation. Use
the following steps to install this fix.

5.1 Before installing the fix
-----------------------------
- 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 section 3.1 entitled 'Prerequisites
for this fix' 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 '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
on Windows systems.

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

- Refer to section 7.0 entitled "Known problems and workarounds"
before installation.

5.2 Local agent update
----------------------
1. Transfer the appropriate archive file
(6.3.1.2-TIV-ITM_ADO-IF0002.tar or .zip) to a temporary directory
on the system that contains the agent code to be updated. For
the purpose of 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. For more information on the "itmpatch" command, see
section 6.2.

On Windows systems, if the fix was expanded to
<TEMP>\6.3.1.2-TIV-ITM_ADO-IF0002, the install command is:

For 32 bit:
> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.3.1.2-TIV-ITM_ADO-IF0002\k3z_winnt_tema_if0002.cab

For 64 bit:
> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.3.1.2-TIV-ITM_ADO-IF0002\k3z_wix64_tema_if0002.cab

5.3 Remote agent update
-----------------------
1. Transfer the appropriate archive file
(6.3.1.2-TIV-ITM_ADO-IF0002.tar or .zip) to a temporary directory
on the IBM Tivoli Enterprise Monitoring Server system. For the
purpose of 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.

On UNIX systems,
if the fix was expanded to <TEMP>/6.3.1.2-TIV-ITM_ADO-IF0002:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.3.1.2-TIV-ITM_ADO-IF0002

On Windows systems,
if the fix was expanded to <TEMP>\6.3.1.2-TIV-ITM_ADO-IF0002:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.3.1.2-TIV-ITM_ADO-IF0002

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. Please see Section 3.1 for the prerequisites
for this fix.
-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.

On UNIX systems:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>

> $CANDLEHOME/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.

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

On 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 063102002

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.


5.4 Agent support update
------------------------
Use the following steps to update the Tivoli Enterprise Monitoring
Server, Tivoli Enterprise Portal Server, or Tivoli Enterprise
Portal Desktop.

1. Transfer the appropriate archive file
6.3.1.2-TIV-ITM_ADO-IF0002.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_if0002.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. Use the Application Support Installer script to launch either
GUI installation or silent installation of the application
support files.

Note: For IBM Tivoli Monitoring Version 6.3 or above, one
of the following additional steps must be performed.

1. Aquire 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-if0002 at
http://www-01.ibm.com/support/docview.wss?uid=swg24034924
for download and installation instructions.

2. Specify the '-j javahome' parameter with the path to
a 32-bit java(r) 1.5 or java 1.6 installation when
running the itmasi.sh or itmasi.bat script described below.

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.

On UNIX systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]

On Windows systems:
> 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".

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

On Windows systems:
> 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.

5. 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:

checked - Tivoli Enterprise Monitoring Server(TEMS)
checked - Tivoli Enterprise Portal Server(TEPS)
checked - Tivoli Enterprise Desktop Client(TEPD)

Continue through the remaining GUI panels selecting the
ADO 06.31.02.02 support to complete the installation.

6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise
Portal Browser was running when the update was installed, it
must be restarted.


6.0 Additional installation information
=======================================
Any existing Microsoft ADO Agent should be restarted after the
installation of this fix.

6.1 Installation instructions for agent baroc file
--------------------------------------------------
Fix (6.3.1.2-TIV-ITM_ADO-IF0002) includes changes to the agent
baroc files which need to be reinstalled. If you have already
installed these baroc files, there are no additional installation
steps. If not,refer to IBM Tivoli Monitoring, Installation
and Setup Guide under "Installing monitoring agent baroc files
on the event server" in "Installing the IBM Tivoli Enterprise
Console Event Synchronization" section for more information.

6.2 Additional information on using "itmpatch" command
------------------------------------------------------
The "itmpatch" command has the following syntax.

Usage: 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> }

where:
-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.

For example, on UNIX systems:
- 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.


6.3 Verifying the update
------------------------
1. To verify the agent was updated correctly, use the "tacmd" command
to view the agent's current version after the agent is restarted.
You are required to log in to a Tivoli Enterprise Monitoring
Server prior to viewing the agent version.

For example:
On UNIX systems, where $CANDLEHOME is the IBM Tivoli
Monitoring installation directory, the default location
is '/opt/IBM/ITM'.

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

> $CANDLEHOME/bin/tacmd listSystems -t 3Z

On Windows systems, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory, the default location
is 'C:\IBM\ITM'.

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

> %CANDLE_HOME%\bin\tacmd listSystems -t 3Z

Note:
- The component (-t) for the tacmd "listSystems" command is
specified as two characters (3Z), not three characters (K3Z).

When the agent update is successful, the agent version is:
06.31.02.02.

After the agent is restarted, you can also use the GUI to verify
the agent was successfully updated.
For the agent on Windows systems, the version number is
06.31.02.02.

2. To verify the agent support files were updated correctly, use
the "kincinfo" command on Windows systems or the "cinfo" command
on Linux or UNIX systems. The sample output below shows the
versions of the Tivoli Enterprise Portal Server, Tivoli
Enterprise Monitoring Server, or Tivoli Enterprise Portal
Desktop systems after this fix has been successfully applied.

Note: The displayed date of the build might not be accurate.
This is a known problem.

On UNIX or Linux systems:
-------------------------
To validate that all components have been installed, run the
following command:

./cinfo -i


On Windows systems:
-------------------
To validate that all components have been installed, run the
following command:

For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i

************* Thursday, May 21, 2015 2:01:22 AM *************
User : Administrator Group : NA
Host Name : ESX3-AD-T-64 Installer : Ver: 062303000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory


PC APPLICATION SUPPORT DESC PLAT APP VER
BUILD INSTALL DATE

3Z TEMS App Support/Active Directory Support WICMS 06.31.02.02
51251 20150513 1248
3Z TEPS App Support/Active Directory Support WICNS 06.31.02.02
51251 20150513 1248
3Z TEPB App Support/Active Directory Support WIXEB 06.31.02.00
41641 20150513 1248
3Z TEPD App Support/Active Directory Support WIXEW 06.31.02.02
51251 20150513 1248


6.4 Caching Configuration
-------------------------------------
Caching Configuration: With this currently implemented mechanism of
configuring caching, the customer can enable or disable caching
and also set the cache interval. This is achieved by using an
environment variable "ADO_CACHE_INTERVAL" in the environment file
K3ZENV. When this fix is applied, a prescript (k3z_preinstall.cmd)
is run which sets the ADO_CACHE_INTERVAL in the K3ZENV file.
If the variable ADO_CACHE_INTERVAL already exists in the K3ZENV
file, the script quits without making any changes.
ADO_CACHE_INTERVAL not only acts as ON/OFF flag, but the value
which is given in seconds, forms the caching interval (time
interval between consecutive data collection). Any positive integer
value turns ON the caching mechanism and negative or zero value
turns it OFF. The k3z_preinstall.cmd script verifies the present
installation of the Monitoring Agent for Active Directory. By default
the value of ADO_CACHE_INTERVAL is set as 240. The customer needs to
turn it OFF by setting the value to 0.


Caching can be turned ON or OFF during run time through Manage Tivoli
Enterprise Monitoring Services (kinconfig.exe). The steps are as
follows:

1. In Manage Tivoli Enterprise Monitoring Services (kinconfig.exe),
select the Active Directory Agent.
2. Right click and go to “Advanced” options.
3. Select "Edit ENV File" from the options. This opens the
K3ZENV file for editing.
4. The ADO_CACHE_INTERVAL variable exists in the K3ZENV file.
To turn OFF caching, set ADO_CACHE_INTERVAL to 0.
To turn ON caching, set ADO_CACHE_INTERVAL to any positive
integer value. This value forms the caching interval
in seconds. For instance, a value of 180 would mean a
3 minute interval.
5. After editing the K3ZENV file, save and close the file to
implement the new cache interval value.
6. A message box will appear asking if agent needs to be recycled
to include the changes in agent functionality.
- "Yes" recycles the agent with the new caching interval value.
- "No" lets the agent continue to run without the changes to
caching interval. When the agent is restarted, the changes
will be implemented.

Note: A negative or zero value turns off caching.
Non-integers (alphabetics, special characters and
alphanumerics are not supported for the cache interval and
might result in unexpected behavior of the Monitoring Agent
for Active Directory. The value recommended for the cache
interval is 240 seconds.

7.0 Known problems and workarounds
==================================
Abstract: Agent version is not upgraded in Add/Remove program however
Build level for the patch is upgraded.
Problem: When we upgrade to the latest patch and checked it on "Add or
Remove Fetures tab" it shows the build level is updated for
the patch but the agent version is not updated.
Workaround: None

8.0 Additional product information
===================================
None.


9.0 Notices
===========
This information was developed for products and services offered in
the United States. IBM may not offer the products, services, or
features discussed in this document in other countries. Consult your
local IBM representative for information on the products and services
currently available in your area. Any reference to an IBM product,
program, or service is not intended to state or imply that only that
IBM product, program, or service may be used. Any functionally
equivalent product, program, or service that does not infringe any
IBM intellectual property right may be used instead. However, it is
the user's responsibility to evaluate and verify the operation of any
non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document
does not grant you any license to these patents. You can send license
inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

The following paragraph does not apply to the United Kingdom
or any other country where such provisions are inconsistent
with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.

This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.


Trademarks and service marks
----------------------------
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks
of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks
is available on the Web at "Copyright and trademark information" at
www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks
of Microsoft Corporation in the United States, other countries, or
both.

Java and all Java-based trademarks are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States
and other countries.

Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.

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

Third-Party License Terms and Conditions, Notices and Information
-----------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.

Notwithstanding the terms and conditions of any other agreement you
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:

- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.