ITCAM Agent for SAP Applications,7.1.1-TIV-ITM_SAP-FP0004

Download Description

Copyright International Business Machines Corporation 2017.
All rights reserved.

Component: IBM(R) Tivoli(R) Composite Application Manager Agent for SAP
Applications, Version 7.1.1 Fix Pack 0004

Component ID: 5724B97SO

Fix: Fix Pack 0004 , 7.1.1-TIV-ITM_SAP-FP0004

Date: Nov 03, 2017

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 pack resolves the APARs and defects listed in the 'Problems fixed'
section below.
This fix pack also includes the superseded fixes listed in section 2.4.

2.0 Problems fixed in 7.1.1-TIV-ITM_SAP-FP0004
==============================================
The following problems are addressed by this fix pack.

2.1 APAR's:
-----------
APAR: IV95558
Abstract: SAP agent 7.1.1.2 Hanging right after log entry
Additional Information: This APAR is opened in order to reduce performance issue
in the '/IBMMON/ITM_HOSTS' function module as the SAP Agent took 20 - 35 minutes
to fetch the data from '/IBMMON/ITM_HOSTS' and the agent would hang during
execution. To handle this performance issue, the 'ITM_UPT_STATFILE' background
job is scheduled for fetching data.


2.2 Defects:
------------

Defects:121867
Abstract: SAP Agent is not displaying count of instances down on TEP under
"System Summary" view.
Additional Information: In the Instances Down attribute group, the count for
number of instances that are down was displayed as '0'.

Defects:124233
Abstract: There are 6 Expert Advise pages which are not shown in original
English build.
Additional Information: 6 Expert Advise help pages were available for other
languages but not visible in English language.

Defects:124929
Abstract: Description for Instance status attribute is incomplete.
Additional Information: In the Instance Configuration attribute group, the
description for the Instance Status attribute was incomplete. Newly added
status, such as Connection Failed, Unknown, and Passive were not mentioned
in the description.

2.3 Enhancements:
-----------------

Enhancement:
Abstract: SAP Agent should not provide multiple alerts in case of User ID
Locked/ Relocked
Additional Information: This is with reference to PMR 81852,442,000 – ITCAM for
SAP sending duplicate alerts. When a situation is created for User ID locked or
relocked, it gets triggered for all the instances that are causing duplication.
Because the Logon Information attribute group is fetching data at each ":ins"
node. However the User Id attribute is a system level attribute. In case of SAP
System when the user is locked, it is locked at a system level specific to
client and not at any instance. To overcome this issue the System Logon
Information attribute group is introduced, which fetches the data at system
level. This attribute group is designed for this situation only.

Enhancement: 106442
Abstract: This is with reference to the PMR 83371,004,000 - ITM SAP Monitoring
Agent should support SNC (Secured Network Communication) connection.
Additional Information: Additional parameters are required for SNC (Secured
Network Communication). Provision to include required additional parameters
during agent configuration is added.
Modified Configuration panel will contain below options for SNC -
1. Enable/Disable SNC
2. SNC Security Level
3. Client/Agent SNC Name
4. Partner/SAP Server SNC Name
5. SAP Cryptolibrary Path

Use of SNC (Secured Network Communication) configuration:
A) SNC specifications can be used with mySAP agent. The new parameters are as
follows:

sap_conn.sap_snc_mode=true
sap_snc_mode1.sap_snc_qop=<QOP value default is 8 >
sap_snc_mode1.sap_snc_client=<Client SNC Name>
sap_snc_mode1.sap_snc_server=<Server SNC Name>
sap_snc_mode1.sap_snc_library=<Crypto library path >

For Remote deployment of agent with SNC configuration the command should
be used with above mentioned paramaeters.
Example:
tacmd addsystem -t sa -n Primary:NT -p INSTANCE=P10
sap_conn.sap_conn_mode=appsrvmode
sap_appsrvmode.sap_hostname=10.77.97.158
sap_appsrvmode.sap_systemno=00
sap_logon.sap_clientno=200
sap_logon.sap_userid=IBMMON_AGENT
sap_logon.sap_password=ITMMYSAP
sap_logon.sap_language=EN
sap_conn.sap_snc_mode=true
sap_snc_mode1.sap_snc_qop=8
sap_snc_mode1.sap_snc_client=p:CN=AGT,OU=IBM,O=IBM,C=IN
sap_snc_mode1.sap_snc_server=p:CN=P35,OU=ITCAM,O=Persistent,C=IN
sap_snc_mode1.sap_snc_library=/sap/sec/libsapcrypto.so

B) Guidelines for SNC usage
1. It is manadatory to install SNC related certificates on Agent system
so that agent can connect to SAP system.
2. By default the SNC mode is disabled while ocnfiguring the agent.
3. The values of parameters Client/Agent SNC Name and Partner/SAP Server
SNC Name should not contain spaces in it.

2.4 Superseded fixes:
---------------------
7.1.1.3-TIV-ITM_SAP-IF0001
7.1.1-TIV-ITM_SAP-FP0003
7.1.1-TIV-ITM_SAP-FP0002
7.1.1.1-TIV-ITM_SAP-IF0002
7.1.1.1-TIV-ITM_SAP-IF0001
7.1.1-TIV-ITM_SAP-FP0001
7.1.1-TIV-ITM_SAP-IF0001
---------------------

2.5 APARS, Defects and Enhancements included from superseded fixes:
-------------------------------------------------------------------

------------------------------------------
7.1.1-TIV-ITM_SAP-FP0003-IF0001
------------------------------------------

