ITCAM Agent for SAP Applications, 7.1.0-TIV-ITM_SAP-IF0001

Downloadable files


Abstract

This fix resolves the APARs and defects listed in the "Problems Fixed" section below.

Download Description

Copyright International Business Machines Corporation 2012.

All rights reserved.


Component: IBM(R) Tivoli(R) Composite Application Manager Agent for
SAP Applications, Version 7.1.0

Component ID: 5724B97SO

Interim Fix: 0001, 7.1.0-TIV-ITM_SAP-IF0001

Date: November 05, 2012

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 in IF0001
============================
The following problems are addressed by this fix.

2.1 APARs
----------
APAR: IV18311
Abstract: SAP ON AIX HAS A DIFFERENT STYLE DATE FORMAT
Additional Information: SAP Gateway Connections Request Time
displays an incorrect value on the Tivoli Enterprise Portal
when the SAP system is on an AIX operating system.

APAR: IV14414
Abstract: VALUES OF SYSTEM_DESCRIPTION ATTRIBUTE ON NON-UNICODE SAP
SYSTEMS IS NOT CORRECT
Additional Information: The agent does not display the value of
System_Description correctly when it runs on Russian (RU)
systems.

APAR: IV10144
Abstract: SAP AGENT CONSUMING HIGH CPU
Additional Information: The agent consumes high memory on the SAP
system because of a heavy workload that causes ABAP memory
dumps such as "TSV_TNEW_PAGE_ALLOC_FAILED". The agent was
enhanced to adjust the duration of data collection by using
two new configuration parameters for STATISTICS COLLECTION and
one new parameter for IDOCS COLLECTION.

Follow these steps to modify the values of these two new
parameters:

(1) STAT_READ_MAX_HISTORY:
The max history is in hours. This variable is used
to collect statistical data from the SAP system. If not
specified, by default the SAP API used by the agent collects
data for the last 6 hours.

Example: For 2 HOURS
PARAM NAME = STAT_READ_MAX_HISTORY
VALUE CHAR = <leave blank>
VALUE INT = 2

Example: For 5 HOURS
PARAM NAME = STAT_READ_MAX_HISTORY
VALUE CHAR = <leave blank>
VALUE INT = 5

(2) STAT_READ_API_INTERVAL:
The value of this parameter is seconds. To collect statistical
data for the STAT_READ_MAX_HISTORY duration, the agent calls
the SAP API and uses the STAT_READ_API_INTERVAL to collect
complete data in samples. By calling the SAP API in short
intervals as specified in STAT_READ_API_INTERVAL, low memory
issues are avoided during data collection. If not specified,
the default is five minutes.

Example: For 60 SECONDS or 1 min
PARAM NAME = STAT_READ_API_INTERVAL
VALUE CHAR = <leave blank>
VALUE INT = 60

Example: For 180 SECONDS or 3 mins
PARAM NAME = STAT_READ_API_INTERVAL
VALUE CHAR = <leave blank>
VALUE INT = 180

Use the following steps to modify the "/ibmmon/itm_cnfg" table:
1: Log on to the SAP system through the SAP GUI.
2: Run the 'SE16' transaction code.
3: Enter '/IBMMON/ITM_CNFG' as the table name.
4: Press F5 to create a new entry.
5.a. In the PARM NAME field, enter 'STAT_READ_MAX_HISTORY' and
in the VALUE INT field, enter the number (default is 6).
OR
5.b. In the PARAM NAME field, enter 'STAT_READ_API_INTERVAL'
and in the VALUE INT field, enter the number (default
is 300).
6. Press Save or CNTRL+S.
7. Press F3 to go to back one screen.

Use the following steps to modify the values of the IDOCS
Configurable parameter:

(3) IDOCS_READ_INTERVAL:
The value of the API Interval is in seconds. To collect IDOCS
data for a Sample duration, the SAP API is called
'IDOCS_READ_INTERVAL' to collect complete data. Calling the SAP
API in short intervals as specified in IDOCS_READ_INTERVAL
avoids low memory issues during data collection.
If not specified, the default is five minutes

