ITM for Virtual Environments: Citrix XenApp agent 7.2.0-TIV-ITM_CTXA-IF0007

Download Description

Copyright International Business Machines Corporation 2015.
All rights reserved.

Component: IBM® Tivoli® Monitoring for Virtual Environments: Citrix®
XenApp® Agent, Version 7.2.0

Component ID: 5724L92XA

Interim Fix 0007, 7.2.0-TIV-ITM_CTXA-IF0007

Date: April 1, 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 Copyright and trademark information
10.0 Notices


1.0 General description
===============
This fix resolves the APARs and defects listed in the "Problems fixed"
section below. This fix also includes the superseded fixes listed in
section 2.4.


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

2.1 APARs
-------------
APAR: IV71598
Abstract: Citrix License Server situation formulas contain
invalid attributes
Additional information: Eleven of the fifteen Citrix License
Server situations do not work because their formulas
contain invalid attributes. This can be seen by opening
the Situation Editor, expanding the Citrix License Server
node, selecting the KXA_CLS_Server_Down situation and
observing that the formula section is empty and the error
"KFWITM375W Situation formula contains invalid attributes"
is displayed in the lower left of the window.

APAR: IV69570
Abstract: ICA Listener Health Test times out in some environments
Additional information: In order to determine the status of
several key XenApp components the agent utilizes several
Citrix provided utilities, including the ICA listener
health test. In some environments the ICA Listener has
been observed to timeout and report a failing status in
the ICA Listener Responding attribute of the XenApp
Operational Status view on the Server Overview workspace,
even though the ICA Listener test passes when run manually.

APAR: IV69295
Abstract: XenApp agent data provider can't start when Windows
firewall is enabled
Additional information: XenApp agent Interim Fix 0005 and Interim
Fix 0006 does not allow the XenApp agent's data provider
to start if the Windows firewall is enabled. The message
'The Windows Firewall was detected as being up. Citrix
XenApp PowerShell SDK commands that require connectivity
to the XenApp Controller may respond in an undesirable
amount of time.' is displayed in the Log Text attribute
of the XenApp Agent Output Log view on the Agent Status
workspace and on the XenApp agent machine. The process
kxa6_data_provider.exe is not running when the process
kxaagent.exe is running.

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

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

2.4 Superseded fixes
-------------------------
7.2.0-TIV-ITM_CTXA-IF0006
7.2.0-TIV-ITM_CTXA-IF0005
7.2.0-TIV-ITM_CTXA-IF0004
7.2.0-TIV-ITM_CTXA-LA0003
7.2.0-TIV-ITM_CTXA-IF0002
7.2.0-TIV-ITM_CTXA-IF0001

2.5 APARs and defects included from superseded fixes
---------------------------------------------------------------

7.2.0-TIV-ITM_CTXA-IF0006
-------------------------
APAR: IV66826
Abstract: The ICA Listener Responding attribute always shows
'Fail'
Additional information: The ICA Listener Responding attribute in
the XenApp Operational Status view of the Server Overview
workspace always shows a value of 'Fail' when the XenApp
installation does not use the default ICA Listener port.
Diagnosing the problem can be done by navigating to the
Citrix HealthMon directory (example:
C:\Program Files (x86)\Citrix\HealthMon\Tests\Citrix) and
running the utility "ICAListener.exe" from the command line
with no parameters and seeing a result ending with "Check
ICA Test failed.", then running
"ICAListener.exe /hostname:<ServerName>"
where <ServerName> is the name of the XenApp server being
tested, and seeing a result ending with "Check ICA Test
passed."

APAR: IV66815
Abstract: No data is returned by the XenApp agent in large
environments
Additional information: The XenApp agent's custom data provider
fails to return data in large environments. When agent
logging level is set to Verbose, data provider log
(<System Name>_xa_kxa6_data_provider_<timestamp>-NN.log)
entries beginning with "Executing command:..." display
"Latest execution returned: <0> objects." or "Latest
execution returned: <null> objects." and the
"Time to complete:" value is higher than normal for the
environment.


7.2.0-TIV-ITM_CTXA-IF0005
-------------------------
APAR: IV63263
Abstact: Event log workspaces return no data
Additional information: The event log workspaces "XA6 Event Log",
"XA5 Event Log", and "CLS Event Log" do not return data when
monitored Windows events occur. This affects XenApp agent
v7.2 Interim Fix 0002, Limited Availability Fix 0003, and
Interim Fix 0004.