APARs:
------
APAR:IV95238
Abstract:SAP Agent is showing fake alerts for instance down
Additional Information:SAP Agent shows situation/alert for instance down though
instance is up and running.Required changes are made for triggering
situation/alert when instance is actual down. New status is introduced when
instance is running but there is a connectivity problem between SAP server and
agent.

APAR:IV93661
Abstract:SAP ABAP syslog entries getting truncated
Additional Information:Syslog data shows truncated values for some basis version
and SP level. Required changes are made to incorporate SAP standard Subroutine
changes from Basis 700 SP17 and Basis 701 SP5 onwards.

Known problems and workarounds
--------------------------------
Defects:120588
Abstract:HDC View Names are Incorrect for SAP qRFC Inbound Queues and SAP qRFC
Outbound Queues Attribute group
Problem:View names are not coming as per object names due to length constrains.
Workaround: There is no work around right now.

------------------------------------------
7.1.1-TIV-ITM_SAP-FP0003
------------------------------------------

APAR's:
-------
APAR: IV85498
Abstract: Mysap Agent gets error after upgrade of sap erp system
to SAP Basis 740 SP12 in procedure /IBMMON/ITM_NEW_CCMS_ALERTS
Additional Information: The /IBMMON/ITM_NEW_CCMS_ALERTS function
module does not support SAP Basis 740 SP12. The updates are made
to support SAP Basis 702 SP17, SAP Basis 730 SP13, SAP Basis 731 SP16,
SAP Basis 740 SP11, and SAP Basis 750

APAR: IV83334
Abstract: SAP AGENT 7.11.2.0 showing EMPTY SAP AGENT SYSTEM SUMMARY
Additional Information: The central instance identification has changed
in SAP Basis 750, and later. The required updates are made to identify
central instance in SAP systems with SAP Basis 750 and later to resolve
this issue that is related to an empty SAP AGENT System summary.

APAR: IV81985
Abstract: The SAP agent is not monitoring the system and service user types
Additional Information: The System user and Service user are now included
for monitoring.


Defects:
--------
Defects:112608
Abstract: Missing/Incorrect information to be handled for KSATRANST &
KSASDETAIL attribute groups
Additional Information: The required corrections were made in the KSATRANST
& KSASDETAIL attribute groups for displaying correct information on the
Tivoli Enterprise Portal.

Defects:108186
Abstract: Documentation should be updated with the DB HOST/ HOST name
permissible length details for Agent
Additional Information: The SAP Agent Installation Guide is updated to add
the limitation about the database host name, which can contain up to 13
characters.

Defects:112553
Abstract: Attribute groups are missing while creating situation
from navigator item
Additional Information: This issue is fixed after the necessary corrections
were made so that attribute groups are listed while creating a situation
when you right-click the navigator items KSACONINF & KSADB2INF Database,
KSAEDIFILE Document Interchange, KSAQRFCIN qRfc Queues,KSACONNABAP,KSACONNHTTP,
KSACONNTCP Connection Monitoring, KSAMTSTATE CCMS Monitoring, KSANUMSUMM,
KSANUMDTL Buffers & Memory, KSATRANST Workload Performance.

Defects:114273
Abstract: Missing attribute "Free Log Size" in KSASQLSUM attribute group
Additional Information: New attribute "Free Log Size" in KSASQLSUM
attribute group to complete the information related to Logs. Also,
added a pie chart displaying the information related to logs rather
than displaying it in tabular format.

Defects:108201
Abstract: Situation creation for 'Abap Dumps count' and 'Output Request'
workspace attributes are not displayed when creating situation by
right clicking on workspace.
Additional Information: This issue that is related to missing attribute
groups while creating a situation is fixed.

Enhancements:
----------------
No enhancements

------------------------------------------
7.1.1-TIV-ITM_SAP-FP0002
------------------------------------------
APAR's:
-------
APAR: IV75500
Abstract: MAI alerts not appearing in ITM SOLMAN workspace
Additional Information: An Additional functionality is added to collect
the MAI Alerts in the /IBMMON/ITM_MAIALRT_INX Function Module without
the email notification configuration in SAP Solution Manager and
/IBMMON/ITM_IMPL_ALRTINBX BADI implementation with
IF_ALERT_DYN_COFIGURATION interface.


Defects:
--------

Defects:82247
Abstract: Instance down situation is getting fired for all 3 instances
( ASCS DI 04, Database DI 03 and CI 02) when only CI instance is
stopped.
Additional Information: The SAP agent is configured using logon server
mode. The Central instance is stopped. The ASCS and database instances
are running. After starting the SAP Agent, the instance down situation
gets fired for all the 3 instances.

Defects:91070
Abstract: Take action (ksar3) not working.
Additional Information: On Windows systems, the ksar3 Take Action
fails with return code 4, and the situation is not cleared.

Defect: 78887
Abstract: System Name is not showing as first column in "HTTP Services
Details" and "DB2 database details".
Additional Information: On the data columns, System Name should be the
first column for "HTTP Services Details" and "DB2 database details".

Defect:82244
Abstract: SAP System down situation does not open after ASCS is
stopped.
Additional Information: The SAP Agent is configured to ASCS DI
instance in application server mode. When ASCS is stopped, system down
situation is not triggered.

Defect:91013
Abstract:108U Transport import failed on SAP Basis Version 700
Additional Information: To fix this issue, refer the SAP Note # 1610716
-about correcting runtime objects with the wrong alignment.

Defect:91154
Abstract:In case of no data at SAP system, ‘No data available’ single
row did not display for Qrfc inbound queues.
Additional Information: When there is no data on the SAP system,
‘data not applicable’ single row did not display for Qrfc inbound queues.
Also, verified at SAP GUI, ‘0’ row returned when executed
/IBMMON/ITM_QIN_GET_QUEUES.