Example: For 60 SECONDS or 1 min
PARAM NAME = IDOCS_READ_INTERVAL
VALUE CHAR = <leave blank>
VALUE INT = 60

Example: For 180 SECONDS or 3 mins
PARAM NAME = IDOCS_READ_INTERVAL
VALUE CHAR = <leave blank>
VALUE INT = 180

Use the following steps to modify the "/ibmmon/itm_cnfg" table:
1: Log on to the SAP system through the SAP GUI.
2: Run the 'SE16' transaction code.
3: Enter '/IBMMON/ITM_CNFG' as the table name.
4: Press F5 to create a new entry.
5. In the PARM NAME field, enter 'IDOCS_READ_INTERVAL' and in
the VALUE INT filed, enter the number(default is 6) .
6. Press Save or CNTRL+S.
7. Press F3 to go to back one screen.

APAR: IV01415
Abstract: SITUATION EVENT FOR "R3_ALERT_SYSTEM_UP" RAISED ON
UNEXPECTED SUBNODE,CAUSING THE DOWN EVENT NOT TO BE CLEARED.
Additional Information: When the "Lost connection to SAP system"
alert appears in the CCMS alerts, the agent fires the
"R3_Alert_System_Down_LI" situation. Later, when the system is
Online the "Reconnect to SAP system" alert is generated on
Another instance or subnode and as a result, the event for
"R3_Alert_System_Down_LI" cannot close automatically.
To close the situation when the up situation was triggered, the
display item must not have a "message" value.

APAR: IV15697
Abstract: ZERO VALUES IN SAP WORKSPACE FOR FRONT END NETWORK TIMES &
GUI TIMES
Additional Information: After applying 6.2.0-TIV-ITM_SAP-IF007 /
IF0014 the values of the Front-End Network Time and GUI-Time
attributes are always zero in the Transaction Performance
workspace. This issue occurs because the agent is using an old
SAP API.

APAR: IV27968
Abstract: SAP AGENT PI SUBNODE DOES NOT SHOW UP
Additional Information: The issue is related to SAP table T000. A
value of XI-Client must exist in this table. This issue is
fixed and new ABAP code does not depend on this table entry.

APAR: IV28119
Abstract: XML MESSAGE NOT SHOWING UP IN TEP VIEW
Additional Information: The issue is related to SAP agent 7.1. XML
Messages not showing up on Tivoli Enterprise Portal workspace.
S_XMB_MONI authorization object need to be added to see the
data of XML messages monitoring. This is fixed in this release.

2.2 Defects
------------
Defect: 190112
Abstract: Inconsistent attribute label for Buffer Performance
Additional Information: In the Buffer Performance workspace, the
"Directory Free Percent" attribute must use a % symbol in the
attribute caption because other attributes in the workspaces
used this symbol.

Defect: 190106
Abstract: Inconsistent listing of workspace for "Transport Request"
Additional Information: Sequence of the Transport Request workspace
is incorrect.

Defect: 189088
Abstract: Data missing for qRFC Saved Inbound Queue Overview

Defect: 189085
Abstract: TEMS and TEPS server upgrade is not working.

Defect: 188799
Abstract: Tranpsort import failed for 4.6 SAP System

Defect: 188428
Abstract: Dumps getting generated in Agent log
Additional Information: Dumps are generating in the agent log
file for Windows(R) and non-Windows systems.

Defect: 187269
Abstract: DEV-PR: SAP Agent TCR reports integrating in IF0001

Defect: 186801
Abstract: CVT1IF1:SWG Inventory Tag files is not updated
Additional Information: After applying the 710IF001 patch, SWG
Inventory Tag files are not being updated for Fix Pack 1.

Defect: 186268
Abstract: CVT1IF1:SDA is not working for 710IF001 patch
Additional Information: After applying the 710IF001 patch, SDA files
are not avalaible in Interim Fix 1.