APAR: IV63037
Abstact: No data is returned for a view even if partial data is
available
Additional information: The XenApp agent's custom data provider
sometimes only has partial data available but displays no
data for any given view. When agent logging level is set to
Verbose, data provider log
(<System Name>_xa_kxa6_data_provider_<timestamp>-NN.log)
entries beginning with "Executing command:..." display
"Latest execution returned: <null> objects.". They can also
have a very high number for "Times since objects have
returned" in the data provider log.

APAR: IV63031
Abstract: XenApp agent does not start after its host machine is
restarted
Additional information: When the XenApp agent's host machine is
restarted, a timing condition can cause the agent or its
custom data provider to not start. Symptoms of this include
a) the agent has a status of "Stopped" and Windows System
event log has the Error event 7000, "The Monitoring Agent
for Citrix XenApp - Primary service failed to start due to
the following error: The service did not respond to the
start or control request in a timely fashion.", or
b) only the top-level agent subnode and Agent Status
workspace are available (not greyed out) in the portal.

APAR: IV63030
Abstract: Errors are logged after the monitoring server sends a
shutdown request
Additional information: When the monitoring server sends a
shutdown request to the XenApp agent's data provider, the
data provider continues to try to fullfill some outstanding
requests for data and logs exceptions. For example, in the
data provider log
(<System Name>_xa_kxa6_data_provider_<timestamp>-NN.log),
after an entry stating, "Received a SHUTDOWN request from
ITM.", entries are found stating, "Called with illegal
state. Expected 2 (REG_COMPLETE_STATE), got 3."

APAR: IV63025
Abstract: Data collection fails because the remote PowerShell
session authentication mechanism of Kerberos is not
supported
Additional information: The XenApp agent data collector uses only
the Negotiate PowerShell session authentication mechanism.
Add support for five additional PowerShell session
authentication mechanisms - Kerberos, Basic, Credential
Security Service Provider (CredSSP), Default, and Digest.
Example error message in the data provider log
(<System Name>_xa_kxa6_data_provider_<timestamp>-NN.log):
"An exception was caught while attempting to setup a
PowerShell runspace for command <Get-XAFarm> on
<XA651.COMPANY.LOCALNET> with the following message:
Connecting to remote server failed with the following error
message: The WinRM client cannot process the request. If the
authentication scheme is different from Kerberos, or if the
client computer is not joined to a domain, then HTTPS
transport must be used or the destination machine must be
added to the TrustedHosts configuration setting. Use
winrm.cmd to configure TrustedHosts. Note that computers in
the TrustedHosts list might not be authenticated. You can
get more information about that by running the following
command: winrm help config. For more information, see the
about_Remote_Troubleshooting Help topic."

APAR: IV63023
Abstract: An error occurs during XenApp agent shutdown
Additional information: During shutdown of the XenApp agent, an
error is logged to the data provider log
(<System Name>_xa_kxa6_data_provider_<timestamp>-NN.log)
saying, "The number of objects passed into
WaitHandle.WaitAll(), <xx>, is greater than the system
permits. Exception message: <The number of WaitHandles
must be less than or equal to 64.>."

APAR: IV63022
Abstract: Session Count displays 'Unavailable' when it should
display zero
Additional information: The Server Details view of the top-level
Remote Farm Monitoring (RFM) workspace displays 'Unavailable'
for the Session Count when it should display '0' (zero).

APAR: IV63021
Abstract: The optional Citrix Provisioning Server Client Service
is not monitored
Additional information: Add the capability to monitor the Citrix
Provisioning Server Client Service (also known as BNDevice)
in the Other Services Status attribute group.

APAR: IV63018
Abstract: The Citrix System Monitoring Agent service and its
database service are not monitored
Additional information: Add the capability to monitor the Citrix
System Monitoring Agent service (also known as Citrix
Edgesite agent, RSCorSvc service, and rscorsvc.exe) and also
its database service FirebirdServerCSMInstance in the Other
Services Status attribute group.