Defect:91470
Abstract:‘R3_Instance_Down2_Crit’ flyover did not seen in Navigator
view > Agent Ins: node.
Additional Information: The ‘R3_Instance_Down2_Crit’ flyover help does
not appear in the Navigator view > Agent Ins node. Because the situation
is not associated to Ins: node.

Defect: 54092
Abstract: ‘Group Key’ attribute has no data for three workspaces under
:Lds > System
Additional Information: The "Group Key" attribute is not required to be
displayed on TEP for these particular LDS > System workspaces. Therefore,
this attribute is hidden.

Defect: 60027
Abstract: ksapwd utility does not work on non-windows platform with OS
agent ITM630FP3.
Additional Information: This issue occurs on non-Windows systems when
the SAP agent coexists with the 6.3 FP3 OS agent.

Defect: 93616
Abstract: Pre-requisite checker is not working for product code KSA.
Additional Information: The prereqchecker utility for product code KSA
failed with following error: Product Code [KSA] is not valid. Check the
product code and try again.

Defect: 95158
Abstract: In "Enque Locks" workspace the values of "Lock Age" are
incorrect.
Additional Information: In the "Enqueue Locks" workspace, the values
displayed for the "Loc Age (min)" attribute were incorrect. The issue
occurs during the transformation of value to 64-bit number.


Enhancements:
------------
Enhancement: 56204
Abstract:Total ABAP Dumps Count
Additional Information: An additional view is added to the ABAP Dumps
attribute group which contains the total count of ABAP Dumps for
last 24 hours.

Enhancement: 56205
Abstract:Total Spool Count
Additional Information: An additional view is added to the Output
Requests attribute group which contains the total count of Output
Requests based on its status for a particular SAP system.

Enhancement: 92132
Abstract:License Expiration Information
Additional Information: The SAP License Information workspace is added
for navigator item System Summary under sys node. This new attribute
group contains information about the SAP License and its details.

Enhancement: 90115:
Abstract: An attribute group for ICM Monitoring and Service Information
collecting data based on Instances.
Additional Information: A new attribute "Instance Name" is added to
“ICM Monitoring" and "ICM Monitor Service" workspaces.

Enhancement: 90113:
Abstract: CCMS and MAI Alerts from SAP appearing on TEP during
DayLight Saving mode.
Additional Information: The agent must keep collecting the CCMS and
MAI alerts during the daylight savings time changes without the agent
getting restarted.

Enhancement: 90114:
Abstract: Logging mechanism enabled in the ABAP Function Modules for key
Attribute Groups
Additional Information: The logging mechanism is enabled in the ABAP
Function Modules for key attribute groups, such as IBMMON/ITM_ALERTS
and IBMMON/ITM_MAIALRT_INX.

Enhancement: 90110:
Abstract: Exceptions handling for Function Modules in ITM SAP Agent 620
Additional Information: All the exceptions that are present in the
function modules belonging to the ITM SAP Agent 620 should be handled
properly. Once the exceptions are handled there should be a round of
negative testing for all the attribute groups which belong to the
ITM SAP Agent 620 for any functionality breakage.

Enhancement: 91992:
Abstract: Refresh the Java certificate used in SAP Agent
Additional Information: Refresh the Java certificate so that customers
can install and use the SAP agent.


------------------------------------------
7.1.1.1-TIV-ITM_SAP-IF0002
------------------------------------------

APARs:
------

APAR: IV70701
Abstract: SAP-AGENT USER IBMMON_AGENT LOCKED IN CASE OF 711FP1 AGENT.
Additional Information: For SAP basis versions less than 6.4, the
password used was case insensitive. So, if the login failed to the SAP
application failed due to any reason with the password used while
configuring the agent, an attempt with same password in upper-case was
made. In any case(i.e. login failure/success), the password in upper-
case was retained for future login attempts. So, by not taking into
account the cause of login failure in first attempt, it was considered
that password was incorrect. This led to continuous attempts with
password in upper-case which led to user getting locked. For SAP basis
version equal or greater than 6.4, passwords are case sensitive.

APAR: IV72055
Abstract: When the agent is connected to SAP using Japanese
locale/language, TEP shows corrupted Japanese characters.
Additional Information: Japanese characters can't be classified into
the set of ASCII characters which is basic requirement for packaging.
So, directly converting the Japanese character to normal ASCII resulted
in garbage values being displayed to the user. Hence, a function that
can give proper ASCII equivalent of a Japanese character was used to
resolve the issue.

APAR: IV72669
Abstract: Sap-Agent is throwing errors on one of the workspaces
The logs are generating the following errors when loading the workspace:
(5527A4D8.000A-C:ksarfcdataaccessor.cpp,224,"FetchItmData") Error :
InvokeFunctionModule for Function Module /IBMMON/ITM_LDS_SYS_OVERVIEW
failed. Exit -1 And the RFC log produces the following: Function module
"LMDB_GET_STEXT_TO_PRODVERS" not found..
Additional Information: SAP removed Standard Function module
'LMDB_GET_STEXT_TO_PRODVERS' in Solution Manager 7.1 SP12. This standard
function module 'LMDB_GET_STEXT_TO_PRODVERS' is used by
/IBMMON/ITM_LDS_SYS_OVERVIEW to send data to System workspace of LDS
subnode. Since this standard Function Module was removed in Solution
Manager 7.1 SP12 , Function Module /IBMMON/ITM_LDS_SYS_OVERVIEW failed.
Alternative class method ‘CL_DIAGLS_FACTORY’ is used in the Function
Module /IBMMON/ITM_LDS_SYS_OVERVIEW to fetch the data.