Defect: 185556
Abstract: FNLR: Reconciling is not happening at TADDM for SAP IDLM
Book.

Defect: 184469
Abstract: FNLR: Unable to launch TEP from TBSM
Additional Information: While loading workspaces, the following
error occurs: KFWITM388E-The link target cannot be found.

Defect: 182474
Abstract: ksa agent hang issue/ unable to start or stop sometime

Defect: 180938
Abstract: SVT:13-Status of Remove system through TEP/tacmd is
inconsistent.
Additional Information: The agent instance is removed, but the
deployment status is in retrial state. If you retry
more than 3 times, the remove system status fails.

Defect: 177733
Abstract: SVT10: Agent failed to start after reboot on HP-UX

Defect: 92240
Abstract: Wrong host ip address display in a IPv6 SAP710 env
Additional Information: In 'Instance Configuration' 'workspace in
an IPv6 environment, an incorrect string is displayed in the
'Instance Host IP Address' column.

Defect: 91183
Abstract: DEV4: terminal column trancate in ipv6 env
Additional Information: In the KSA Active Users workspace, the
"Terminal" column that contains the IPv6 address is
truncated, because the length of 20 in docksa must be
updated to 64.

Defect: 89710
Abstract: Dev621: Wrong topology in
<local_SID>-<remote_SID>_CCMS_alerts
Additional Information: In the <local_SID>-<remote_SID>_CCMS_alerts:Grp
managed system, the currect state topology view is not
displayed, because the number attribute is incorrect.

Defect: 81226
Abstract: CCMS Current State does not work in central CCMS environment
Additional Information: The problem is that the ABAP code is not
generating original nodes correctly for the following subnodes:
"<local_SID>-<remote_SID>_CCMS_alerts:Grp"
and "<local_SID>-<local_SID>_CCMS_alerts:Grp"

2.3 Enhancements
----------------

Enhancement: 187474
Abstract: Support for PI/XI 7.0 SAP system

2.4 Superseded fixes
---------------------
NONE

3.0 Architecture and prerequisites
===================================
This fix is supported on all operating systems listed in the IBM Tivoli
Composite Application Manager Agent for SAP Applications User's Guide
, Version 7.1

The following website contains the latest certification information:
Software Product Compatibility Reports (SPCR)
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html

You can also find system requirements for ITCAM for Applications 7.1 at
www-01.ibm.com/support/knowledgecenter/?lang=en#!/SS3JRN_7.2.0/com.ibm.itcama.doc_7.1/prerequisites/apps71_systemreqs.html

ITCAM for Applications 7.1 Information Center:
www-01.ibm.com/support/knowledgecenter/?lang=en#!/SS3JRN_7.2.0/com.ibm.itcama.doc_7.1/welcome_itcamfapps71.html

3.1 Prerequisites for this fix
------------------------------
The prerequisite level for this fix is as follows:
- IBM Tivoli Composite Application Manager Agent for SAP Applications:
SAP Agent, Version 7.1.0

- IBM Tivoli Monitoring, Version 6.2.2 FP2

Because this fix is cumulative, it can be installed on any fix level
for this version, release, and modification level later than the
prerequisite.


4.0 Image directory contents
=============================
This fix image contains the following files:
- 7.1.0-TIV-ITM_SAP-IF0001.README - This README file
- 7.1.0-TIV-ITM_SAP-IF0001.tar - Fix archive .tar format
- 7.1.0-TIV-ITM_SAP-IF0001.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 environment.