7.2.0-TIV-ITM_CTXA-IF0004
-------------------------
APAR: IV59378
Abstract: XenApp agent v7.2 logical navigator for remote farm
monitoring breaks the agent's physical workspaces
Additional information: Importing the optional sample custom logical
navigator file for remote farm monitoring
(xenapp_farm_details_logicalnav.xml) results in the
XenApp_Farm_Details workspace showing no subnodes and it also
breaks some of the default physical navigator workspaces for
the XenApp agent by making some workspace views such as
the top-level XenApp Farm workspace's Farm Summary view
display the error message "KFWITM454E Request failed due to
offline managed system(s).". A new optional sample custom
logical navigator file named XenApp_Agent_logicalnav.xml
replaces the remote farm monitoring logical navigator. The
new logical navigator file contains one navigator view named
"XenApp Agent 7.2" which includes updated subnodes for
XenApp 6.x local monitoring and XenApp 5 local monitoring
in addition to the new XenApp 6 remote farm monitoring
subnode.

APAR: IV58568
Abstract: Add Operating System Performance attribute group and
workspace
Additional information: The Citrix XenApp Server 5.x and 6.x local
monitoring components of the XenApp agent have been enhanced
to include an Operating System Performance attribute group
and alternate workspace on the Performance node. The
new workspace views are:
- Processor metrics
- Memory metrics
- System metrics
- Logical disk metrics
- TCPv4 metrics
- Counters that are ideally zero
- Context switches per second
- Segments sent and received per second

APAR: IV58563
Abstract: Add print subsystem monitoring attributes to XenServer
status groups
Additional information: Print subsystem monitoring has been added
to the XenApp Server 5.x and 6.x local monitoring components.
The following attributes have been added to the
XenApp_Status and XenApp_Status_5 attribute groups:
- Printers Test
- Printer Processor Test
- Printer Driver Test

APAR: IV58557
Abstract: Append Summary attributes to Detail groups for Remote
Farm Servers, Worker Groups, and Applications
Additional information: The Remote Farm Monitoring component's
Farm Server Details attribute group now includes attributes
joined from the Farm Summary attribute group. The Remote
Farm Monitoring component's Farm Worker Group Details
attribute group now includes attributes joined from the
Farm Worker Group Summary attribute group. The Remote Farm
Monitoring component's Farm Application Details attribute
group now includes attributes joined from the Farm
Application Summary attribute group. This has been done to
make it easier to compare individual server, worker group,
and application detail attributes with summary attributes
from a respective group that the individual component is a
part of.

APAR: IV58553
Abstract: Update XenApp agent sample reports
Additional information: The XenApp agent sample TCR reports
package has been updated. The Citrix XenApp Report
Prerequisite Scanner report has been improved and the
following reports have been added:
- Citrix XenApp Remote and Local Server Correlation Report
- Citrix XenApp Remote and Local Server Monitoring Count Report
- Citrix XenApp 6.x Server ICA Latency Average by User Report
- Citrix XenApp 6.x Server Load Report
- Citrix XenApp 6.x Server Session Duration Report

APAR: IV58479
Abstract: High XenApp server query load when the only published
application is a desktop
Additional information: The XenApp server query load can increase
the work load on a server when the only published
application is a desktop. The frequency of retries to get
applications served by a XenApp server has been reduced.

7.2.0-TIV-ITM_CTXA-LA0003
-------------------------
APAR: IV54485
Abstract: Remote deploy prereq check for
citrixHealthMonTestDirAccess fails with '[Not Found]'
Additional information: The XenApp agent v7.2 prereq scanner is
failing during remote deployment with the message
"citrixHealthMonTestDirAccess FAIL [Not Found]"

APAR: IV54483
Abstract: XenApp agent does not start after applying Interim
Fix 0002 unless it is reconfigured
Additional information: The XenApp v7.2.0 agent does not start
after applying 7.2.0-TIV-ITM_CTXA-IF0002. The agent will
only start after it is reconfigured. No configuration
values need to be changed if they were previously valid.

APAR: IV54470
Abstract: Historical configuration fails for table
KXA_CITRIX_LICENSE_SERVER_LICENSE_DETAILS
Additional information: Running kxa_hist_config.cmd does not
configure KXA_CITRIX_LICENSE_SERVER_LICENSE_DETAILS. It
fails with the error "KUIHCC090E: The -e|--description
has a long value. The description cannot be longer than
64 chars."