APAR IV73325
Abstract: SAP Agent goes UN-responsive after few days of activity.
Additional Information: When configuring Multiple Application Instances
Server with Logon group Mode we need to configure SAP agent using
message server (ASCS = ABAP SAP Central Services) node thus unable to
fetch the details of Central Instance and the logs are generating
following error ‘pthread_mutex_unlock.c,44,"pthread_mutex_unlock") errno
EAGAIN’. Hence, code has been modified to fetch appropriate Central
Instance details.

Defects:
--------

Defect: 78882
Abstract: Duplicate rows are observed on System Summary workspace.
Additional Information: In the Function Module - /IBMMON/ITM_CONFIG,
there was not routine/macro to handle the data collection for the
correct node. Due to which the output of the Function Module
/IBMMON/ITM_CONFIG was showing data for all nodes, even if the origin
node contained 'LDS',it is returning origin node as 'INS'.


--------------------------------
7.1.1-TIV-ITM_SAP-IF0001
--------------------------------

APARs:
------

APAR: IV53685
Abstract: TRANSPORT IMPORT FAILS FOR ITM_CONN_CHECK FUNCTION MODULE.
Additional Information: 711 GA transport fails with ABAP dump for the
/IBMMON/ITM_CONN_CHECK function module. Because of this, the
data is not collected and displayed on the Tivoli Enterprise
Portal for some attribute groups, and the dumps are generated
on SAP side.

APAR: IV52434
Abstract: ATTRLIB MISSING SLASH IF INSTANCE IS CREATED USING
ADDSYSTEM.
Additional Information: Because of the missing slash in ATTRLIB
field name, the agent is configured incorrectly that hampers
the agent functionality and Historical Data Collection (HDC).
This problem occurs when the SAP agent instance is created by
using the tacmd Addsystem command, and the same instance is
reconfigured.

APAR: IV51184
Abstract: FUNCTION MODULE "/IBMMON/ITM_SYS_LOG" GENERATING ABAP
DUMP.
Additional Information: The "IBMMON/ITM_SYS_LOG" function module is
invoked every 10 minutes and it generates ABAP dumps.
"/IBMMON/ITM_SYS_LOG" function module was called with
"ITM_R3_LOG_RECORD" parameter. This parameter is not defined.
The Syslog information is available from INS and GRP subnodes,
however, problem occurs only while collecting the data for
:GRP subnode.

APAR: IV47613
Abstract: ABAP DUMPS DUE TO OVERFLOW IN /IBMMON/ITM_CCMS_ALERTS
(ALERT UNIQUE ID).
Additional Information: Added a new attribute named
'Extended Alert Unique Identifier' to hold bigger alert unique
identifier. The extended alert unique identifier attribute is
used to close an alert in the SAP system.


Defects:
--------

Defect: 43177
Abstract: Data is not coming for ‘ITM_USER_INFORMATION’ for ':Sys'
node.
Additional Information: The code considered only the 'INS' node.
Therefore, the user information link in the 'SYS' node did not
receive any data.

Defect: 43075
Abstract: 'No Applicable data' seen for CCMS Monitoring on ALL Grp
node along with 9911 alert in second call of agent in case of
CEN configured SAP.
Additional Information: When retrieving alerts for the first call of
the new CCMS design for GRP node in case of Central (CEN)
system, 'No Applicable Data' is displayed on the Tivoli
Enterprise Portal. The second call of the agent was
generating a 9911 alert.

Defect: 42393
Abstract: Argument column in "Lock Information" is showing invalid
data.
Additional Information: Lock argument of locked object shows string
'[][][][][][][]' on the Tivoli Enterprise Portal, when all
possible fields are responsible for locking that object.

Defect: 42317
Abstract : Delete transport unable to delete reference of agent BADI
class from MAI configured SAP system.
Additional Information: BADI delete transport must be able to
delete all relevant BADI classes and implementations from the
system where BADI is imported.

Defect: 40637
Abstract: Exception condition "ITM-NOT_FOUND" raised in case syslog
records are not found at SAP side.
Additional Information: If particular syslog details are not present
on the SAP system, then while accessing syslog details using
sys_detail link on the Tivoli Enterprise Portal, a "Exception
condition 'ITM-NOT FOUND' raised" short dump is generated on
the SAP side and a blank screen is displayed on the Tivoli
Enterprise Portal.

Defect: 39686
Abstract: Syslog causing ABAP dump for Group Sub Node.
Additional Information: For the logs and traces attribute group of
the GRP node, exceptions are raised.

Defect: 39681
Abstract: Data is missing for many columns of ITM_JOBS.
Additional Information: Data is not displayed for many columns of
ITM_Jobs.

Defect: 39007
Abstract: "No applicable Data" row should be seen on TEP for system
log under system name.
Additional Information: If there is no data for the "System Log"
workspace, then, "No applicable data" must be displayed in the
System Name column.

Defect: 38998
Abstract: Unable to interpret X as a number in function module
/IBMMON/ITM_HOSTS.
Additional Information: If the SAP system contains more than 9
application servers (RFC servers), the "Unable to interpret *
as a number" message is displayed in the /IBMMON/ITM_HOSTS
function module.

Defect: 38995
Abstract: Tivoli SAP agent causing dump in SAP on UNIX server.
Additional Information: If an exception occurred while reading job
log, the /IBMMON/ITM_JOB_LOG function module is terminated.

Defect: 38903
Abstract: IDOC Number not included in the Display item.
Additional Information: The "IDOC Number" is not available to use
as a display item in situations.