The fix archive file contains the following files:
7.1.0-TIV-ITM_SAP-IF0001/ksa_winnt_tema_IF0001.cab
7.1.0-TIV-ITM_SAP-IF0001/ksa_wix64_tema_IF0001.cab
7.1.0-TIV-ITM_SAP-IF0001/KSAWINNT.dsc
7.1.0-TIV-ITM_SAP-IF0001/KSAWIX64.dsc
7.1.0-TIV-ITM_SAP-IF0001/ksaaix523.dsc
7.1.0-TIV-ITM_SAP-IF0001/ksaaix526.dsc
7.1.0-TIV-ITM_SAP-IF0001/ksahpi116.dsc
7.1.0-TIV-ITM_SAP-IF0001/ksali6263.dsc
7.1.0-TIV-ITM_SAP-IF0001/ksals3266.dsc
7.1.0-TIV-ITM_SAP-IF0001/ksalx8266.dsc
7.1.0-TIV-ITM_SAP-IF0001/ksasol283.dsc
7.1.0-TIV-ITM_SAP-IF0001/ksasol286.dsc
7.1.0-TIV-ITM_SAP-IF0001/ksasol606.dsc
7.1.0-TIV-ITM_SAP-IF0001/sa_dd_07100000.xml
7.1.0-TIV-ITM_SAP-IF0001/sa_dd_07100001.xml
7.1.0-TIV-ITM_SAP-IF0001/sa_dd.properties
7.1.0-TIV-ITM_SAP-IF0001/ABAP/K710_00104.ITM
7.1.0-TIV-ITM_SAP-IF0001/ABAP/R710_00104.ITM
7.1.0-TIV-ITM_SAP-IF0001/ABAP/K710_00104U.ITM
7.1.0-TIV-ITM_SAP-IF0001/ABAP/R710_00104U.ITM
7.1.0-TIV-ITM_SAP-IF0001/ABAP/K710_00104_DELETE.ITM
7.1.0-TIV-ITM_SAP-IF0001/ABAP/R710_00104_DELETE.ITM
7.1.0-TIV-ITM_SAP-IF0001/ksa_tems_teps_tepd_IF0001.tar
7.1.0-TIV-ITM_SAP-IF0001/ksa_tems_teps_tepd_IF0001.zip
7.1.0-TIV-ITM_SAP-IF0001/ksa_aix523_tema_IF0001.tar
7.1.0-TIV-ITM_SAP-IF0001/ksa_aix526_tema_IF0001.tar
7.1.0-TIV-ITM_SAP-IF0001/ksa_hpi116_tema_IF0001.tar
7.1.0-TIV-ITM_SAP-IF0001/ksa_li6263_tema_IF0001.tar
7.1.0-TIV-ITM_SAP-IF0001/ksa_lx8266_tema_IF0001.tar
7.1.0-TIV-ITM_SAP-IF0001/ksa_ls3266_tema_IF0001.tar
7.1.0-TIV-ITM_SAP-IF0001/ksa_sol283_tema_IF0001.tar
7.1.0-TIV-ITM_SAP-IF0001/ksa_sol286_tema_IF0001.tar
7.1.0-TIV-ITM_SAP-IF0001/ksa_sol606_tema_IF0001.tar

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 <CANDLEHOME> symbol 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 CANDLEHOME
environment variable to the IBM Tivoli Monitoring installation
directory.

For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME

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

5.2 Local agent update
--------------------------
1. Transfer the appropriate archive file (7.1.0-TIV-ITM_SAP-IF0001.tar
or .zip) to a temporary directory on the system that contains the
agent to be updated. For the purpose of this README, the
<TEMP> symbol 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 supported
operating systems.

3. Use the "itmpatch" command to install the fix for the operating
system for that agent. For more information on the "itmpatch"
command, see section [6.2].

On UNIX systems, if the fix was expanded to
<TEMP>/7.1.0-TIV-ITM_SAP-IF0001, the install command is:

> <TEMP>/7.1.0-TIV-ITM_SAP-IF0001/itmpatch -h <CANDLEHOME>
-i <TEMP>/7.1.0-TIV-ITM_SAP-IF0001/ksa_xxxxxx_tema_if0001.tar

where:
- xxxxxx corresponds to the value in the first column
returned by the ./cinfo -i command.

In the following example, the file is
"ksa_li6243_tema_if0001.tar".
> ./cinfo -i
[Monitoring Agent for Your Product]
[li6243 Version: 07.01.00.01]