7.2.0-TIV-ITM_CTXA-IF0002
-------------------------
APAR: IV51357
Abstract: Processes are left running after the agent is
stopped
Additional information: The processes cmd.exe and PowerShell.exe,
which are started in the agents start up script
(KXA_run.bat), can be left running after the XenApp agent
is stopped.

APAR: IV51356
Abstract: CPU utilization metrics are inconsistent
Additional information: The values returned to the CPU utilization
metric are not always the same in Process Details, Session
Details, and User Details attribute groups for the
XenApp 5.0 and XenApp 6.x subnodes.

APAR: IV51355
Abstract: Idle time is too high in Session Details attribute
group
Additional information: The idle time can be much too high
(possibly more than 412 years) in the Session Details
attribute group.

APAR: IV51353
Abstract: All pipe instances are busy exception
Additional information: Under certain conditions, an entry in the
*_xa_kxa6_data_provider_*.log can be found saying "Unhandled
Exception: System.IO.IOException: All pipe instances are
busy."

APAR: IV51351
Abstract: Incorrect listing of server status in Remote Farm
Monitoring subnode
Additional information: When a server's state changes, the server
sometimes disappears from the results in all Remote Farm
Monitoring attribute groups.

APAR: IV51350
Abstract: Incorrect detection of Visual Studio 2010 C++
redistributable library
Additional information: The presence of the Visual Studio 2010
C++ redistributable library, msvcr100.dll, is checked by
a common, but not definite, location. With this fix, it
is now checked via the registry.

APAR: IV51349
Abstract: Inconsistent application session count between XenApp 5,
XenApp 6, and Remote Farm Monitoring subnodes
Additional information: The application session count is different
between XenApp 5.0, XenApp 6.x (XA6), and Remote Farm
Monitoring (RFM) subnodes. For example: there are 10
sessions using an application in the XA6 subnode but it
says there are 15 in a RFM subnode.

APAR: IV51348
Abstract: The Citrix Audio Redirection Service is counted twice
Additional information: The Citrix Audio Redirection Service
appears in both the Critical Services Status and Other
Services Status attribute groups in the XenApp 5 and
XenApp 6 subnodes when it should have only appeared in the
Other Services Status attribute group.

APAR: IV51347
Abstract: Applications assigned to WorkerGroups are not enumerated
properly in the Remote Farm Monitoring (RFM) subnode
Additional information: Applications assigned to WorkerGroups
appear in the Summary-centric attribute groups in the Remote
Farm Monitoring (RFM) subnode but not in the Details-centric
attribute groups in the RFM subnode.

APAR: IV51275
Abstract: IP address metric is displaying incorrectly when server
is down
Additional information: The IP address metric can display
incorrectly as "System String []" in all of the Remote Farm
Monitoring subnode's attribute groups.

APAR: IV51258
Abstract: Data provider continues to run after agent is stopped
Additional information: The data provider continues to run even
though the user stops the agent through the Manage Tivoli
Enterprise Monitoring Server application. An example is if
the user starts the agent, which calls agent start script
(KXA_run.bat), and immediately stops the agent before the
custom data provider executable has even been invoked by the
start script, much less connected to IBM Tivoli Monitoring
to receive the stop request.

APAR: IV51257
Abstract: Applications not served locally are being displayed
Additional information: Applications not served on the local
XenApp server are not being filtered out in the Application
Details and Application Summary attribute groups in the
XenApp 5 and XenApp 6 subnodes as they should be.

APAR: IV51256
Abstract: Remote monitoring of 'session-host only' XenApp server
fails
Additional information: If the agent is configured to remotely
monitor a session-host only configured XenApp server,
it fails. These configurations are not supported.

APAR: IV41610
Abstract: XenApp agent workspaces stop returning data when the
available servers in a farm drops to zero
Additional information: When there is only one connectable server
in a farm and it becomes unconnectable, making the total
number of servers available in the farm zero, the Tivoli
Enterprise Portal stops returning data for the XenApp agent.
The XenApp DataCollector log (*_xa_KXA_DataCollector_*.log)
displays "Unable to contact <ServerName>. Not going to make
command to <ServerName> until the PowerShell remoting
port <5985> is available."

APAR: IV41567
Abstract: Application Count is inaccurate
Additional information: The Application Count attribute used in
the User Details view of the Users workspace is inaccurate.

APAR: IV41566
Abstract: XenApp Edition Logging returns an error for PLT Edition
Additional information: When running on XenApp Platinum edition,
the agent logs the error, "Edition of XenApp installed:
<PLT>. Only Enterprise and Platinum editions are supported."