Defect: 38251
Abstract : Data is getting fetched for invalid sub-nodes.
Additional Information: Data must be returned only for the sub node
that is called; data must not be returned for other irrelevant
sub nodes. Call from the agent gives ITM_MGROUP or Origin node
as input to most of the function modules that contain the node
details.


Enhancements:
-------------

Enhancement: 38724
Abstract: "Client" column is required for ITM_IDOC workspace to
differentiate the respective client's data.
Additional Information: Added a "Client" column in the
"IDOC Information" view of the "Data Transfer Information"
workspace. The “Client” column shows the client name for the
respective data of client.


-------------------------------
7.1.1-TIV-ITM_SAP-FP0001
--------------------------------

APARs:
-----

APAR: IV60177
Abstract: TEPS DISPLAYS ALERT TIMESTAMP AS UTC
Additional Information: MAI Alerts stored in the database table
'/IBMMON/ITM_ALIX' are in the UTC format.So while fetching
such MAI Alerts, conversion from UTC time zone to current
system time zone is required.

APAR: IV60254
Abstract: 'TRANSACTION PERFORMANCE' AND 'R/3 TRANSACTION PERFORMANCE'
MODULES ARE NOT SENDING DATA FOR HDC
Additional Information: Code has been changed in Transaction
performance logic which creates 'KSATRANS' file to display
historical data on TEP for Transaction performance.

APAR: IV60989
Abstract: EMPTY WORKSPACE FOR BUSINESS PROCESS MONITORING AND
SYSTEMMONITORING IN TEP
Additional Information: Code changes have been done to handle
exceptions for the SAP standard DSWP_BPM_SOLUTION_ID_CONVERT
function module and for the /IBMMON/ITM_MAIBP_MONITORING
MAI BPM function module.

APAR: IV61450
Abstract: REMOVE PERIOD START/END ATTRIBUTES OF XML MESSAGE LOGS
Additional Information: The attributes 'Period Start' and 'Period
End' are used by the agent internally and aren't helpful
to customer in anyway. In order to hide them from attribute
view, the 'USAGE' and 'COST' tags have been set to appropriate
values. Also, the queries that define the attribute view have
been modified to remove the 'Period Start' and 'Period End'
attributes.

APAR: IV59319
Abstract: SAP AGENT NOT PICKING UP ALERTS FROM SOLUTION MANAGER
Additional Information: This is DOC APAR and the third Party OS
command adapter should be configured and mail notification
should be enabled using appropriate steps.

Defects:
--------

Defect: 53372
Abstract: Unable to start SAP Agent when candlehome contains ‘SAP’
word.
Additional Information: Post install script ignores variables
containing 'SAP' keyword and they are not included in 'ksaenv'
file. When CANDLEHOME and JAVAHOME contained 'SAP' keyword,
they were ignored as well resulting in failure to start
ksaagent.

Defect: 49745
Abstract: Agent doesn't read syslog.idx file correctly
Additional Information: SAP agent read '<SID>_syslog.idx' incorrectly
leading to corrupt '.idx' file. This resulted in system log not
getting detected sometimes.
Note: This issue is reproducible only with multi instance SAP
system.

Defect: 47233
Abstract: Test connection utility is not working on windows as
designed for application server mode.
Additional Information: With the new NWRFC library, 'Gateway Host'
and 'Gateway service' are not required while creating a RFC
connection with the SAP server. So, these fields have been
removed from the agent configuration panel.

Defect: 45898
Abstract: R/3 action link of ‘Close Alert’ and ‘Close Alerts of the
same type’ are missing in ‘Alert Information’ view of CCMS
monitoring workspaces.
Additional Information: The workspace has been modified to create the
two missing links. Also, the code on the SAP side has been
fixed to correct the close alert mechanism.


Enhancements:
-------------

Enhancement: 44620
Abstract: Netweaver RFC support added for SAP Agent common
layers.
Additional Information: Netweaver RFC v7.20 support has been added.
Communication with SAP system will now happen using the NWRFC
library instead of the Classic RFC library.

Enhancement: 44663
Abstract: Logging of SAP 'Component Version Id' and 'Interim Fix Id'
in the agent log file.
Additional Information: SAP 'Component Version Id' and 'Interim Fix
Id' are returned as additional parameters by the
'/IBMMON/ITM_FUNC_PARMS' function module and can be viewed in
the agent logs with minimum trace level enabled.

Enhancement: 45911
Abstract: Facilitate remote connection of type 'Internal Connection',
'Connections via ABAP driver' and 'TCP/IP' Connections defined
in SAP server.
Additional Information: This link has been provided from the 'Test
Connection' link in the 'Connection Monitoring' workspace to
check the status of a remote connection on demand.

Enhancement: 45973
Abstract: Facilitate single Unicode ITM file containing both BADI and
non-BADI objects.
Additional Information: Single ITM file has been provided to import
the SAP Agent transport on all supported SAP versions having
BADI or non-BADi implementation.

--------------------------------
7.1.1-TIV-ITM_SAP-IF0001
--------------------------------

APARs:
------

APAR: IV53685
Abstract: TRANSPORT IMPORT FAILS FOR ITM_CONN_CHECK FUNCTION MODULE.
Additional Information: 711 GA transport fails with ABAP dump for the
/IBMMON/ITM_CONN_CHECK function module. Because of this, the
data is not collected and displayed on the Tivoli Enterprise
Portal for some attribute groups, and the dumps are generated
on SAP side.

APAR: IV52434
Abstract: ATTRLIB MISSING SLASH IF INSTANCE IS CREATED USING
ADDSYSTEM.
Additional Information: Because of the missing slash in ATTRLIB
field name, the agent is configured incorrectly that hampers
the agent functionality and Historical Data Collection (HDC).
This problem occurs when the SAP agent instance is created by
using the tacmd Addsystem command, and the same instance is
reconfigured.