On Windows systems, if the fix was expanded to
<TEMP>\7.1.0-TIV-ITM_SAP-IF0001, the install command is:

For Windows 32-bit
> <TEMP>\7.1.0-TIV-ITM_SAP-IF0001\itmpatch -h <CANDLEHOME>
-i <TEMP>\7.1.0-TIV-ITM_SAP-IF0001\ksa_winnt_tema_if0001.cab

For Windows 64-bit
> <TEMP>\7.1.0-TIV-ITM_SAP-IF0001\itmpatch -h <CANDLEHOME>
-i <TEMP>\7.1.0-TIV-ITM_SAP-IF0001\ksa_wix64_tema_if0001.cab

5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file (7.1.0-TIV-ITM_SAP-IF0001.tar
or .zip) to a temporary directory on the IBM Tivoli Enterprise
Monitoring Server system. For the purpose of this README, the
<TEMP> symbol 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
operating systems.

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 Command Reference.

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

On Windows systems,
if the fix was expanded to <TEMP>\7.1.0-TIV-ITM_SAP-IF0001:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i
<TEMP>\7.1.0-TIV-ITM_SAP-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. 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. After "tacmd addBundles.." from step 3 above, control files
on the Tivoli Enterprise Monitoring Server and the
Tivoli Enterprise Portal Server must be updated.
These updates must be done manually.

a. Tivoli Enterprise Monitoring Server update
The sa_dd_07100001.xml and sa_dd.properties files must be
copied from the <TEMP>/7.1.0-TIV-ITM_SAP-IF0001 directory to
the 071000000 version of the Tivoli Enterprise Monitoring
Services depot.

Two scripts are provided to make these copies and are
in the fix <TEMP>/7.1.0-TIV-ITM_SAP-IF0001 directory after
the expansion of the tar or zip file:

ksa_patchdepot.bat - Windows
ksa_patchdepot.sh - UNIX

From the <TEMP>/7.1.0-TIV-ITM_SAP-IF0001 directory, run the
appropriate script based on the operating system. The script
output contains details about the copies being made.

b. Tivoli Enterprise Portal Server update
Resource files must be copied from the
<TEMP>/7.1.0-TIV-ITM_SAP-IF0001 directory to the Tivoli
Enterprise Monitoring Portal directory.

Two scripts are provided to make these copies and are
in the fix <TEMP>/7.1.0-TIV-ITM_SAP-IF0001 directory after
the expansion of the tar or zip file:

ksa_patch_resource_teps.bat - Windows
ksa_patch_resource_teps.sh - UNIX

From the <TEMP>/7.1.0-TIV-ITM_SAP-IF0001 directory, run the
appropriate script based on the operating system. The
script output contains details about the copies being made.

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 Command Reference.

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 sa
-n <Managed system name>
-v 07100001

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 sa
-n <Managed system name>
-v 07100001

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (sa), not three characters (ksa).
- 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
------------------------------
This fix (7.1.0-TIV-ITM_SAP-IF0001) includes changes to the agent
support files that must be installed. If you installed these updates,
there are no additional installation steps. If you did not install
these updates, 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.1.0-TIV-ITM_SAP-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 (ksa_tems_teps_tepd_if0001.tar or .zip)
that contains the updates for the 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(ASI) GUI or the silent
installation method to install 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.

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.

5. The next panel presented by the Application Support Installer
asks for the selection of Tivoli Monitoring components to which
you want to add application support. For this fix, check or
clear the check boxes as follows:

[checked | unchecked] - Tivoli Enterprise Monitoring Server (TEMS)
[checked | unchecked] - Tivoli Enterprise Portal Server (TEPS)
[checked | unchecked] - Tivoli Enterprise Desktop Client (TEPD)

Continue through the remaining GUI panels selecting SAP Agent
07.10.00.01 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.5 Installing SAP agent transport
------------------------------------
This procedure installs the SAP transport into the SAP system. You
are not required to uninstall the previous transport before
installing this transport.