APAR: IV41563
Abstract: No data possible for "Top 10 Applications by Load
Level" view
Additional information: An obsolete attribute is used in the
"Top 10 Applications by Load Level" view of the Application
workspace causing no data to be available.

7.2.0-TIV-ITM_CTXA-IF0001
-------------------------
APAR: IV42643
Abstract: XENAPP 7.2 LOCAL INSTALL ISSUE ON GERMAN XENAPP 6.5
SYSTEM
Additional information: The XenApp agent shows only the agent
status subnode when installed locally on a XenApp v6 or
v6.5 server in languages which use a comma (,) as a
decimal place separator, instead of a period (.).
The "XenApp 6" node and, if installed, the "Citrix
License Server" nodes are not displayed.


3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the IBM
Tivoli Monitoring for Virtual Environments: Citrix XenApp Agent
User's Guide, version 7.2.0.

Please refer to the IBM Software Product Compatibility Reports (SPCR)
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html

Note: With this fix (7.2.0-TIV-ITM_CTXA-IF0007), the Citrix XenApp
agent is certified for Citrix License Server v11.11.1.

3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:
- IBM Tivoli Monitoring for Virtual Environments: Citrix XenApp
Agent, Version 7.2.0

- IBM Tivoli Monitoring, Version 6.2.2: Fix Pack 04 or
higher (6.2.2-TIV-ITM-FP0004).

Note: See section 7.0 Known problems and workarounds if you
recieve the error "itmpatch.exe has stopped working".

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:

- 7.2.0-TIV-ITM_CTXA-IF0007.README - This README file
- 7.2.0-TIV-ITM_CTXA-IF0007.tar - Fix archive .tar format
- 7.2.0-TIV-ITM_CTXA-IF0007.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® environment; use the .zip file if
you are working in a Windows® environment.

The fix archive file contains the following files:
- 7.2.0-TIV-ITM_CTXA-IF0007/KXA_winnt_tema_if0007.cab
- 7.2.0-TIV-ITM_CTXA-IF0007/KXA_wix64_tema_if0007.cab
- 7.2.0-TIV-ITM_CTXA-IF0007/kxa_tems_teps_tepd_if0007.tar
- 7.2.0-TIV-ITM_CTXA-IF0007/kxa_tems_teps_tepd_if0007.zip
- 7.2.0-TIV-ITM_CTXA-IF0007/KXAWINNT.dsc
- 7.2.0-TIV-ITM_CTXA-IF0007/KXAWIX64.dsc
- 7.2.0-TIV-ITM_CTXA-IF0007/kxa_patchdepot_720if7.bat
- 7.2.0-TIV-ITM_CTXA-IF0007/kxa_patchdepot_720if7.sh
- 7.2.0-TIV-ITM_CTXA-IF0007/xa_dd.properties
- 7.2.0-TIV-ITM_CTXA-IF0007/xa_dd_072000007.xml
- 7.2.0-TIV-ITM_CTXA-IF0007/ITMfVE_XenApp_Reports.zip
- 7.2.0-TIV-ITM_CTXA-IF0007/ITMfVE_XenApp_prereqchecker.zip
- 7.2.0-TIV-ITM_CTXA-IF0007/ITMfVE_XenApp_logicalnav.zip

The cab file has updates to the IBM Tivoli Enterprise Monitoring
Server component for a specific platform. The platform
that each file applies to is included in its name.


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

- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.

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

On Windows systems, if the fix was expanded to
<TEMP>\7.2.0-TIV-ITM_CTXA-IF0007, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>\7.2.0-TIV-ITM_CTXA-IF0007\KXA_wix64_tema_if0007.cab

Note: See section 7.0 Known problems and workarounds if you
recieve the error "itmpatch.exe has stopped working".