APAR: IV51184
Abstract: FUNCTION MODULE "/IBMMON/ITM_SYS_LOG" GENERATING ABAP
DUMP.
Additional Information: The "IBMMON/ITM_SYS_LOG" function module is
invoked every 10 minutes and it generates ABAP dumps.
"/IBMMON/ITM_SYS_LOG" function module was called with
"ITM_R3_LOG_RECORD" parameter. This parameter is not defined.
The Syslog information is available from INS and GRP subnodes,
however, problem occurs only while collecting the data for
:GRP subnode.

APAR: IV47613
Abstract: ABAP DUMPS DUE TO OVERFLOW IN /IBMMON/ITM_CCMS_ALERTS
(ALERT UNIQUE ID).
Additional Information: Added a new attribute named
'Extended Alert Unique Identifier' to hold bigger alert unique
identifier. The extended alert unique identifier attribute is
used to close an alert in the SAP system.


Defects:
--------

Defect: 43177
Abstract: Data is not coming for ‘ITM_USER_INFORMATION’ for ':Sys'
node.
Additional Information: The code considered only the 'INS' node.
Therefore, the user information link in the 'SYS' node did not
receive any data.

Defect: 43075
Abstract: 'No Applicable data' seen for CCMS Monitoring on ALL Grp
node along with 9911 alert in second call of agent in case of
CEN configured SAP.
Additional Information: When retrieving alerts for the first call of
the new CCMS design for GRP node in case of Central (CEN)
system, 'No Applicable Data' is displayed on the Tivoli
Enterprise Portal. The second call of the agent was
generating a 9911 alert.

Defect: 42393
Abstract: Argument column in "Lock Information" is showing invalid
data.
Additional Information: Lock argument of locked object shows string
'[][][][][][][]' on the Tivoli Enterprise Portal, when all
possible fields are responsible for locking that object.

Defect: 42317
Abstract : Delete transport unable to delete reference of agent BADI
class from MAI configured SAP system.
Additional Information: BADI delete transport must be able to
delete all relevant BADI classes and implementations from the
system where BADI is imported.

Defect: 40637
Abstract: Exception condition "ITM-NOT_FOUND" raised in case syslog
records are not found at SAP side.
Additional Information: If particular syslog details are not present
on the SAP system, then while accessing syslog details using
sys_detail link on the Tivoli Enterprise Portal, a "Exception
condition 'ITM-NOT FOUND' raised" short dump is generated on
the SAP side and a blank screen is displayed on the Tivoli
Enterprise Portal.

Defect: 39686
Abstract: Syslog causing ABAP dump for Group Sub Node.
Additional Information: For the logs and traces attribute group of
the GRP node, exceptions are raised.

Defect: 39681
Abstract: Data is missing for many columns of ITM_JOBS.
Additional Information: Data is not displayed for many columns of
ITM_Jobs.

Defect: 39007
Abstract: "No applicable Data" row should be seen on TEP for system
log under system name.
Additional Information: If there is no data for the "System Log"
workspace, then, "No applicable data" must be displayed in the
System Name column.

Defect: 38998
Abstract: Unable to interpret X as a number in function module
/IBMMON/ITM_HOSTS.
Additional Information: If the SAP system contains more than 9
application servers (RFC servers), the "Unable to interpret *
as a number" message is displayed in the /IBMMON/ITM_HOSTS
function module.

Defect: 38995
Abstract: Tivoli SAP agent causing dump in SAP on UNIX server.
Additional Information: If an exception occurred while reading job
log, the /IBMMON/ITM_JOB_LOG function module is terminated.

Defect: 38903
Abstract: IDOC Number not included in the Display item.
Additional Information: The "IDOC Number" is not available to use
as a display item in situations.

Defect: 38251
Abstract : Data is getting fetched for invalid sub-nodes.
Additional Information: Data must be returned only for the sub node
that is called; data must not be returned for other irrelevant
sub nodes. Call from the agent gives ITM_MGROUP or Origin node
as input to most of the function modules that contain the node
details.

Enhancements:
-------------

Enhancement: 38724
Abstract: "Client" column is required for ITM_IDOC workspace to
differentiate the respective client's data.
Additional Information: Added a "Client" column in the
"IDOC Information" view of the "Data Transfer Information"
workspace. The “Client” column shows the client name for the
respective data of client.

----------------------------
7.1.1.1-TIV-ITM_SAP-IF0001
----------------------------

APARs:
------

APAR: IV63525
Abstract: CUSTOMER IS GETTING 0 ENTRIES FOR THE OUTPUT OF THE
FUNCTION MODULE /IBMMON/ITM_QOUT_GET_QUEUES.
Additional Information: The /IBMMON/ITM_QOUT_GET_QUEUES function
module stopped collecting the data even though the data was
present in the SAP system. Due to this, SYSID ‘+++’ was
displayed on the Tivoli Enterprise Portal. The function module
has been rectified for collecting the data from the SAP
systems having versions greater than 46C and SP level
SPKB46C39.

APAR: IV60733
Abstract: MPS CX_SY_CONVERSION_NO_NUMBER IN FUNCTION MODULE
IBMMON/ITM_FILE_SYSTEM
Additional Information: ABAP dump ‘Conversion Error –unable to
handle‘---‘ as a number ’ for the / IBMMON/ITM_FILE_SYSTEM
function module is gracefully handled towards File Systems
attribute group.


Defects:
--------

Defect: 58382
Abstract: Exception condition "GWY_COMMUNICATION_FAILURE" raised.
Additional Information: "GWY_COMMUNICATION_FAILURE" has been
gracefully handled for the /IBMMON/ITM_GWY_CONNECTIONS
function module towards the Gateway Connections attribute
group.