1. Go to the ABAP directory in the location where you expanded the
fix archive file.

2. Copy the transport files into the SAP environment as follows:
a. The following three sets of transport files are in the
ABAP directory of the SAP agent fix archive:

1) K710_00104.ITM and R710_00104.ITM
These files are non-Unicode versions of the transport.

2) K710_00104U.ITM and R710_00104U.ITM
These files are Unicode versions of the transport.

3) K710_00104_DELETE.ITM and R710_00104_DELETE.ITM
These transport files remove the ABAP code. Do not import
the DELETE transport unless you stop using the product
entirely and want to remove the transports from your SAP
systems.

b. Determine which transport is required for your SAP system:
Unicode or non-Unicode.

c. Copy your transport files to the SAP Transport System data
directory as follows:
non-Unicode transport
1) Copy the K710_00104.ITM file to the cofiles directory.
2) Copy the R710_00104.ITM file to the data directory.
or
Unicode transport
1) Copy the K710_00104U.ITM file to the cofiles directory.
2) Copy the R710_00104U.ITM file to the data directory.

3. Run the following non-Unicode and Unicode commands where:
SID Target SAP : system ID
PROFILE_NAME : Name of the tp profile file
nnn : Number for the target client where the agent is to run
non-Unicode
tp addtobuffer ITMK710_00104 SID
pf=\usr\sap\trans\bin\PROFILE_NAME
tp import ITMK710_00104 SID client=nnn U16
pf=\usr\sap\trans\bin\PROFILE_NAME
Unicode
tp addtobuffer ITMK710_00104U SID
pf=\usr\sap\trans\bin\PROFILE_NAME
tp import ITMK710_00104U SID client=nnn U16
pf=\usr\sap\trans\bin\PROFILE_NAME

Alternately, you can use the SAP STMS transaction to import the
transport requests. Ensure that the Import Transport Request Again
and the Overwrite Objects in Unconfirmed Repairs options are
checked on the Import Options tab of the Import Transport Request
window.

6.0 Additional installation information
========================================

6.1 Installation instructions for agent baroc file
------------------------------------------------------

This fix (7.1.0-TIV-ITM_SAP-IF0001) includes changes to the agent
baroc files that must be reinstalled. If you have already
installed these baroc files, there are no additional installation
steps. If you have not installed the files, see the "IBM Tivoli
Monitoring, Version 6.2.2: Installation and Setup Guide" under
"Installing monitoring agent baroc files on the event server" in the
"Installing the IBM Tivoli Enterprise Console Event Synchronization"
section for more information.

6.2 Additional information on using the 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 path must
include the drive letter.

6.3 Verifying the update
------------------------
1. To verify that the agent was updated correctly, use the tacmd
command to view the current version of the agent after the agent
is restarted. You are required to log in to a Tivoli Enterprise
Monitoring Server before 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 sa

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 sa

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

When the agent update is successful, the agent version is
07.10.00.01

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

When the agent update is successful, the agent version is
07.10.00.01

After the agent is restarted, you can also use the GUI to verify
that the agent was successfully updated.

For the agent on Windows systems, the version number is
07.10.00.01
For the agent on UNIX systems, the version number is
07.10.00.01

2. To verify that the agent support files were updated correctly,
use the kincinfo command on Windows systems or the cinfo command
on Linux(R) 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 date of the build displayed might not be accurate. This is
a known problem.

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

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

>kincinfo -i
************ Tuesday, September 27, 2012 10:07:08 AM *********
User : Administrator Group : NA
Host Name : TIVE38 Installer : Ver: 062300000
CandleHome : E:\IBM\ITM
Installitm : E:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory

Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal
Server, and Tivoli Enterprise Portal Desktop update:

SA IBM Tivoli Composite Application Manager Agent for SAP Applications
WINNT Version: 07.10.00.01 Build: 201210300909

SA IBM Tivoli Composite Application Manager Agent for SAP Applications
WINNT Version: 07.10.00.01 Build: 201210300909