5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file (7.2.0-TIV-ITM_CTXA-IF0007.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>/7.2.0-TIV-ITM_CTXA-IF0007:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/7.2.0-TIV-ITM_CTXA-IF0007


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

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. From the <TEMP>/7.2.0-TIV-ITM_CTXA-IF0007 directory, run the
appropriate script based on the operating system.

On Windows systems:
> kxa_patchdepot_720if7.bat

On UNIX systems:
> kxa_patchdepot_720if7.sh <Tivoli Enterprise Monitoring Server Name>

This script is provided to do the copy of xa_dd_072000007.xml and
xa_dd.properties files from the <TEMP>/6.2.0-TIV-ITM_CTXA-IF0007
directory to the 072000000 and 072000003 versions of the agent
bundles in the Tivoli Enterprise Monitoring Services depot.

5. 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 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 xa
-n <Managed system name>
-v 072000007

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 XA
-n <Managed system name>
-v 072000007

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (xa), not three characters (kxa).
- 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 Reconfiguration of existing agent instances
--------------------------------------------------
Existing agent instances which perform remote farm monitoring (RFM)
must be reconfigured in order to set a new configuration parameter
which was introduced with APAR IV63025:

WSMan Authentication Mechanism

1. Local agent reconfiguration

Use the Manage Tivoli Enterprise Monitoring Server application
to reconfigure the agent, selecting an authentication mechanism
from the new list of WSMan Authentication Mechanisms to be used
to create remote PowerShell sessions used by the agent for
remote farm monitoring.

2. Remote agent reconfiguration

Log in to the Tivoli Enterprise Monitoring server, and
reconfigure the agent on the appropriate nodes where the remote
farm monitoring agent is running, using the following "tacmd"
commands. For more information on the "tacmd login" and
"tacmd configureSystem" commands, see the IBM Tivoli Monitoring
Administrator's Guide. Specify an authentication mechanism for
the new configuration parameter DEFAULT_CREDENTIALS.KXA_AUTH_MECH
from the following set of restricted values:
KXA_BASIC
KXA_CREDSSP
KXA_DEFAULT
KXA_DIGEST
KXA_KERBEROS
KXA_NEGOTIATE

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

> $CANDLEHOME/bin/tacmd listSystems -t xa

The output shows the Managed System Name for the XenApp agent
on the remote system to be updated. Use this value as the
target of the tacmd updateAgent command.

> $CANDLEHOME/bin/tacmd configureSystem -m <Managed system name>
-p <Properties to add or change>

Example configureSystem command:
> $CANDLEHOME/bin/tacmd configureSystem -m XA65-TEST1:XA -p DEFAULT_CREDENTIALS.KXA_AUTH_MECH="KXA_KERBEROS"

On Windows systems:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems -t xa

The output shows the Managed System Name for the XenApp agent
on the remote system to be updated. Use this value as the
target of the tacmd updateAgent command.

> %CANDLE_HOME%\bin\tacmd configureSystem -m <Managed system name>
-p <Properties to add or change>

Example configureSystem command:
> %CANDLE_HOME%\bin\tacmd configureSystem -m XA65-TEST1:XA -p DEFAULT_CREDENTIALS.KXA_AUTH_MECH="KXA_KERBEROS"

5.5 Agent support update
------------------------------
This fix (7.2.0-TIV-ITM_CTXA-IF0007) includes changes to the agent
support files which need to be installed. If you have already
installed these updates, there are no additional installation
steps. Otherwise, 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 (7.2.0-TIV-ITM_CTXA-IF0007.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 (kxa_tems_teps_tepd_if0007.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 one of the following options to install the application
support files.

A. Use the Self Describing Agent (SDA) capability.
With the self-describing agent capability, new or updated
IBM Tivoli Monitoring agents using IBM Tivoli Monitoring
V6.2.3 or later can become operational after installation
without having to perform additional product support
installation steps. To take advantage of this capability,
see Enabling self-describing agent capability at the hub
monitoring server in the IBM Tivoli Monitoring Installation
and Setup Guide. Also, see Self-describing monitoring
agents in the IBM Tivoli Monitoring Administrator's Guide.

Skip agent support update steps 5. and 6. if you use the SDA
capability.

B. 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. 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-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® 1.5 or Java 1.6 installation when
running the itmasi.sh or itmasi.bat script described
below.

GUI installation option
------------------------
The Application Support Installer can be started by using
one of the following commands from within the CD-ROM directory
where the setup.jar file 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, specify the CD-ROM directory,
not the component directory (i.e. TEMS). The installer can
install updates for multiple components at the same time.

Silent installation option
--------------------------
To use the silent installation option (-r), 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-IF0002.README".

On UNIX systems:
> ./itmasi.sh -h [CANDLEHOME]
[-silent]
{-r }
[-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 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. The Application Support Installer will
detect what IBM Tivoli Monitoring components are installed.
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 xa
07.20.00.07 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.

5.6 Sample reports update
--------------------------------------
Fix 7.2.0-TIV-ITM_CTXA-IF0004 and later patches include
enhancements to the agent sample reports. If you have already
installed these reports, there are no additional installation
steps. Installation is optional. Use the following steps to
install the new agent sample reports.

1. Transfer the appropriate archive file
(7.2.0-TIV-ITM_CTXA-IF0007.tar or .zip) to a temporary
directory on the same computer on which the Tivoli Common
Reporting server is installed.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
ITMfVE_XenApp_Reports.zip archive file that contains the
updated XenApp agent sample reports.

3. Expand the ITMfVE_XenApp_Reports.zip archive file using an
extract utility. This step creates a directory structure that
includes a subdirectory called ITMfVE_XenApp_Reports/KXA, with
the updated sample reports installer.

4. Follow the instructions in Importing and running Cognos reports
in the IBM Tivoli Monitoring for Virtual Environments,
Version 7.2, Monitoring for Virtual Environments User's Guide.
http://publib.boulder.ibm.com/infocenter/tivihelp/v61r1/topic/com.ibm.tivoli.itmvs.doc_7.2/xenapp/tcr_importingandrunningreports_xens.html

5.7 Prerequisite checker update
--------------------------------------
Fix 7.2.0-TIV-ITM_CTXA-LA0003 and later patches include fixes to
the agent prerequisite checker tool's remote deployment package
called XI-CHECKER. If you have already installed these
prerequisite checker fixes, there are no additional installation
steps. Use the following steps to add the updated package to the
remote deploy depot.

1. Transfer the appropriate archive file (7.2.0-TIV-ITM_CTXA-IF0007.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
ITMfVE_XenApp_prereqchecker.zip archive file that contains the
updated XenApp agent prerequisite checker tool.

3. Expand the ITMfVE_XenApp_prereqchecker.zip archive file using
an extract utility. This step creates a directory structure
that includes a subdirectory called ITMfVE_XenApp_Agent, with
the updated prerequisite checker.

4. To add the agent prerequisite checker 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>/ITMfVE_XenApp_Agent:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/ITMfVE_XenApp_Agent/WINDOWS/prereqchecker/Deploy


On Windows systems,
if the fix was expanded to <TEMP>\ITMfVE_XenApp_Agent:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\ITMfVE_XenApp_Agent\WINDOWS\prereqchecker\Deploy

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.

5.8 Sample custom logical navigator update
-------------------------------------------------
Fix 7.2.0-TIV-ITM_CTXA-IF0004 and later patches include a new
sample custom logical navigator to replace the three sample
custom logical navigators that are shipped with the Citrix
XenApp agent v7.2. If you have already installed the new sample
custom logical navigator, there are no additional installation
steps. Installation is optional. Use the following steps to
install the new sample custom logical navigator.

1. Transfer the appropriate archive file
(7.2.0-TIV-ITM_CTXA-IF0007.tar or .zip) to the Tivoli
Enterprise Monitoring Servers, Tivoli Enterprise Portal
Servers, or Tivoli Enterprise Portal Desktops. 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
ITMfVE_XenApp_logicalnav.zip archive file that contains the
XenApp agent sample custom logical navigator.

3. Expand the ITMfVE_XenApp_logicalnav.zip archive file using an
extract utility. This step creates a directory structure that
includes a subdirectory called Logical_Navigator, with
the sample custom logical navigator.

4. To import the custom logical navigator, use the
"tacmd importNavigator" command found in $CANDLEHOME/bin on
UNIX systems or in %CANDLE_HOME%\bin on Windows systems. For
more information on the "tacmd importNavigator" command, see
the IBM Tivoli Monitoring Administrator's Guide.

On UNIX systems,
if the fix was expanded to <TEMP>/Logical_Navigator:
> $CANDLEHOME/bin/tacmd importNavigator -x <TEMP>/Logical_Navigator/XenApp_Agent_7.2.xml
-s <TEPS_SERVER>
-u <TEPS_ADMIN_USER>
-p <TEPS_ADMIN_PASSWORD>

On Windows systems,
if the fix was expanded to <TEMP>\Logical_Navigator:
> %CANDLE_HOME%\bin\tacmd importNavigator -x <TEMP>\Logical_Navigator\XenApp_Agent_7.2.xml
-s <TEPS_SERVER>
-u <TEPS_ADMIN_USER>
-p <TEPS_ADMIN_PASSWORD>

where:
-x is the path to the file that contains the custom logical
navigator to be imported.
-s specifies which Tivoli Enterprise Portal Server to use.
-u is the identifier of the user to authenticate on the
Tivoli Enterprise Portal Server.
-p is the password of the user to authenticate on the Tivoli
Enterprise Portal Server.

5. To assign the custom logical navigator to a user, use the
"tacmd editUser" command found in $CANDLEHOME/bin on UNIX
systems or in %CANDLE_HOME%\bin on Windows systems. For more
information on the "tacmd editUser" command, see the IBM Tivoli
Monitoring Administrator's Guide.

On UNIX systems:
> $CANDLEHOME/bin/tacmd editUser -s <TEPS_SERVER>
-u <TEPS_ADMIN_USER>
-w <TEPS_ADMIN_PASSWORD>
-i <TEPS_USER>
-p NavigatorViews=<EXISTING VIEWS>,"XenApp Agent 7.2"

On Windows systems:
> %CANDLE_HOME%\bin\tacmd editUser -s <TEPS_SERVER>
-u <TEPS_ADMIN_USER>
-w <TEPS_ADMIN_PASSWORD>
-i <TEPS_USER>
-p NavigatorViews=<EXISTING VIEWS>,"XenApp Agent 7.2"

where:
-s specifies which Tivoli Enterprise Portal Server to use.
-u is the identifier of the user to authenticate on the
Tivoli Enterprise Portal Server.
-w is the password of the user to authenticate on the Tivoli
Enterprise Portal Server.
-i is the identifier of the user to assign the custom logical
navigator to.
-p is the property value listing the user's existing
navigator views (See 'tacmd viewUser -i <TEPS_USER> -v')
and adding the new "XenApp Agent 7.2" view.


6.0 Additional installation information
========================
For additional troubleshooting installation information, see the
itmpatch.log in the patchlogs directory in <CANDLEHOME>.

6.1 Installation instructions for agent baroc file
-----------------------------------------------------
Fix 7.2.0-TIV-ITM_CTXA-IF0004 and later fixes include changes to
the agent baroc files that must be installed. If you have already
installed these baroc files, there are no additional installation
steps. If not, refer to IBM Tivoli Monitoring, Version 6.2.2,
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 XA

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 XA

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

When the agent update is successful, the agent version is:
07.20.00.07

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

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 -t xa

For example:
> $CANDLEHOME/bin/cinfo -t xa

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

kincinfo -t xa

For example:
> %CANDLE_HOME%\InstallITM\kincinfo -t xa

************ Monday, March 21, 2015 7:11:11 PM **************
User : Administrator Group : NA
Host Name : WinServer Installer : Ver: 062204000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product inventory

PC APPLICATION SUPPORT DESC PLAT APP VER BUILD INSTALL DATE

XA Monitoring Agent for Citrix XenApp WICMS 07.20.00.07 201503271651 <date time>
XA Monitoring Agent for Citrix XenApp WICNS 07.20.00.07 201503271651 <date time>
XA Monitoring Agent for Citrix XenApp WIXEB 07.20.00.00 201302242057 <date time>
XA Monitoring Agent for Citrix XenApp WIXEW 07.20.00.07 201503271651 <date time>


7.0 Known problems and workarounds
=========================
Problem: itmpatch.exe might fail with the error "itmpatch.exe has
stopped working" on some Windows agent machines with Tivoli
Monitoring agent framework less than version 6.2.2 Fix Pack 9.
Workaround: Use IBM Tivoli Monitoring Version 6.2.2 Fix Pack 9
(6.2.2-TIV-ITM-FP0009) or higher to upgrade the installed
components on the affected Windows agent machine.


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


9.0 Copyright and trademark information
==================================
A current list of IBM trademarks is available on the Web at "Copyright
and trademark information" at www.ibm.com/legal/copytrade.shtml.


10.0 Notices
=======

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.

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

Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.

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.

Citrix and XenApp are trademarks of Citrix Systems, Inc. and/or one or
more of its subsidiaries, and may be registered in the United States
Patent and Trademark Office and in other countries.

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.