Defect: 55733
Abstract: TEP Remote configuration of SAP Agent is not working on
non-windows after remote upgrade.
Additional Information: While getting the Config parameters from the
".cfg" file, the two parameters for gateway are removed from
the parameters that are being sent to the Tivoli Enterprise
Portal Configuration Panel. Also the ".cfg" file is updated
by removing those parameters. Then, reconfiguration of Agent
Instance with appserver and logon mode through Tivoli
Enterprise Portal is successful after remote upgradation to
711FP1 IF1.

Defect: 55366
Abstract: ABAP Dumps when Job Name is not present in SAP standard
table.
Additional Information: Exception handling was missing for the
scenario of the Job Name not being present in the SAP standard
table. The issue has been fixed by adding the required
exception handling for Workspace Integration engine background
jobs when Job is not present in SAP.


Enhancements:
-------------

Enhancement: 67334
Abstract: Additional functionality to handle the MAI missing Alerts
in the Function Module /IBMMON/ITM_MAIALRT_INX.
Additional Information: Function module /IBMMON/ITM_MAIALRT_INX is
modified to fetch the MAI Alerts which are missed by ITM SAP
Agent as these MAI Alerts are inserted into table
/IBMMON/ITM_ALIX with some delay by SAP.
Note:
1) SAP system time and ITCAM SAP Agent machine time should be
in sync upto accuracy of seconds.
2) In order to have full collection of MAI Alerts, there is
an additional overlap time being added to the sampling time
frequency given by the ITCAM SAP Agent.
This additional overlap time is configurable parameter on
the SAP side
Please note -
a)By default the additional overlap time will be 1 min i.e.
60 seconds.
b)Maximum additional overlap time which can be configured
will be 5 mins i.e. 300 seconds.
c)If the user wants the additional overlap time greater than
1 min i.e. 60 seconds and less than or equal to 5mins i.e.
300 mins, then he should follow the below steps.

Please find below the steps to configure this additional
overlap time on SAP side:
• Go to transaction code SE16.
• Enter the table name as '/IBMMON/ITM_CNFG' and press 'F7'.
• Execute the database table '/IBMMON/ITM_CNFG' or press 'F8'.
• Add the additional overlap time parameter as ‘MAI_PERD_OV’
in the database field 'ITM Configuration Parameters' and
then add the additional overlap time in seconds in the
database field 'VALUE_INT' and save it.


3.0 Architecture and prerequisites
==================================
This Fix Pack is supported on all operating systems listed in the IBM
Tivoli Composite Application Manager Agent for SAP Applications
Installation and Configuration guide, Version 7.1.1 Fix Pack 3:
Link:
http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.
itcama.doc_7.2.1.1/sap/sap_landing_install.html

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 V7.2.1
Fix Pack 2 at:
http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.it
cama.doc_7.2.1.1/prerequisites/apps7211_systemreqs.html

ITCAM for Applications 7.2.1.1 Knowledge Center:
http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.it
cama.doc_7.2.1.1/welcome_apps7211.html


3.1 Prerequisites for this fix:
------------------------------
There are no prerequisites for this fix. As this fix is cumulative,it
can be installed on any fix level for this version, release, and
modification level above the prerequisite.


4.0 Image directory contents
============================
Physical Part Number: ITCAM Agent for SAP Applications CBP26ML
Electronic Part Number: ITCAM Agent for SAP Applications CN91BML

5.0 Installation instructions
=============================
When this fix pack image is downloaded from the IBM Software Support
web site, these rules apply:
1. You can locally install the fix pack only on a system that already
hosts a licensed copy of IBM Tivoli Monitoring for SAP Applications.
Similar to other upgrade software, the fix pack image can also be
locally installed on a computer where the product software is not
already installed.
2. You can populate agents to the depot.
3. You can remotely deploy agents to existing or new installations.

When this fix pack image is downloaded from Passport Advantage, these
rules apply:
1. You can locally install the fix pack on a system that already hosts
a licensed copy of IBM Tivoli Monitoring for SAP Applications.
2. You can locally install the fix pack on a system that does not
already host a licensed copy of IBM Tivoli Monitoring for SAP
Applications.
3. You can populate agents to the depot.
4. You can remotely deploy agents to existing or new installations.

5.1 Before installing the fix:
-----------------------------
- The prerequisites listed under section 3.1 entitled
'Prerequisites for this fix' must be installed for upgrade.

- 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 pack 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 pack, be sure to
perform a backup of your environment before installing this fix pack.

5.2 Local agent update:
----------------------
1. Transfer the appropriate archive file 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 unzip utility on Windows systems. This step creates a directory
structure that contains fixes for all supported operating systems.

3. Use the procedures in the 'IBM Tivoli Composite Application Manager
Agent for SAP Applications Version 7.1.1 Fix Pack 4 User's Guide'
to install the agent.

5.3 Remote agent update:
-----------------------
1. Transfer the appropriate archive file 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 pack 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 Appendix A.
Commands reference of the 'IBM Tivoli Monitoring Command Reference'.

On UNIX systems,
if the fix was expanded to <TEMP>/<PARTNUMBER>:
> $CANDLEHOME/bin/tacmd addBundles -i
<TEMP>/<PARTNUMBER>/unix -t sa

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

where:
-i is the directory that contains the deployment bundles to be
added to the depot.
-t is the product code of the product to add, in this case sa
represents the Monitoring Agent for SAP.

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

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 07110400

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:
------------------------
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 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. Use the procedures in the 'IBM Tivoli Composite Application
Manager Agent for SAP Applications Version 7.1.1 Fix Pack 4 User's
Guide' to install the support.