SA IBM Tivoli Composite Application Manager Agent for SAP Applications
WINNT Version: 07.10.00.00 Build: 21691

SA IBM Tivoli Composite Application Manager Agent for SAP Applications
WINNT Version: 07.10.00.01 Build: 201210300909

7.0 Known problems and workarounds
===================================


Abstract: SVT 3IF1: IDML book certification fails in case of
multiple Ins
Problem: If you generate the IDML book in a multiple
instance environment, the certification tool fails while
certifying the IDML book.

Workaround: Before you generate the IDML book,
complete the following steps:
1. Run the /n/ibmmon/itm_config transcation on the SAP
server side.
2. Select the SAP Instance Monitoring.
3. Clear all other instances except the central instance.
4. Generate the IDML book.
5. When you are finished with the IDML book, you can reselect
the cleared instances in step 3.

8.0 Additional product information
==================================

ABAP Transport Compatibility:
------------------------------
Each fix includes an updated agent executable
program (ksaagent or ksaagent.exe) and an updated ABAP transport.
Install both programs to obtain the highest level of support.

In some situations, you cannot install
a new transport immediately because of change control processes on the
mySAP systems. In these situations, sometimes you can run a new agent
executable with a prior version of the ABAP transport. This section
explains when it is possible to run a newer agent executable program
with an older version of an ABAP transport.

Note: The mySAP agent does not run correctly if not installed with
a compatible level of the transport.

Fix Level Delivered Transport Minimum Transport Level
----------- ------------------- -----------------------
IF0001 ITMK710_00104 ITMK710_00103




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.

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.

Prerequisites

IBM Tivoli Composite Application Manager Agent for SAP Applications, Version 7.1.0

Installation Instructions

Please refer to the 7.1.0-TIV-ITM_SAP-IF0001.README contained in the description section above for general installation instructions

URL LANGUAGE SIZE(Bytes)
7.1.0-TIV-ITM_SAP-IF0001.tar English 137728000
7.1.0-TIV-ITM_SAP-IF0001.zip English 91740520
7.1.0-TIV-ITM_SAP-IF0001.README English 39128
7.1.0-TIV-ITM_SAP-IF0001.README.DEU German 45491
7.1.0-TIV-ITM_SAP-IF0001.README.FR French 43942
7.1.0-TIV-ITM_SAP-IF0001.README.JPN Japanese 46632
7.1.0-TIV-ITM_SAP-IF0001.README.PTB Brazilian Portuguese 41539

Download package


Problems solved

IV18311; IV14414; IV10144; IV01415; IV15697; IV27968;

Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central (FC)?
7.1.0-TIV-ITM_SAP-IF0001.tar 6 Nov 2012 English 137728000 FC
7.1.0-TIV-ITM_SAP-IF0001.zip 6 Nov 2012 English 91740520 FC
7.1.0-TIV-ITM_SAP-IF0001.README 6 Nov 2012 English 39128 FC
7.1.0-TIV-ITM_SAP-IF0001.README.DEU 6 Nov 2012 German 45491 FC
7.1.0-TIV-ITM_SAP-IF0001.README.FR 6 Nov 2012 French 43942 FC
7.1.0-TIV-ITM_SAP-IF0001.README.JPN 6 Nov 2012 Japanese 46632 FC
7.1.0-TIV-ITM_SAP-IF0001.README.PTB 6 Nov 2012 Brazilian Portuguese 41539 FC

Product Alias/Synonym

SAP agent 7.1.0 IF0001

Problems (APARS) fixed
IV18311, IV14414, IV10144, IV01415, IV15697, IV27968

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Composite Application Manager for Applications
ITCAM Agent for mySAP -5724B97SO

Software version:

7.1

Operating system(s):

AIX, AIX 64bit, HP-UX, Linux, Solaris, Windows, Windows 2003 server, Windows 2008 server

Software edition:

All Editions

Reference #:

4033552

Modified date:

2014-07-16

Translate my page

Machine Translation

Content navigation