4. If the Tivoli Enterprise Monitoring Server being updated is remote
(not a Hub Tivoli Enterprise Monitoring Server) then restart the
Tivoli Enterprise Monitoring Server.

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

5.5 Installing SAP agent transport:
----------------------------------
Note: From this fix onwards, a single ITM file has been provided for
importing SAP transport on all supported SAP versions having BADI or
non-BADI implementation.

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 sets of transport files are in the
ABAP directory of the SAP agent fix archive:

1) K711_00115U.ITM and R711_00115U.ITM in /ABAP directory.
These files are for Unicode versions of the transport.

2) K711_00115_DELETE.ITM and R711_00115_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. Copy your transport files to the SAP Transport System data
directory as follows:
1) Copy the K711_00115U.ITM file to the cofiles directory.
2) Copy the R711_00115U.ITM file to the data directory.

4. Run the following command 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

tp addtobuffer ITMK711_00115U SID
pf=\usr\sap\trans\bin\PROFILE_NAME
tp import ITMK711_00115U 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 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 must be
displayed as 07.11.04.00

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

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 non-Windows systems:
----------------------
To validate that all components have been installed, run the
following command:

For example:
> %CANDLE_HOME%/bin/cinfo -i

Note: cinfo output may differ depending on ITM version.

*********** Wed Jun 25 15:10:46 IST 2014 ******************
User: root Groups: root bin daemon sys adm disk wheel pkcs11
Host name : IBMSAP2V8 Installer Lvl:06.23.03.00
CandleHome: /opt/IBM/ITM
***********************************************************
...Product inventory

ax IBM Tivoli Monitoring Shared Libraries
lx8266 Version: 06.23.03.00

gs IBM GSKit Security Interface
li6243 Version: 07.40.43.00
lx8266 Version: 07.40.43.00

jr Tivoli Enterprise-supplied JRE
lx8266 Version: 06.12.00.00

sa IBM Tivoli Composite Application Manager Agent for SAP Applications
lx8266 Version: 07.11.04.00

ue Tivoli Enterprise Services User Interface Extensions
lx8266 Version: 06.23.03.00

ui Tivoli Enterprise Services User Interface
lx8266 Version: 06.23.03.00


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

1. The "System Topology" linked workspace is blank for the Solution Manager 7.2.
The "System Topology" linked workspace which is linked from "Systems
Overview" view of "Systems Overview" workspace available for "Systems"
Navigator item will display a blank page as the "Systems Overview" view is
not supported in case of the Solution Manager 7.2.

2. Value of count for ‘Instances ConnectionFailed' status in "System Summary" of
":mySAP" view may differ from actual status displayed ‘Instance Summary' view
on "System Summary" workspace of ":mySAP" node on TEP.

3. The procedure to be followed in case of CCMS alerts, Syslogs and MAI Alerts
not received by agent on TEP -
3.A: Stop SAP agent.
3.B: Delete the idx files related to CCMS alerts, Syslogs or MAI alerts as
per the case may be -
On windows:
Delete <candle home>\TMAITM6\<Sys id>_alerts.idx file.
Delete <candle home>\TMAITM6\<Sys id>_syslog.idx file.
Delete <candle home>\TMAITM6\<Sys id>_mai.idx file.
On Non-Windows:
Delete <candle home>\config\<Sys id>_alerts.idx file.
Delete <candle home>\config\<Sys id>_syslog.idx file.
Delete <candle home>\config\<Sys id>_mai.idx file.
3.C: Start SAP agent.

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

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

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

8.2 Additional Information:
---------------------------
1. Solution Manager 7.2 having SPS level upto 3 will be supported in this release.

2. For the Solution Manager 7.2, only the “New MAI Alert Fetching Design" will
be supported.

3. The 'Passive' instance status and the 'Instances Passive' attribute for the
'Instance Configuration' attribute group will only be supported for the SAP
Basis version greater than or equal to 750.

4. 4.A: For the Solution Manager 7.2, the "Solution Manager Landscape Databases
And System" attribute group will display the data on the views specific
to Solution Manager 7.2 of "Database Overview" and "Systems Overview"
workspace at "Databases" and "Systems" navigator item of ":LDS" node
respectively. The "Solution Manager Servers" attribute group will be
supported for Solution Manager 7.2 with a limitation of few attributes.
The HOST OS, OS Version, Application Server Hardware, SAPS Measured,
SAP Vendor, Central System Routing Information, and Central System to
Server Routing Information attributes are not supported for the
Solution Manager 7.2. Therefore, "Not applicable" message will be
displayed for those attributes on "Servers Overview" workspace of
"Servers" Navigator item available under ":LDS" node on TEP.
All the other attribute groups except the one's, which are mentioned
above will not be supported in the Solution Manager 7.2.
The workspaces related to those attribute groups will display the
message "Not Supported for this SAP version".

For the Solution Manager less than 7.2, the views "Solution Manager 7.2
Database Overview" and "Solution Manager 7.2 Systems Overview" will
display the message as "Not Supported for this SAP version".
Apart from this, the rest remains the same as it was in previous
releases of SAP Agent.

4.B: The "Business Process Monitoring Alerts" workspace is introduced for
"Business Process Monitoring Alerts" under ":SLM" node for the "Alert
Inbox" navigator item.

4.C: The "MAI Solution Overview" and "MAI Business Process Monitoring"
attribute groups are not supported in this release of SAP Agent.
Hence, the "Solution Overview" and "Business Process Monitoring"
workspaces will display the message "Not Supported for this SAP
version".


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.