Fix Readme
Abstract
This fix pack resolves APARs and defects listed in the
"Problems Fixed" section below. This fix pack also includes the
superseded fixes listed in section 2.4.
Content
Copyright International Business Machines Corporation 2022.
All rights reserved.
All rights reserved.
Component: IBM(R) Tivoli(R) Composite Application Manager Agent for SAP
Applications, Version 7.1.0 Fix Pack 0003
Component ID: 5724B97SO
Fix: Fix Pack 0003, 7.1.0-TIV-ITM_SAP-FP0003
Date: March 25, 2022
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
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 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.0-TIV-ITM_SAP-FP0003
======================================
The following problems are addressed by this fix pack. 2.1 APARs
--------------
APAR: IJ36909
Abstract: IBM Agent for SAP 07.10.02.02 creating ABAP dumps
Additional Information: ABAP dump is created during execution of Function
module, /IBMMON/ITM_NEW_CCMS_ALERTS. This APAR is opened to support parameter
change for the SAP routine, ‘RAWALERT2ALERTRC’ to get aligned with the support
package level changes introduced by SAP.
2.2 Defects
No Defects
2.3 Enhancements
No Enhancements
2.4 Superseded fixes
7.1.0.2-TIV-ITM_SAP-IF0003
7.1.0.2-TIV-ITM_SAP-IF0002
7.1.0.2-TIV-ITM_SAP-IF0001
7.1.0-TIV-ITM_SAP-FP0002
7.1.0.1-TIV-ITM_SAP-IF0001
7.1.0-TIV-ITM_SAP-FP0001
7.1.0-TIV-ITM_SAP-IF0001
----------------------------------
APARs
----------
No APARs
Defect: 136432
Abstract: For windows platform, Incorrect interim patch version is displayed
under the heading “SELF-DESCRIBED APPLICATION SUPPORT PACKAGE” .
Additional Information: After installing the IF2 patch on SAP Agent 710FP2,
the support under “SELF-DESCRIBED APPLICATION SUPPORT PACKAGE” was
not getting updated earlier and remained 07100200. This defect is
now fixed and correct version, that is 07100202, gets updated for
support of TEMS, TEPS, and TEPD on windows platform.
Enhancements
--------------------
No Enhancements
----------------------------------
7.1.0.2-TIV-ITM_SAP-IF0001
----------------------------------
APARs
----------
APAR: IV81985
Abstract: Monitoring for SAP user types
Additional Information: The SAP agent monitored system information
for all the user types except the SYSTEM and SERVICE user
types. The docksa.odi is updated so that the SAP agent can
monitor the SYSTEM and SERVICE user types. The SYSTEM and
SERVICE user types along with their ENUM values are added
under properties of ‘/IBMMON/ITM_LOGON_INFORMATION' function
module in the docksa.odi. The agent side support files are
also updated to incorporate functionality for the two
additional users.
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
1. Transfer the appropriate archive file
to the Tivoli Enterprise Monitoring Servers, Tivoli
Enterprise Portal Servers, or Tivoli Enterprise Portal Desktops.
This procedure installs the SAP transport into the SAP system. You
are not required to uninstall the previous transport before
installing this transport.
non-Unicode
tp addtobuffer ITMK710_00148 SID
pf=\usr\sap\trans\bin\PROFILE_NAME
tp import ITMK710_00148 SID client=nnn U16
pf=\usr\sap\trans\bin\PROFILE_NAME
Unicode
tp addtobuffer ITMK710_00148U SID
pf=\usr\sap\trans\bin\PROFILE_NAME
tp import ITMK710_00148U SID client=nnn U16
pf=\usr\sap\trans\bin\PROFILE_NAME
6.0 Additional installation information
1. To verify 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.
On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring
installation directory. The default location is '/opt/IBM/ITM'.
> $CANDLEHOME/bin/tacmd listSystems -t sa
For the agent on UNIX systems, the version number is
07.10.03.00.
> %CANDLE_HOME%\InstallITM\kincinfo -i
7.0 Known problems and workarounds
None
8.0 Additional product information
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.
1. Linux 32 bit(li6243) support has been removed from
7.1.0-TIV-ITM_SAP-FP0003 SAP agent.
2. Windows 32 bit(winnt) support has been removed from
7.1.0-TIV-ITM_SAP-FP0003 SAP agent.
3. Java version is updated to JAVA 8.
4. Upgraded agent code compilation to Visual Studio 2013
5. TEMA version is upgraded to ITM 630 FP7 SP10 from 623 FP3 for
7.1.0-TIV-ITM_SAP-FP0003 SAP Agent.
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.
Abstract: IBM Agent for SAP 07.10.02.02 creating ABAP dumps
Additional Information: ABAP dump is created during execution of Function
module, /IBMMON/ITM_NEW_CCMS_ALERTS. This APAR is opened to support parameter
change for the SAP routine, ‘RAWALERT2ALERTRC’ to get aligned with the support
package level changes introduced by SAP.
2.2 Defects
--------------
No Defects
2.3 Enhancements
---------------------
No Enhancements
2.4 Superseded fixes
------------------------
7.1.0.2-TIV-ITM_SAP-IF00037.1.0.2-TIV-ITM_SAP-IF0002
7.1.0.2-TIV-ITM_SAP-IF0001
7.1.0-TIV-ITM_SAP-FP0002
7.1.0.1-TIV-ITM_SAP-IF0001
7.1.0-TIV-ITM_SAP-FP0001
7.1.0-TIV-ITM_SAP-IF0001
----------------------------------
7.1.0.2-TIV-ITM_SAP-IF0003
----------------------------------
APARs
----------
No APARs
Defects
------------
Defect: 139053
Abstract: Copy functionality is not working for SAP Agent.
Additional Information: Copy Functionality is enabled. The system picks the
backup file that was created and create copy of backup file for any systems.
----------------------------------
APARs
------------
Defect: 139053
Abstract: Copy functionality is not working for SAP Agent.
Additional Information: Copy Functionality is enabled. The system picks the
backup file that was created and create copy of backup file for any systems.
Enhancements
--------------------
Enhancement: 127520
Abstract: ITCAM SAP agent security enhancement
Additional Information:
Implemented enhancement for the following security scenarios:
1. "Hardcoded Domain":
For improved security, user can configure the password of the default
username.
2. "Generic Table operations":
An Authorization Object 'S_DEVELOP' is added to the profile /IBMMON/AUTH and
assigned to user IBMMON_AGENT. The user with the Authorization Object
'S_DEVELOP' has the authority to perform Generic table
operations such as:
a) "Generic Read Report"
b) "Generic Delete Report"
c) "Generic Table Query(Read Access)"
d) "Forceful querying(Read/Write Access)"
3. "Missing authority check in Report and RFC Enabled Functions"
A new Authorization Object ZITM_AUTH is created in the profile /IBMMON
/AUTH and assigned to user IBMMON_AGENT. The user with the Authorization
Object ZITM_AUTH has the authority to access the attributes
tagged under "SYS","LDS","SOL,"PI" node and for Reports. For other users,
"RFC Error Check Agent Log" message is displayed on TEP.
4. "Missing Authority check before Call Transaction"
An Authorization Object 'S_DEVELOP' is added to the profile /IBMMON/AUTH
and assigned to user IBMMON_AGENT. The user with the Authorization Object
'S_TCODE' has the authority to call any transactions
5. "Hardcoded Password"
Default password for IBMMON_AGENT is replaced with random generation of
password. User can modify the password according to their password policy.
Use the following procedure to change your password:
a) Logon to SAP GUI. Go to SU01 transaction.
b) In the user field, enter username and click the change icon.
c) Open the Logon Data tab .
d) In New Password and Repeat Password fields, enter the
password of your choice.
e) Click save.
6. "Directory Traversal (Read/Write Access)"
Direct read and write access of directories are replaced with logical file
paths.
Note: If SAP system is installed on UNIX or WINDOWS NT operating system,
the <SYSID>_ConfigBackup.csv file is created either on application
server (at /usr/sap/<SYSID>/<INSTANCE>/work/<FILENAME>) or in the global
directory (at /usr/sap/<SYSID>/<INSTANCE>/global/<FILENAME>). According to
SAP environment, filename might be truncated.
7. "Direct database modification"
For improved security, additional internal security layer is implemented
for database access.
8. "Usage of db tables without authorization groups"
Added an authorization group "ZITM" and all database tables are assigned to
ZITM authorization group. This authorization group is assigned to the
authorization object "S_TABU_DIS" and is added to the profile /IBMMON/AUTH
and assigned to user IBMMON_AGENT. The user with the Authorization Object
'S_TABU_DIS' and the authorization group ZITM has the authority to access
database tables.
--------------------
Enhancement: 127520
Abstract: ITCAM SAP agent security enhancement
Additional Information:
Implemented enhancement for the following security scenarios:
1. "Hardcoded Domain":
For improved security, user can configure the password of the default
username.
2. "Generic Table operations":
An Authorization Object 'S_DEVELOP' is added to the profile /IBMMON/AUTH and
assigned to user IBMMON_AGENT. The user with the Authorization Object
'S_DEVELOP' has the authority to perform Generic table
operations such as:
a) "Generic Read Report"
b) "Generic Delete Report"
c) "Generic Table Query(Read Access)"
d) "Forceful querying(Read/Write Access)"
3. "Missing authority check in Report and RFC Enabled Functions"
A new Authorization Object ZITM_AUTH is created in the profile /IBMMON
/AUTH and assigned to user IBMMON_AGENT. The user with the Authorization
Object ZITM_AUTH has the authority to access the attributes
tagged under "SYS","LDS","SOL,"PI" node and for Reports. For other users,
"RFC Error Check Agent Log" message is displayed on TEP.
4. "Missing Authority check before Call Transaction"
An Authorization Object 'S_DEVELOP' is added to the profile /IBMMON/AUTH
and assigned to user IBMMON_AGENT. The user with the Authorization Object
'S_TCODE' has the authority to call any transactions
5. "Hardcoded Password"
Default password for IBMMON_AGENT is replaced with random generation of
password. User can modify the password according to their password policy.
Use the following procedure to change your password:
a) Logon to SAP GUI. Go to SU01 transaction.
b) In the user field, enter username and click the change icon.
c) Open the Logon Data tab .
d) In New Password and Repeat Password fields, enter the
password of your choice.
e) Click save.
6. "Directory Traversal (Read/Write Access)"
Direct read and write access of directories are replaced with logical file
paths.
Note: If SAP system is installed on UNIX or WINDOWS NT operating system,
the <SYSID>_ConfigBackup.csv file is created either on application
server (at /usr/sap/<SYSID>/<INSTANCE>/work/<FILENAME>) or in the global
directory (at /usr/sap/<SYSID>/<INSTANCE>/global/<FILENAME>). According to
SAP environment, filename might be truncated.
7. "Direct database modification"
For improved security, additional internal security layer is implemented
for database access.
8. "Usage of db tables without authorization groups"
Added an authorization group "ZITM" and all database tables are assigned to
ZITM authorization group. This authorization group is assigned to the
authorization object "S_TABU_DIS" and is added to the profile /IBMMON/AUTH
and assigned to user IBMMON_AGENT. The user with the Authorization Object
'S_TABU_DIS' and the authorization group ZITM has the authority to access
database tables.
----------------------------------
7.1.0.2-TIV-ITM_SAP-IF0002
----------------------------------
APARs
-----------
APAR: IJ12935
Abstract: Instance Summary showing wrong instance details
Additional Information: When the hostname contains System Name (SYSID)
in it, the Instance name is fetched incorrectly (shown as
'DELETED' in Instance name string). To resolve this, ABAP
code has been changed to display correct instance
name in the output of Function Module – /IBMMON/ITM_CONFIG,
/IBMMON/ITM_HOSTS. In reference to PMR TS001686112
(Parent Case: TS001666075) - Instance Summary showing wrong
instance details.
Defects
------------
Defect: 136442
Abstract: SAP Agent log file does not display “ITM_interim” as an entry .
Additional Information: “Interim Fix” field is being added by doing the
required code changes in the Function Module -
/IBMMON/ITM_FUNC_PARMS and /IBMMON/ITM_HOSTS. This is seen at
the output of the Function Module - /IBMMON/ITM_FUNC_PARMS and
/IBMMON/ITM_HOSTS.
------------
Defect: 136442
Abstract: SAP Agent log file does not display “ITM_interim” as an entry .
Additional Information: “Interim Fix” field is being added by doing the
required code changes in the Function Module -
/IBMMON/ITM_FUNC_PARMS and /IBMMON/ITM_HOSTS. This is seen at
the output of the Function Module - /IBMMON/ITM_FUNC_PARMS and
/IBMMON/ITM_HOSTS.
Defect: 136432
Abstract: For windows platform, Incorrect interim patch version is displayed
under the heading “SELF-DESCRIBED APPLICATION SUPPORT PACKAGE” .
Additional Information: After installing the IF2 patch on SAP Agent 710FP2,
the support under “SELF-DESCRIBED APPLICATION SUPPORT PACKAGE” was
not getting updated earlier and remained 07100200. This defect is
now fixed and correct version, that is 07100202, gets updated for
support of TEMS, TEPS, and TEPD on windows platform.
Enhancements
--------------------
No Enhancements
----------------------------------
7.1.0.2-TIV-ITM_SAP-IF0001
----------------------------------
APARs
----------
APAR: IV81985
Abstract: Monitoring for SAP user types
Additional Information: The SAP agent monitored system information
for all the user types except the SYSTEM and SERVICE user
types. The docksa.odi is updated so that the SAP agent can
monitor the SYSTEM and SERVICE user types. The SYSTEM and
SERVICE user types along with their ENUM values are added
under properties of ‘/IBMMON/ITM_LOGON_INFORMATION' function
module in the docksa.odi. The agent side support files are
also updated to incorporate functionality for the two
additional users.
APAR: IV77994
Abstract: Problem with ITM SAP Agent on CRM3.0 basis version 610
Additional Information: Dynamic code is not supporting Basis 610. ABAP dump
occurs due to undefined variables for SAP Basis 610. To solve
this issue, the required variables are defined in the dynamic
code for SAP Basis 610.
Abstract: Problem with ITM SAP Agent on CRM3.0 basis version 610
Additional Information: Dynamic code is not supporting Basis 610. ABAP dump
occurs due to undefined variables for SAP Basis 610. To solve
this issue, the required variables are defined in the dynamic
code for SAP Basis 610.
APAR: IV78409
Abstract: SAP ABAP dump is occurring due to one unhandled exception
in the application
Additional Information: The SAP agent was throwing ABAP dump due to unhandled
exception in the SAP function modules such as,
'/ibmmon/itm_work_processes', '/ibmmon/itm_ccms_alerts',
'/ibmmon/itm_new_ccms_alerts', '/ibmmon/itm_r3_action', and
'/ibmmon/itm_buffer_perf'.
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: SAP changed the standard routine from SAP Basis 740
SP 11 onwards. Accordingly, the code is updated for the SAP ABAP
agent side '/IBMMON/ITM_NEW_CCMS_ALERTS' procedure to use SAP
standard routine.
Abstract: SAP ABAP dump is occurring due to one unhandled exception
in the application
Additional Information: The SAP agent was throwing ABAP dump due to unhandled
exception in the SAP function modules such as,
'/ibmmon/itm_work_processes', '/ibmmon/itm_ccms_alerts',
'/ibmmon/itm_new_ccms_alerts', '/ibmmon/itm_r3_action', and
'/ibmmon/itm_buffer_perf'.
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: SAP changed the standard routine from SAP Basis 740
SP 11 onwards. Accordingly, the code is updated for the SAP ABAP
agent side '/IBMMON/ITM_NEW_CCMS_ALERTS' procedure to use SAP
standard routine.
Defects
------------
No defects
Enhancements
----------------
Enhancement: 90113(RTC Id)
Abstract: As administrator I want to see CCMS and MAI Alerts from SAP
appearing on TEP during Day Light Saving mode.
Additional Information: The ITM SAP agent reads the last x minutes of CCMS
alerts, but when the clocks time is changed during the Daylight
Saving Time (DST) the agent stops collecting alert details until
the agent is restarted. Changes are made according to the
requirement to get CCMS and MAI alerts from SAP to appear on
Tivoli Enterprise Portal during the daylight saving mode.
Enhancement: 101538(RTC Id)
Abstract: As administrator I want to see default New CCMS design enabled for
CCMS Alerts attribute group
Additional Information: Changes are made to enable new CCMS design by
default for the SAP agent monitoring.
--------------------------------
7.1.0-TIV-ITM_SAP-FP0002
--------------------------------
------------
No defects
Enhancements
----------------
Enhancement: 90113(RTC Id)
Abstract: As administrator I want to see CCMS and MAI Alerts from SAP
appearing on TEP during Day Light Saving mode.
Additional Information: The ITM SAP agent reads the last x minutes of CCMS
alerts, but when the clocks time is changed during the Daylight
Saving Time (DST) the agent stops collecting alert details until
the agent is restarted. Changes are made according to the
requirement to get CCMS and MAI alerts from SAP to appear on
Tivoli Enterprise Portal during the daylight saving mode.
Enhancement: 101538(RTC Id)
Abstract: As administrator I want to see default New CCMS design enabled for
CCMS Alerts attribute group
Additional Information: Changes are made to enable new CCMS design by
default for the SAP agent monitoring.
--------------------------------
7.1.0-TIV-ITM_SAP-FP0002
--------------------------------
APARs
----------
APAR: IV61450
Abstract: REMOVE PERIOD START/END ATTRIBUTES OF XML MESSAGE LOGS
Additional Information: SAP Agent attributes 'Period Start' and
'Period End' are used by agent internally and aren't helpful
to customer in anyway. In order to hide them from attribute
view, the 'USAGE' and 'COST' tags are 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: IV61450
Abstract: REMOVE PERIOD START/END ATTRIBUTES OF XML MESSAGE LOGS
Additional Information: SAP Agent attributes 'Period Start' and
'Period End' are used by agent internally and aren't helpful
to customer in anyway. In order to hide them from attribute
view, the 'USAGE' and 'COST' tags are 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: 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 Function module
/ IBMMON/ITM_FILE_SYSTEM is gracefully handled towards File
Systems attribute group.
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 Function module
/ IBMMON/ITM_FILE_SYSTEM is gracefully handled towards File
Systems attribute group.
APAR: IV59060
Abstract: NAME ATTRIBUTE OF BUFFER PERFORMANCE ATTRIBUTE GROUP WAS
TRUNCATED AND GARBLED.
Additional Information: Name field for the attribute group
‘Buffer Performance’ has garbled characters for symbolic
languages like Japanese(JA) in Non-Unicode SAP systems. Fix is
provided by introducing a new field 'ENAME-Extended Name' with
increased character length in the Function Modules -
/IBMMON/ITM_BUFFER_PERF AND /IBMMON/ITM_BUFFER_PERF_64 to handle
the multi-byte character languages like Japanese(JA). A new
workspace with the attribute as "Ename-Extended Name" is also
added for Buffer Performance attribute group.
Abstract: NAME ATTRIBUTE OF BUFFER PERFORMANCE ATTRIBUTE GROUP WAS
TRUNCATED AND GARBLED.
Additional Information: Name field for the attribute group
‘Buffer Performance’ has garbled characters for symbolic
languages like Japanese(JA) in Non-Unicode SAP systems. Fix is
provided by introducing a new field 'ENAME-Extended Name' with
increased character length in the Function Modules -
/IBMMON/ITM_BUFFER_PERF AND /IBMMON/ITM_BUFFER_PERF_64 to handle
the multi-byte character languages like Japanese(JA). A new
workspace with the attribute as "Ename-Extended Name" is also
added for Buffer Performance attribute group.
APAR: IV52434
Abstract: ATTRLIB MISSING SLASH IF INSTANCE IS CREATED USING
ADDSYSTEM
Additional Information: 'sa_xa.exe' is used when 'addSystem' is
called. Wrong ATTRLIB path was getting created because of
missing '\'. This resulted in failure to start ksaagent after
reconfiguration. This was creating problem in HDC.
Abstract: ATTRLIB MISSING SLASH IF INSTANCE IS CREATED USING
ADDSYSTEM
Additional Information: 'sa_xa.exe' is used when 'addSystem' is
called. Wrong ATTRLIB path was getting created because of
missing '\'. This resulted in failure to start ksaagent after
reconfiguration. This was creating problem in HDC.
APAR: IV47613
Abstract: ABAP DUMPS DUE TO OVERFLOW IN '/IBMMON/ITM_CCMS_ALERTS'
(ALERT UNIQUE ID)
Additional Information: Overflow condition occurring due to Alert
Unique number exceeding the maximum length of ALUNIQNUM
in the Function Module '/IBMMON/ITM_CCMS_ALERTS' causes ABAP
dumps during CCMS processing by SAP agent. Fix is provided by
introducing a new field ‘EALUNIQNUM- Extended Alert Unique
Identifier’ with increased length to handle this overflow
condition. Also, a new attribute ' EALUNIQNUM-Extended Alert
Unique Identifier' is added under KSAALERTS attribute. Existing
workspace 'Alert Information' is modified with a new query that
holds this new attribute.
APAR: IV43091
Abstract: DESCRIBE THE REQUIREMENT FOR THE DDIC USER IN SAP
Additional Information: Multiple issues while upgrading SAP agent.
Technote published to describe the authorization requirement
for the DDIC User. Refer to Technote Link for more detail:
http://www.ibm.com/support/docview.wss?uid=swg21640739
Abstract: ABAP DUMPS DUE TO OVERFLOW IN '/IBMMON/ITM_CCMS_ALERTS'
(ALERT UNIQUE ID)
Additional Information: Overflow condition occurring due to Alert
Unique number exceeding the maximum length of ALUNIQNUM
in the Function Module '/IBMMON/ITM_CCMS_ALERTS' causes ABAP
dumps during CCMS processing by SAP agent. Fix is provided by
introducing a new field ‘EALUNIQNUM- Extended Alert Unique
Identifier’ with increased length to handle this overflow
condition. Also, a new attribute ' EALUNIQNUM-Extended Alert
Unique Identifier' is added under KSAALERTS attribute. Existing
workspace 'Alert Information' is modified with a new query that
holds this new attribute.
APAR: IV43091
Abstract: DESCRIBE THE REQUIREMENT FOR THE DDIC USER IN SAP
Additional Information: Multiple issues while upgrading SAP agent.
Technote published to describe the authorization requirement
for the DDIC User. Refer to Technote Link for more detail:
http://www.ibm.com/support/docview.wss?uid=swg21640739
Defects
------------
Defect: 59670
Abstract: ksapwd utility not working on Solaris 11 - 64 bit SPARC.
Additional Information: ksapwd not working on Solaris, Command get
executed without any result or output.
Defect: 58382
Abstract: Exception condition "GWY_COMMUNICATION_FAILURE" raised.
Additional Information:"GWY_COMMUNICATION_FAILURE" is
gracefully handled for the Function Module -
/IBMMON/ITM_GWY_CONNECTIONS towards Gateway Connections attribute
group.
Defect: 57881
Abstract: Take action failed when incorrect sap parameters in primary
and correct sap parameters in alternate1 are entered during agent
configuration on windows machine.
Additional Information: The connection mechanism tried to connect to
SAP system by giving higher priority to primary parameters
with which the agent is configured instead of with which the
agent connection is successful (maybe secondary or tertiary).
Changed the connection mechanism to rightly fetch the connection
parameters with which the agent connection is successful.
------------
Defect: 59670
Abstract: ksapwd utility not working on Solaris 11 - 64 bit SPARC.
Additional Information: ksapwd not working on Solaris, Command get
executed without any result or output.
Defect: 58382
Abstract: Exception condition "GWY_COMMUNICATION_FAILURE" raised.
Additional Information:"GWY_COMMUNICATION_FAILURE" is
gracefully handled for the Function Module -
/IBMMON/ITM_GWY_CONNECTIONS towards Gateway Connections attribute
group.
Defect: 57881
Abstract: Take action failed when incorrect sap parameters in primary
and correct sap parameters in alternate1 are entered during agent
configuration on windows machine.
Additional Information: The connection mechanism tried to connect to
SAP system by giving higher priority to primary parameters
with which the agent is configured instead of with which the
agent connection is successful (maybe secondary or tertiary).
Changed the connection mechanism to rightly fetch the connection
parameters with which the agent connection is successful.
Defect: 57879
Abstract: Test connection failed for incorrect primary parameters and
alternate1 correct parameters on windows machine.
Additional Information: The connection mechanism tried to connect to
SAP system by giving higher priority to Primary Parameters given
at the time of configuring agent instead of with which agent
connection is successful (alternate1 or alternate2). Changed
the connection mechanism to correctly fetch the Sap parameters
for alternate1 and alternate2 also with which the agent
connection had got successful.
Abstract: Test connection failed for incorrect primary parameters and
alternate1 correct parameters on windows machine.
Additional Information: The connection mechanism tried to connect to
SAP system by giving higher priority to Primary Parameters given
at the time of configuring agent instead of with which agent
connection is successful (alternate1 or alternate2). Changed
the connection mechanism to correctly fetch the Sap parameters
for alternate1 and alternate2 also with which the agent
connection had got successful.
Defect: 57155
Abstract: The predefined Launch definition not available for KSAIDOCS,
KSAALERTS, KSAXMLLOGS attribute group.
Additional Information: Queries for all three attribute groups
were changed to display additional fields. Since the launch
definitions weren't associated with the resultant query, they
were not visible. The launch definitions are associated with
the new queries to get them displayed.
Abstract: The predefined Launch definition not available for KSAIDOCS,
KSAALERTS, KSAXMLLOGS attribute group.
Additional Information: Queries for all three attribute groups
were changed to display additional fields. Since the launch
definitions weren't associated with the resultant query, they
were not visible. The launch definitions are associated with
the new queries to get them displayed.
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 Job Name not 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.
Abstract: ABAP Dumps when Job Name is not present in SAP standard
table.
Additional Information: Exception handling was missing for the
scenario of Job Name not 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.
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.
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: 38995
Abstract: Tivoli SAP agent causing dump in SAP on UNIX server.
Additional Information: Sometimes exceptions come while reading job
log. SAP function module BP_JOBLOG_READ throws exceptions if
error occurs while reading job log. As the function module
/IBMMON/ITM_JOB_LOG did not handle these exceptions, function
module terminates. Exceptions are handled in the function
module /IBMMON/ITM_JOB_LOG and exception details are written in
syslog which can be used for further reference. On TEP ‘Error
while reading job log ’ is seen for this job.
Abstract: Tivoli SAP agent causing dump in SAP on UNIX server.
Additional Information: Sometimes exceptions come while reading job
log. SAP function module BP_JOBLOG_READ throws exceptions if
error occurs while reading job log. As the function module
/IBMMON/ITM_JOB_LOG did not handle these exceptions, function
module terminates. Exceptions are handled in the function
module /IBMMON/ITM_JOB_LOG and exception details are written in
syslog which can be used for further reference. On TEP ‘Error
while reading job log ’ is seen for this job.
Enhancements
-----------------
Enhancement: 55877
Abstract: SAP Agent 7.1 Support for 7.4 non-unicode.
Additional Information: ABAP dump occur on basis 740
sa Program cancelled (job RDDEXECL, number 15260600)
Support for SAP Basis 740 added to meet RFE 54137.
Enhancement: 55375
Abstract: Need to show information about "error code" in the
query "XML Messages Logs"
Additional Information: The three fields viz. Message status
description, Error code and Error category were added
into the query to meet the RFE 55367.
-----------------
Enhancement: 55877
Abstract: SAP Agent 7.1 Support for 7.4 non-unicode.
Additional Information: ABAP dump occur on basis 740
sa Program cancelled (job RDDEXECL, number 15260600)
Support for SAP Basis 740 added to meet RFE 54137.
Enhancement: 55375
Abstract: Need to show information about "error code" in the
query "XML Messages Logs"
Additional Information: The three fields viz. Message status
description, Error code and Error category were added
into the query to meet the RFE 55367.
Enhancement: 55374
Abstract: Enable HDC for R\3_Oracle_Data_Base_Detail Attribute Group
Additional Information: Oracle Database Detail is enabled for
Historical data collection.
----------------------------------
7.1.0.1-TIV-ITM_SAP-IF0001
----------------------------------
Abstract: Enable HDC for R\3_Oracle_Data_Base_Detail Attribute Group
Additional Information: Oracle Database Detail is enabled for
Historical data collection.
----------------------------------
7.1.0.1-TIV-ITM_SAP-IF0001
----------------------------------
APARs
----------
APAR: IV51184
Abstract: FUNCTION MODULE "/IBMMON/ITM_SYS_LOG" GENERATING ABAP DUMP
Additional Information: "IBMMON/ITM_SYS_LOG is invoked every 10
minutes and it generates ABAP Dump like : Function Module
"/IBMMON/ITM_SYS_LOG" was called with parameter
"ITM_R3_LOG_RECORD".This parameter is not defined. Syslog
information is available from INS and GRP subnodes, but
problem only occurs while collecting data for :GRP subnode.
Problem occurs with MySAP Agent 620 IF15 and IF16.
APAR: IV46719
Abstract: ITCAMFORSAP7.1/SAP SYSLOG IS NOT DETECTED
Additional Information: Syslogs are not detected sometimes on SAP
Version 731. This problem is specific to SAP V731
The agent does not return system log information from
SAP V731 server due to SAP API change.
APAR: IV46184
Abstract: CCMS ALERTS OLDER THAN 3 MINUTES ARE NOT SET TO DONE WHEN
THE ALERT CONDITION IS CLOSED.
Additional Information: As the NEW CCMS Design is only collecting the
alerts for specified start and end time, we changed the logic
of comparison of previous and new collection of alert. With the
new ccms alert data collection, using DONE status to perform
autoclosure of the events, a problem occurs if the alerts are
older than 3 minutes. If you open an event, and wait longer than
3 minutes to close the event, the event does not get closed.
APAR: IV43860
Abstract: BSM_identity appended with GUID
Additional Information: BSM_identity is shown on TBSM tree for SAP
system was appended with GUID, due to incorrect value into the
BSM_Identity situations are not seen on TBSM tree which are
triggered on ITM side. This issue is resolved by changing Event
rule file & mapping file on TBSM Server and adding new DLA
attribute for mySAPABAPApplicationServer class in Agent DLA
book. The changes for EventIdentifierRules.xml,
CDM_TO_TBSM4x_MAP_Templates.xml and DLA file are detailed
mentioned in below technote:
Technote link:
http://www.ibm.com/support/docview.wss?uid=swg21646756
APAR: IV40032
Abstract: ABAP DUMPS STATING THAT FUNCTION MODULE WAS CALLED
INCORRECTLY
Additional Information: SAP has increased PFEVALUE length from 320 to
512. Same is mentioned in SAP note 0001582914.
Following ABAP dumps stating that function module was called
incorrectly are occurring:
The exception, which is assigned to class
'CX_SY_DYN_CALL_ILLEGAL_TYPE' was not caught in procedure
"/IBMMON/ITM_PERSIST_LAYER" "(FUNCTION)", nor was it propagated
by a RAISING clause.
APAR: IV41680
Abstract: CCMS ALERTS STATUS SET TO DONE IN THE NEXT DATA COLLECTION
USING THE NEW CCMS ALERT DATA COLLECTION METHOD INCORRECTLY
Additional Information: As the NEW CCMS Design is only collecting the
alerts for specified start and end time, we changed the
logic of comparison of previous and new collection of alert.
SAP AGENT is sending open and closed alerts for a given time
frame (Start and End time).
Open alerts are collected from SAP Standard function module and
closed/completed alerts are collected from SAP standard table
ALALERTDB. Currently no SAP API is available to collect closed
alerts in specified alert change time, so we are collecting the
completed alerts from ALALERTDB table according to the changed
time.
----------
APAR: IV51184
Abstract: FUNCTION MODULE "/IBMMON/ITM_SYS_LOG" GENERATING ABAP DUMP
Additional Information: "IBMMON/ITM_SYS_LOG is invoked every 10
minutes and it generates ABAP Dump like : Function Module
"/IBMMON/ITM_SYS_LOG" was called with parameter
"ITM_R3_LOG_RECORD".This parameter is not defined. Syslog
information is available from INS and GRP subnodes, but
problem only occurs while collecting data for :GRP subnode.
Problem occurs with MySAP Agent 620 IF15 and IF16.
APAR: IV46719
Abstract: ITCAMFORSAP7.1/SAP SYSLOG IS NOT DETECTED
Additional Information: Syslogs are not detected sometimes on SAP
Version 731. This problem is specific to SAP V731
The agent does not return system log information from
SAP V731 server due to SAP API change.
APAR: IV46184
Abstract: CCMS ALERTS OLDER THAN 3 MINUTES ARE NOT SET TO DONE WHEN
THE ALERT CONDITION IS CLOSED.
Additional Information: As the NEW CCMS Design is only collecting the
alerts for specified start and end time, we changed the logic
of comparison of previous and new collection of alert. With the
new ccms alert data collection, using DONE status to perform
autoclosure of the events, a problem occurs if the alerts are
older than 3 minutes. If you open an event, and wait longer than
3 minutes to close the event, the event does not get closed.
APAR: IV43860
Abstract: BSM_identity appended with GUID
Additional Information: BSM_identity is shown on TBSM tree for SAP
system was appended with GUID, due to incorrect value into the
BSM_Identity situations are not seen on TBSM tree which are
triggered on ITM side. This issue is resolved by changing Event
rule file & mapping file on TBSM Server and adding new DLA
attribute for mySAPABAPApplicationServer class in Agent DLA
book. The changes for EventIdentifierRules.xml,
CDM_TO_TBSM4x_MAP_Templates.xml and DLA file are detailed
mentioned in below technote:
Technote link:
http://www.ibm.com/support/docview.wss?uid=swg21646756
APAR: IV40032
Abstract: ABAP DUMPS STATING THAT FUNCTION MODULE WAS CALLED
INCORRECTLY
Additional Information: SAP has increased PFEVALUE length from 320 to
512. Same is mentioned in SAP note 0001582914.
Following ABAP dumps stating that function module was called
incorrectly are occurring:
The exception, which is assigned to class
'CX_SY_DYN_CALL_ILLEGAL_TYPE' was not caught in procedure
"/IBMMON/ITM_PERSIST_LAYER" "(FUNCTION)", nor was it propagated
by a RAISING clause.
APAR: IV41680
Abstract: CCMS ALERTS STATUS SET TO DONE IN THE NEXT DATA COLLECTION
USING THE NEW CCMS ALERT DATA COLLECTION METHOD INCORRECTLY
Additional Information: As the NEW CCMS Design is only collecting the
alerts for specified start and end time, we changed the
logic of comparison of previous and new collection of alert.
SAP AGENT is sending open and closed alerts for a given time
frame (Start and End time).
Open alerts are collected from SAP Standard function module and
closed/completed alerts are collected from SAP standard table
ALALERTDB. Currently no SAP API is available to collect closed
alerts in specified alert change time, so we are collecting the
completed alerts from ALALERTDB table according to the changed
time.
Limitations:
If SAP System is CEN(Centralized Monitoring) System SAP agent
fetches closed alerts from remote system from table
ALALERTDB. However while collecting these old alerts SAP agent
also takes care of performance issue or delay caused during
data collection.
To avoid any further delay in closed alerts data collection SAP
agent collects below fields from remote systems.
Customer should include only following attributes in closed
situation's formula
'ALSYSID' SAP System Name
'ALUNIQNUM' Alert Unique Identifier
'ALERTDATE' Alert Date
'ALERTTIME' Alert Time
'MTSYSID' Name of the SAP System
'MTUID' Monitoring Types ID
'MTMCNAME' Alert: Name of Monitoring Context
'MSEGNAME' Alert: Name of Monitoring Segment
'MTCLASS' MTE Class
'VALUE' Alert Value
'SEVERITY' Severity
'STATUS' Alert Status
'OBJECTNAME' Alert Object Name
'FIELDNAME' Alert Field Name
If SAP System is CEN(Centralized Monitoring) System SAP agent
fetches closed alerts from remote system from table
ALALERTDB. However while collecting these old alerts SAP agent
also takes care of performance issue or delay caused during
data collection.
To avoid any further delay in closed alerts data collection SAP
agent collects below fields from remote systems.
Customer should include only following attributes in closed
situation's formula
'ALSYSID' SAP System Name
'ALUNIQNUM' Alert Unique Identifier
'ALERTDATE' Alert Date
'ALERTTIME' Alert Time
'MTSYSID' Name of the SAP System
'MTUID' Monitoring Types ID
'MTMCNAME' Alert: Name of Monitoring Context
'MSEGNAME' Alert: Name of Monitoring Segment
'MTCLASS' MTE Class
'VALUE' Alert Value
'SEVERITY' Severity
'STATUS' Alert Status
'OBJECTNAME' Alert Object Name
'FIELDNAME' Alert Field Name
Pre-Requisite:
1. To collect the rfc destinations of remote systems
Pre-Requisite is that while configuring CEN the below RFC
Destinations should be present according to the recommended
naming convention and these should be active in RZ21. These
steps are mentioned by SAP while configuring CEN system to
monitor multiple systems, please check the link below.
https://help.sap.com/saphelp_nw70/helpdata/en/84/d2b33a687d747ee10000000a114084
/content.htm
RFC Destination: Enter the name for the RFC connection; we
recommend <SID>_RZ20_COLLECTfor the RFC destination for data
collection, <SID>_RZ20_ANALYZE for the RFC destination to
execute the analysis method.
Connection Type: Enter 3 (for ABAP system).
1. To collect the rfc destinations of remote systems
Pre-Requisite is that while configuring CEN the below RFC
Destinations should be present according to the recommended
naming convention and these should be active in RZ21. These
steps are mentioned by SAP while configuring CEN system to
monitor multiple systems, please check the link below.
https://help.sap.com/saphelp_nw70/helpdata/en/84/d2b33a687d747ee10000000a114084
/content.htm
RFC Destination: Enter the name for the RFC connection; we
recommend <SID>_RZ20_COLLECTfor the RFC destination for data
collection, <SID>_RZ20_ANALYZE for the RFC destination to
execute the analysis method.
Connection Type: Enter 3 (for ABAP system).
2. Authorization might be required to read the table ALALERTDB
from Remote systems however we have added an authorization:
S_TABU_DIS to IBMMON_AGENT User which is used to collect
data from remote systems. Please refer to
ITCAM_SAP_Agent_HowTos.pdf for steps for adding authorizations.
Note: If any error happens while reading the remote system agent
writes a syslog entry like below example
'Error reading ALALERTDB table from remote system'.
You can check this entry from SM21 transaction code.
APAR: IV38554
Abstract: /IBMMON/ITM_IDOCS SYSTEM_FAILURE NO MORE STORAGE SPACE
AVAILABLE FOR EXTENSDING AN INTERNAL TABLE
Additional Information: After applying 7.1.0-TIV-ITM_SAP-FP0001
mySAP agent ABAP dump occurs for IDOC function module.
Performance improvement is done in function module
/IBMMON/ITM_IDOCS. Agent collects the status details
of IDOCS according to the IDOC number.
from Remote systems however we have added an authorization:
S_TABU_DIS to IBMMON_AGENT User which is used to collect
data from remote systems. Please refer to
ITCAM_SAP_Agent_HowTos.pdf for steps for adding authorizations.
Note: If any error happens while reading the remote system agent
writes a syslog entry like below example
'Error reading ALALERTDB table from remote system'.
You can check this entry from SM21 transaction code.
APAR: IV38554
Abstract: /IBMMON/ITM_IDOCS SYSTEM_FAILURE NO MORE STORAGE SPACE
AVAILABLE FOR EXTENSDING AN INTERNAL TABLE
Additional Information: After applying 7.1.0-TIV-ITM_SAP-FP0001
mySAP agent ABAP dump occurs for IDOC function module.
Performance improvement is done in function module
/IBMMON/ITM_IDOCS. Agent collects the status details
of IDOCS according to the IDOC number.
Defects
------------
Defect: 39686
Abstract: Syslog causing ABAP dump for Group Sub Node.
Additional Information: Issue specific to SAP 7.02 and 7.31.
Problem occurs always with :GRP node,
ABAP Dump CX_SY_DYN_CALL_PARAM_NOT_FOUND
Function module "/IBMMON/ITM_SYS_LOG" was called with the
parameter "ITM_R3_LOG_RECORD". This parameter is not defined.
Defect: 39013/34098
Abstract: SAP Agent missing some classes in DLA Book.
Additional Information: MySAPSqlServer and MySAPOracleInstance
classes are not present into the SAP agent DLA book. Those
classes have been added to differentiate the database type into
TADDM server.
Defect: 39011
Abstract: Situation and HDC are not working for CCMS alerts in first
call sometimes
Additional Information: Issue fixed with Situations not triggers in
first CCMS data call after agent is started. First call CCMS
data not collected by HDC.
Defect: 39010
Abstract: 710FP1IF1 Workload Performance Workspaces Views are not
aligned properly
Additional Information: Two graph view of Transaction Performance
Workspace under subnode Workload Performance is merged into
one graph view name "Average Response Time Greater Than 1000
Milliseconds". It shows all information of graph Average
Response 1000 to 5000 Milliseconds and Average Response
Greater Than 5000 Milliseconds in one graph view.
Defect: 39008
Abstract: Remove "Time Span" query icon from 'System Log' workspace
Additional Information: Need to remove "Time Span" query icon from
'System Log' workspace as system log is pure event attribute
group.
Defect: 39006/29355
Abstract: IDML book certification fails in case of Multiple Instance
SAP system.
Additional Information: After generating IDML book on Multiple
Instance SAP system, IBM Discovery Library Certification Tool
Version 2.4.4. is failed with error as The 'id' attribute value
already exists.
Defect: 38998
Abstract: Unable to interpret X as a number. in function module
/IBMMON/ITM_HOSTS
Additional Information: The "R3_Instance_Down2_Crit" situation was
not firing as soon as SAP dialog instance or application
instance stopped. The reason was the relative navigator was
going offline as soon as SAP instance stopped.
Defect: 38996
Abstract: IDOC Number not coming correctly on TEP workspace
Additional Information: IDOC Number displayed on TEP workspace not
matching with SAP IDOC number. Issue fixed in ABAP.
Defect: 38995
Abstract: Tivoli SAP agent dumping within SAP on UNIX server
Additional Information: Sometimes exceptions come while reading job
log. SAP function module BP_JOBLOG_READ throws exceptions if
error occurs while reading job log. As the function module
/IBMMON/ITM_JOB_LOG did not handle these exceptions, function
module terminates. Exceptions are handled in the function
module /IBMMON/ITM_JOB_LOG and exception details are written in
syslog which can be used for further reference. On TEP ‘Error
while reading job log’ is seen for this job.
Defect: 38514
Abstract: Instance down situation is not firing
Additional Information: The "R3_Instance_Down2_Crit" situation was
not firing as soon as SAP dialog instance or application
instance stopped. The reason was the relative navigator was
going offline as soon as SAP instance stopped.
------------
Defect: 39686
Abstract: Syslog causing ABAP dump for Group Sub Node.
Additional Information: Issue specific to SAP 7.02 and 7.31.
Problem occurs always with :GRP node,
ABAP Dump CX_SY_DYN_CALL_PARAM_NOT_FOUND
Function module "/IBMMON/ITM_SYS_LOG" was called with the
parameter "ITM_R3_LOG_RECORD". This parameter is not defined.
Defect: 39013/34098
Abstract: SAP Agent missing some classes in DLA Book.
Additional Information: MySAPSqlServer and MySAPOracleInstance
classes are not present into the SAP agent DLA book. Those
classes have been added to differentiate the database type into
TADDM server.
Defect: 39011
Abstract: Situation and HDC are not working for CCMS alerts in first
call sometimes
Additional Information: Issue fixed with Situations not triggers in
first CCMS data call after agent is started. First call CCMS
data not collected by HDC.
Defect: 39010
Abstract: 710FP1IF1 Workload Performance Workspaces Views are not
aligned properly
Additional Information: Two graph view of Transaction Performance
Workspace under subnode Workload Performance is merged into
one graph view name "Average Response Time Greater Than 1000
Milliseconds". It shows all information of graph Average
Response 1000 to 5000 Milliseconds and Average Response
Greater Than 5000 Milliseconds in one graph view.
Defect: 39008
Abstract: Remove "Time Span" query icon from 'System Log' workspace
Additional Information: Need to remove "Time Span" query icon from
'System Log' workspace as system log is pure event attribute
group.
Defect: 39006/29355
Abstract: IDML book certification fails in case of Multiple Instance
SAP system.
Additional Information: After generating IDML book on Multiple
Instance SAP system, IBM Discovery Library Certification Tool
Version 2.4.4. is failed with error as The 'id' attribute value
already exists.
Defect: 38998
Abstract: Unable to interpret X as a number. in function module
/IBMMON/ITM_HOSTS
Additional Information: The "R3_Instance_Down2_Crit" situation was
not firing as soon as SAP dialog instance or application
instance stopped. The reason was the relative navigator was
going offline as soon as SAP instance stopped.
Defect: 38996
Abstract: IDOC Number not coming correctly on TEP workspace
Additional Information: IDOC Number displayed on TEP workspace not
matching with SAP IDOC number. Issue fixed in ABAP.
Defect: 38995
Abstract: Tivoli SAP agent dumping within SAP on UNIX server
Additional Information: Sometimes exceptions come while reading job
log. SAP function module BP_JOBLOG_READ throws exceptions if
error occurs while reading job log. As the function module
/IBMMON/ITM_JOB_LOG did not handle these exceptions, function
module terminates. Exceptions are handled in the function
module /IBMMON/ITM_JOB_LOG and exception details are written in
syslog which can be used for further reference. On TEP ‘Error
while reading job log’ is seen for this job.
Defect: 38514
Abstract: Instance down situation is not firing
Additional Information: The "R3_Instance_Down2_Crit" situation was
not firing as soon as SAP dialog instance or application
instance stopped. The reason was the relative navigator was
going offline as soon as SAP instance stopped.
Enhancements
-----------------
-----------------
Enhancement: 39012/27843
Abstract: CCMS current state monitoring filter
Additional Information: Currently /IBMMON/ITM_CCMS_MTE_STATE function
module retrieves all records with states green, red, yellow etc.
Situations which are associated with this attribute use only red
and yellow states. A new configurable “Green_Alerts check box”
option at ABAP side is added under transaction
/n/ibmmon/itm_ccmsmon. If this check box is checked then
Function module retrieves all MTE states and if it is
unchecked then only red and yellow state is retrieved.
Note: By default it is unchecked.
Steps To Enable Green alerts state -
1) Logon to SAP GUI.
2) Execute “/n/IBMMON/ITM_CONFIG” transaction code
3) click /IBMMON/ITM_CCMSMON
4) Check “Green Alerts” checkbox
5) Save changes.
Enhancement: 38997
Abstract: Alert Object Number and MTE name attributes added in
Display Item.
Additional Information: incorporated Alert Object Number and MTE name
attribute in Display Item for
“Solution Manager System Monitoring Alerts" attribute group.
Enhancement: 38903
Abstract: Allow "IDOC number" to set as display item in situations
Additional Information: Previously "IDOC number was not available to
set as display item in situations. Now changes are made to allow
user to set "IDOC number" as display item.
Enhancement: 38724
Abstract: The "Client" column is required for IDOC Information view
Additional Information: As the "IDOC Information" is supporting multi
-client, So the "Client" column was required for the
"IDOC Information" view of the "Data Transfer Information"
workspace to differentiate the respective client's data.
Added "Client" column under this task.
---------------------------------
7.1.0-TIV-ITM_SAP-FP0001
---------------------------------
Abstract: CCMS current state monitoring filter
Additional Information: Currently /IBMMON/ITM_CCMS_MTE_STATE function
module retrieves all records with states green, red, yellow etc.
Situations which are associated with this attribute use only red
and yellow states. A new configurable “Green_Alerts check box”
option at ABAP side is added under transaction
/n/ibmmon/itm_ccmsmon. If this check box is checked then
Function module retrieves all MTE states and if it is
unchecked then only red and yellow state is retrieved.
Note: By default it is unchecked.
Steps To Enable Green alerts state -
1) Logon to SAP GUI.
2) Execute “/n/IBMMON/ITM_CONFIG” transaction code
3) click /IBMMON/ITM_CCMSMON
4) Check “Green Alerts” checkbox
5) Save changes.
Enhancement: 38997
Abstract: Alert Object Number and MTE name attributes added in
Display Item.
Additional Information: incorporated Alert Object Number and MTE name
attribute in Display Item for
“Solution Manager System Monitoring Alerts" attribute group.
Enhancement: 38903
Abstract: Allow "IDOC number" to set as display item in situations
Additional Information: Previously "IDOC number was not available to
set as display item in situations. Now changes are made to allow
user to set "IDOC number" as display item.
Enhancement: 38724
Abstract: The "Client" column is required for IDOC Information view
Additional Information: As the "IDOC Information" is supporting multi
-client, So the "Client" column was required for the
"IDOC Information" view of the "Data Transfer Information"
workspace to differentiate the respective client's data.
Added "Client" column under this task.
---------------------------------
7.1.0-TIV-ITM_SAP-FP0001
---------------------------------
APARs
----------
APAR: IV36588
Abstract: QRFC DATA IS COMING SHOULD BE IDENTIFIED BY CLIENT
Additional Information: For qRFC workspace data is not coming for all
clients even if agent is configured with single client as
expected. Issue is fixed and data is expected from all clients
configured on monitoring sap system.
APAR: IV36092
Abstract: SAP AGENT APPL SUPPORT MISMATCH BETWEEN TEP CLIENT AND
SERVER
Additional Information: After applying 7.1.0-TIV-ITM_SAP-IF0001 mySAP
agent the TEP browser application support version file is not
updated. As a result it displays constant warnings on TEPS and
TEP browser with warning message "Application Support Mismatch".
Client version displayed is 07100000 and Servers Version is
0710001. This warning message issue fixed in this release.
APAR: IV35790
Abstract: TCR REPROT GIVES ERROR SQL020N
Additional Information: After applying mySAP agent
7.1 GA/7.1.0-TIV-ITM_SAP-IF0001 Following predefined Cognos
report fails with error SQL0204N:
"SAP Agent ICM Monitoring Performance report"
----------
APAR: IV36588
Abstract: QRFC DATA IS COMING SHOULD BE IDENTIFIED BY CLIENT
Additional Information: For qRFC workspace data is not coming for all
clients even if agent is configured with single client as
expected. Issue is fixed and data is expected from all clients
configured on monitoring sap system.
APAR: IV36092
Abstract: SAP AGENT APPL SUPPORT MISMATCH BETWEEN TEP CLIENT AND
SERVER
Additional Information: After applying 7.1.0-TIV-ITM_SAP-IF0001 mySAP
agent the TEP browser application support version file is not
updated. As a result it displays constant warnings on TEPS and
TEP browser with warning message "Application Support Mismatch".
Client version displayed is 07100000 and Servers Version is
0710001. This warning message issue fixed in this release.
APAR: IV35790
Abstract: TCR REPROT GIVES ERROR SQL020N
Additional Information: After applying mySAP agent
7.1 GA/7.1.0-TIV-ITM_SAP-IF0001 Following predefined Cognos
report fails with error SQL0204N:
"SAP Agent ICM Monitoring Performance report"
TIP console displays following:
UDA-SQL-0353 An error was detected while processing the SQL
request.[IBM][CLI Driver][DB2/NT64] SQL0204N
"ITMUSER.PI_ICM_MON_INFO_DV" is an undefined name.
SQLSTATE=42704 RSV-SRV-0042 Trace back:RSReportService.cpp(779):
QFException: CCL_CAUGHT:
RSReportService::process()RSReportServiceMethod.cpp(UDA-SQL-0353
Issue is fixed in this release.
APAR: IV33731
Abstract: SITUATION FOR ICM MONITORING NOT WORKING WHEN ICM STATUS IS
'NOT RUNNING'
Additional Information: After applying mySAP agent 7.1 GA situation
for ICM monitoring not working when ICM status is 'Not Running'.
When ICM service is not running, then ABAP function module gives
ABAP dump and fails to handle this shutdown situation. Instead
of sending 0 value it terminates with "RAISE_EXCEPTION"
ICM_ERROR. Here situation-monitoring ICM shutdown does not gets
any value so fails to fire alarms.
APAR: IV33539
Abstract: MULTIBYTES CHARS WAS CUT OFF INCORRECTLY IN MESSAGE TEXT
ATTRIB
Additional Information: When a multiple bytes character like Japanese
character is overlaid before and behind 78th bytes in Message
Text attribute of System Log attribute group, the character is
cut off at the middle of the character incorrectly. Then, the
character is garbled. As a result, the event isn't formed
correctly in Netcool EIF probe and it cannot handle the event.
APAR: IV33183
Abstract: SAP AGENT SOMETIMES FAILED TO COLLECT SYSTEM LOG DATA
Additional Information: With 620 IF0015 mySAP agent sometimes failed
to collect System Log Information. As a result all of situation
of SAP syslog monitor delays around 15 minutes. Issue is fixed
in this build and change is done to modify the default value of
SYSLOG_FREQUENCY. Default value is 600 seconds.
How To change SYSLOG_FREQUENCY.
1. For Windows: Set SYSLOG_FREQUENCY=180 in an agent specific
configuration file
Example:<candle home>\tmaitm6\ksaenv_<sid>
2. For Non-Windows: Set SYSLOG_FREQUENCY=180 in an agent
specific configuration file
Example:<candle home>/config/sa_<sid>.config
Recommended values are between 5 to 10 minutes.
APAR: IV32752
Abstract: MYSAP AGENT FILE SYSTEMS WORKSPACE NOT DISPLAYING
FILESYSTEM NAMES FOR NON-UNICODE SAP SYSTEMS
Additional Information: After applying mySAP agent 7.1 GA File
Systems Workspace not displaying Filesystem names for
non-Unicode sap Systems. This is expected behavior and agent
running on non-Unicode sap system does not show any value.
There is no applicable data for such fields.
APAR: IV27160
Abstract: Situation formula was not correct in SAP Agent 710 UG
Additional Information: The issue is related to some of the Situation
formulas listed in the User's Guide "Chapter 5: Situations
reference" were not correct. This is fixed in User's Guide of
this release.
APAR: IV25676
Abstract: ITM for SAP 6.2.0 how to monitor SAP Central instance outage
Additional Information: After applying 6.2.0-TIV-ITM_SAP-IF0014 in
multiple SAP instances setup if both SAP Instances, including
the Central Instance is down then System_Down situation only
fires once, indicating that Application Instance is down. So
the issue is that up to now we never have seen any System_Down
Alert indicating that the Central Instance is down.
APAR: IV25294
Abstract: Upgrade process information not clear in user guide
Additional Information: The Agent upgrade procedure is updated in
User's Guide of this release.
UDA-SQL-0353 An error was detected while processing the SQL
request.[IBM][CLI Driver][DB2/NT64] SQL0204N
"ITMUSER.PI_ICM_MON_INFO_DV" is an undefined name.
SQLSTATE=42704 RSV-SRV-0042 Trace back:RSReportService.cpp(779):
QFException: CCL_CAUGHT:
RSReportService::process()RSReportServiceMethod.cpp(UDA-SQL-0353
Issue is fixed in this release.
APAR: IV33731
Abstract: SITUATION FOR ICM MONITORING NOT WORKING WHEN ICM STATUS IS
'NOT RUNNING'
Additional Information: After applying mySAP agent 7.1 GA situation
for ICM monitoring not working when ICM status is 'Not Running'.
When ICM service is not running, then ABAP function module gives
ABAP dump and fails to handle this shutdown situation. Instead
of sending 0 value it terminates with "RAISE_EXCEPTION"
ICM_ERROR. Here situation-monitoring ICM shutdown does not gets
any value so fails to fire alarms.
APAR: IV33539
Abstract: MULTIBYTES CHARS WAS CUT OFF INCORRECTLY IN MESSAGE TEXT
ATTRIB
Additional Information: When a multiple bytes character like Japanese
character is overlaid before and behind 78th bytes in Message
Text attribute of System Log attribute group, the character is
cut off at the middle of the character incorrectly. Then, the
character is garbled. As a result, the event isn't formed
correctly in Netcool EIF probe and it cannot handle the event.
APAR: IV33183
Abstract: SAP AGENT SOMETIMES FAILED TO COLLECT SYSTEM LOG DATA
Additional Information: With 620 IF0015 mySAP agent sometimes failed
to collect System Log Information. As a result all of situation
of SAP syslog monitor delays around 15 minutes. Issue is fixed
in this build and change is done to modify the default value of
SYSLOG_FREQUENCY. Default value is 600 seconds.
How To change SYSLOG_FREQUENCY.
1. For Windows: Set SYSLOG_FREQUENCY=180 in an agent specific
configuration file
Example:<candle home>\tmaitm6\ksaenv_<sid>
2. For Non-Windows: Set SYSLOG_FREQUENCY=180 in an agent
specific configuration file
Example:<candle home>/config/sa_<sid>.config
Recommended values are between 5 to 10 minutes.
APAR: IV32752
Abstract: MYSAP AGENT FILE SYSTEMS WORKSPACE NOT DISPLAYING
FILESYSTEM NAMES FOR NON-UNICODE SAP SYSTEMS
Additional Information: After applying mySAP agent 7.1 GA File
Systems Workspace not displaying Filesystem names for
non-Unicode sap Systems. This is expected behavior and agent
running on non-Unicode sap system does not show any value.
There is no applicable data for such fields.
APAR: IV27160
Abstract: Situation formula was not correct in SAP Agent 710 UG
Additional Information: The issue is related to some of the Situation
formulas listed in the User's Guide "Chapter 5: Situations
reference" were not correct. This is fixed in User's Guide of
this release.
APAR: IV25676
Abstract: ITM for SAP 6.2.0 how to monitor SAP Central instance outage
Additional Information: After applying 6.2.0-TIV-ITM_SAP-IF0014 in
multiple SAP instances setup if both SAP Instances, including
the Central Instance is down then System_Down situation only
fires once, indicating that Application Instance is down. So
the issue is that up to now we never have seen any System_Down
Alert indicating that the Central Instance is down.
APAR: IV25294
Abstract: Upgrade process information not clear in user guide
Additional Information: The Agent upgrade procedure is updated in
User's Guide of this release.
Defects
------------
------------
Defect: 189839
Abstract: unwanted log statement
Additional Information: After applying mySAP agent 7.1 GA
log files are filled up with unwanted debug statements.
Defect: 188441
Abstract: Unexpected spaces in formula column of manage situation
view
Additional Information: The problem is that there are unexpected
spaces observed under the formula column for few situations in
manage situation view of SAP 7.1 agent’s node at TEP.
Affected situations were:
R3_Alert_Abort_Update_Crit
R3_Alert_DB_Warn
R3_AlertNo_Update_Crit
R3_Alert_Output_Pending
R3_Alert_Pend_Update_Crit
R3_Alert_System_Down
Defect: 186180
Abstract: ZERO VALUES IN SAP WORKSPACE FOR FRONT END NETWORK 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.
Defect: 33840
Abstract: SA 710FP01 Cert Issue fix with new part number
Additional Information: After 710 FP001 published on 12 April,
ksa_resources.jar certificate expires on June 10. Issue fixed in
republished 710 FP001 build.
Defect: 30281
Abstract: Self-Describing Agent Not working for window in Remote
Deployment
Additional Information: After remote deployment of SAP Agent, SDA
Support is not getting installed on Tivoli Enterprise Monitoring
server.
Defect: 31264
Abstract: Unwanted error's while executing the utility programs
Additional Information: After executing the Utility programs below
unwanted errors observed.
[root@ps0831 bin]# ./ksanfy
./ksanfy[2]: /bin: cannot execute [Is a directory]
./ksanfy[3]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[4]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[5]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[6]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[7]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[8]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[9]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[10]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[11]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[12]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[13]: **************************************************
***************************************
/: not found [No such file or directory]
Defect: 31233
Abstract: RFC connection issue while using Alternate1 and Alternate2
configuration settings in case of non-windows Platform.
Additional Information: During configuring the SAP Agent, if the
Alternate1 and Alternate2 configurations are provided, then
the agent while connecting was using the incorrect host, SAP
system number, gateway and gateway service combination. This
is fixed in this release.
Defect: 29171
Abstract: Need to update the user guide for the prerequisites of ksh
while installing the SAP Agent
Additional Information: This prerequisite is in case of Remote
installation on Unix or Linux system. This is fixed in User's
Guide of this release in "Chapter 2: Agent installation and
configuration".
Defect: 28518
Abstract: Spool Process (sum) column values are not displaying
completely due to alignment in TCR Instance Performance Report.
Additional Information: The problem is that the Spool Process (sum)
column data is cut for IE6,7 into result table. This is fixed
in this release.
Abstract: unwanted log statement
Additional Information: After applying mySAP agent 7.1 GA
log files are filled up with unwanted debug statements.
Defect: 188441
Abstract: Unexpected spaces in formula column of manage situation
view
Additional Information: The problem is that there are unexpected
spaces observed under the formula column for few situations in
manage situation view of SAP 7.1 agent’s node at TEP.
Affected situations were:
R3_Alert_Abort_Update_Crit
R3_Alert_DB_Warn
R3_AlertNo_Update_Crit
R3_Alert_Output_Pending
R3_Alert_Pend_Update_Crit
R3_Alert_System_Down
Defect: 186180
Abstract: ZERO VALUES IN SAP WORKSPACE FOR FRONT END NETWORK 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.
Defect: 33840
Abstract: SA 710FP01 Cert Issue fix with new part number
Additional Information: After 710 FP001 published on 12 April,
ksa_resources.jar certificate expires on June 10. Issue fixed in
republished 710 FP001 build.
Defect: 30281
Abstract: Self-Describing Agent Not working for window in Remote
Deployment
Additional Information: After remote deployment of SAP Agent, SDA
Support is not getting installed on Tivoli Enterprise Monitoring
server.
Defect: 31264
Abstract: Unwanted error's while executing the utility programs
Additional Information: After executing the Utility programs below
unwanted errors observed.
[root@ps0831 bin]# ./ksanfy
./ksanfy[2]: /bin: cannot execute [Is a directory]
./ksanfy[3]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[4]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[5]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[6]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[7]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[8]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[9]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[10]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[11]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[12]: ksamsgf.msg: not found [No such file or directory]
./ksanfy[13]: **************************************************
***************************************
/: not found [No such file or directory]
Defect: 31233
Abstract: RFC connection issue while using Alternate1 and Alternate2
configuration settings in case of non-windows Platform.
Additional Information: During configuring the SAP Agent, if the
Alternate1 and Alternate2 configurations are provided, then
the agent while connecting was using the incorrect host, SAP
system number, gateway and gateway service combination. This
is fixed in this release.
Defect: 29171
Abstract: Need to update the user guide for the prerequisites of ksh
while installing the SAP Agent
Additional Information: This prerequisite is in case of Remote
installation on Unix or Linux system. This is fixed in User's
Guide of this release in "Chapter 2: Agent installation and
configuration".
Defect: 28518
Abstract: Spool Process (sum) column values are not displaying
completely due to alignment in TCR Instance Performance Report.
Additional Information: The problem is that the Spool Process (sum)
column data is cut for IE6,7 into result table. This is fixed
in this release.
Enhancement: 187311
Abstract: New CCMS Enhancement to improve the performance
Additional Information: Alerts are missing due to the collection of
the huge number of alert records in a single call. In this case
9911/9912 alerts are getting generated to notify user that some
alerts are missed in data collection. Here 9911 alert is due to
huge number of alerts and 9912 are generated due to rfc failure
or network delay. Please refer to the mySAP agent 7.1 FP1 User Guide
for more details on new CCMS design.
Abstract: New CCMS Enhancement to improve the performance
Additional Information: Alerts are missing due to the collection of
the huge number of alert records in a single call. In this case
9911/9912 alerts are getting generated to notify user that some
alerts are missed in data collection. Here 9911 alert is due to
huge number of alerts and 9912 are generated due to rfc failure
or network delay. Please refer to the mySAP agent 7.1 FP1 User Guide
for more details on new CCMS design.
Enhancements
-----------------
Enhancement: 194134
Abstract: mySAP Agent 7.1.0: certification for SAP release 7.31
Additional Information: After applying mySAP agent
7.1 GA/7.1.0-TIV-ITM_SAP-IF0001 transport on SAP basis version
731 following error occurs when trying to add the agents
transport to SAP :
"Stopping error 12 during EXECUTION OF REPORTS AFTER PUT"
In SAP, got the following error message (translated from German):
The data object RZLLITAB contains no component with name
IPV6_ADDRESS. Module: /IBMMON/ITM_LOGON_GROUPS
-------------------------------
7.1.0-TIV-ITM_SAP-IF0001
-------------------------------
-----------------
Enhancement: 194134
Abstract: mySAP Agent 7.1.0: certification for SAP release 7.31
Additional Information: After applying mySAP agent
7.1 GA/7.1.0-TIV-ITM_SAP-IF0001 transport on SAP basis version
731 following error occurs when trying to add the agents
transport to SAP :
"Stopping error 12 during EXECUTION OF REPORTS AFTER PUT"
In SAP, got the following error message (translated from German):
The data object RZLLITAB contains no component with name
IPV6_ADDRESS. Module: /IBMMON/ITM_LOGON_GROUPS
-------------------------------
7.1.0-TIV-ITM_SAP-IF0001
-------------------------------
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.
----------
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.
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:
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.
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.
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.
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.
Defects
------------
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: 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.
Abstract: TEMS and TEPS server upgrade is not working.
Defect: 188799
Abstract: Transport import failed for 4.6 SAP System
Abstract: Transport 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
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 are 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 available in Interim Fix 1.
Defect: 185556
Abstract: Reconciling is not happening at TADDM for SAP IDLM Book.
Abstract: CVT1IF1:SWG Inventory Tag files are 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 available in Interim Fix 1.
Defect: 185556
Abstract: Reconciling is not happening at TADDM for SAP IDLM Book.
Defect: 184469
Abstract: 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
Abstract: 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: 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
Abstract: 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: 166690
Abstract: SAP Agent Syslog not working on SAP System 702
Additional Information: This problem is specific to SAP V7.0.2
The agent does not return system log information from
SAP V7.0.2 server due to SAP API change.
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 truncates 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: The correct state topology view is not
displayed in the <local_SID>-<remote_SID>_CCMS_alerts :Grp
managed system, 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"
Abstract: SAP Agent Syslog not working on SAP System 702
Additional Information: This problem is specific to SAP V7.0.2
The agent does not return system log information from
SAP V7.0.2 server due to SAP API change.
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 truncates 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: The correct state topology view is not
displayed in the <local_SID>-<remote_SID>_CCMS_alerts :Grp
managed system, 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"
Enhancements
-----------------
Enhancement: 187474
Abstract: Support for PI/XI 7.0 SAP system
-----------------
Enhancement: 187474
Abstract: Support for PI/XI 7.0 SAP system
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 Readme ,
Version 7.1.0-TIV-ITM_SAP-FP0003
Tivoli Composite Application Manager Agent for SAP Applications Readme ,
Version 7.1.0-TIV-ITM_SAP-FP0003
The following website contains the latest certification information:
Software Product Compatibility Reports (SPCR)
https://www.ibm.com/software/reports/compatibility/clarity/index.html
Software Product Compatibility Reports (SPCR)
https://www.ibm.com/software/reports/compatibility/clarity/index.html
You can also find system requirements for SAP Applications agent 7.1 at
https://www.ibm.com/docs/en/itcam-app-mgr/7.2.0?topic=applications-prerequisites
Note: From SAP Agent 7.1.0 Fix Pack 3 version, minimum ITM level required is ITM 6.3.0 Fix Pack 7 SP6 or above.
SAP Applications agent 7.1 User's Guide:
https://www.ibm.com/docs/en/itcam-app-mgr/7.2.0?topic=agent-version-71-fix-pack-1
Installing and enabling application support:
https://www.ibm.com/docs/en/tivoli-monitoring/6.3.0.2?topic=monitoring-
installing-enabling-application-support
https://www.ibm.com/docs/en/tivoli-monitoring/6.3.0.2?topic=monitoring-
installing-enabling-application-support
3.1 Upgrade prerequisites for this fix
------------------------------------------
Before starting agent upgrade ensure to have below framework level
------------------------------------------
Before starting agent upgrade ensure to have below framework level
installed in your agent installation directory:
Framework level: ITM 6.3.0 Fix Pack 7 SP6 or above.
Note: The above prerequisite is applicable for Windows platform.
Agent prerequisite level for this fix is as follows:
None
Because this fix is cumulative, it can be installed on any fix level
for this version, release, and modification level above the
prerequisite.
for this version, release, and modification level above the
prerequisite.
4.0 Image directory contents
=============================
Electronic Part Number: ITCAM Agent for SAP Applications M057JML
5.0 Installation instructions
=============================
When this fix pack image is downloaded from Passport Advantage, the following
rules are applicable:
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 the existing or new installations.
rules are applicable:
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 the 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.
-----------------------------
- 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 location
of IBM Tivoli Monitoring installation directory. The default value for
CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM' on
Windows systems.
of 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.
environment variable to the IBM Tivoli Monitoring installation
directory.
For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME
-As there is no uninstall utility for this fix pack, be sure to
perform a backup of your environment before installing the fix pack.
perform a backup of your environment before installing the 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.
--------------------------
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.
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.0-TIV-ITM_SAP-FP0001
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.
Agent for SAP Applications Version 7.1.0-TIV-ITM_SAP-FP0001
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.
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'.
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
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
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.
-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.
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 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.
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 07100300
-n <Managed system name>
-v 07100300
On Windows systems:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>
> %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.
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 07100300
-n <Managed system name>
-v 07100300
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.
- 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.
Note: If SDA feature is enabled at the HUB TEMS, then below steps are
are not required. SDA installs only browser support and if
customer is using TEP Desktop then install the support manually
as shown below.
------------------------------
Use the following steps to update the Tivoli Enterprise Monitoring
Server, Tivoli Enterprise Portal Server, or Tivoli Enterprise Portal
Desktop.
Note: If SDA feature is enabled at the HUB TEMS, then below steps are
are not required. SDA installs only browser support and if
customer is using TEP Desktop then install the support manually
as shown below.
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.
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.
3. To install application support on a monitoring server on Windows
or UNIX or Linux, see the "Installing and enabling application support"
topic in the "Installing IBM Tivoli Monitoring" chapter of the IBM Tivoli
Monitoring: Installation and Setup Guide for the procedure for setting up
application support on Tivoli Enterprise Monitoring.
or UNIX or Linux, see the "Installing and enabling application support"
topic in the "Installing IBM Tivoli Monitoring" chapter of the IBM Tivoli
Monitoring: Installation and Setup Guide for the procedure for setting up
application support on Tivoli Enterprise Monitoring.
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.
(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, it must be
restarted.
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.
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:
a. The following three sets of transport files are in the
ABAP directory of the SAP agent fix archive:
1) K710_00148.ITM and R710_00148.ITM
These files are non-Unicode versions of the transport.
These files are non-Unicode versions of the transport.
2) K710_00148U.ITM and R710_00148U.ITM
These files are Unicode versions of the transport.
These files are Unicode versions of the transport.
3) K710_00148_DELETE.ITM and R710_00148_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.
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.
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_00148.ITM file to the cofiles directory.
2) Copy the R710_00148.ITM file to the data directory.
or
Unicode transport
1) Copy the K710_00148U.ITM file to the cofiles directory.
2) Copy the R710_00148U.ITM file to the data directory.
directory as follows:
non-Unicode transport
1) Copy the K710_00148.ITM file to the cofiles directory.
2) Copy the R710_00148.ITM file to the data directory.
or
Unicode transport
1) Copy the K710_00148U.ITM file to the cofiles directory.
2) Copy the R710_00148U.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
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_00148 SID
pf=\usr\sap\trans\bin\PROFILE_NAME
tp import ITMK710_00148 SID client=nnn U16
pf=\usr\sap\trans\bin\PROFILE_NAME
Unicode
tp addtobuffer ITMK710_00148U SID
pf=\usr\sap\trans\bin\PROFILE_NAME
tp import ITMK710_00148U 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.
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 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>
-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'.
Monitoring installation directory. The default location
is 'C:\IBM\ITM'.
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>
-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).
- 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.03.00.
07.10.03.00.
After the agent is restarted, you can also use the GUI to verify
that the agent was successfully updated.
that the agent was successfully updated.
For the agent on Windows systems, the version number is
07.10.03.00.
07.10.03.00.
For the agent on UNIX systems, the version number is
07.10.03.00.
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 is successfully applied.
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 is successfully applied.
Note:
- The date of the build displayed might not be accurate. This is
a known problem.
- 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:
-------------------------
To validate that all components have been installed, run the
following command:
For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i
Result of below command may vary depending on ITM and
other components. We have displayed only ksa component.
other components. We have displayed only ksa component.
>kincinfo -i
************ Tuesday, March 1, 2022 2:01:29 PM *************
User : Administrator Group : NA
Host Name : <Hostname> Installer : Ver: 063007160
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory
************ Tuesday, March 1, 2022 2:01:29 PM *************
User : Administrator Group : NA
Host Name : <Hostname> Installer : Ver: 063007160
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory
SA KSA(64-bit) CMA/IBM Tivoli Composite Application Manager
Agent for SAP Applications WIX64 Version: 07.10.03.00
Build: 20751
SA TEMS App Support/IBM Tivoli Composite Application Manager
Agent for SAP Applications WINNT Version: 07.10.03.00
Build: 20751
SA TEPS App Support/IBM Tivoli Composite Application Manager
Agent for SAP Applications WINNT Version: 07.10.03.00
Build: 20751
SA TEPB App Support/IBM Tivoli Composite Application Manager
Agent for SAP Applications WINNT Version: 07.10.03.00
Build: 20751
SA TEPD App Support/IBM Tivoli Composite Application Manager
Agent for SAP Applications WINNT Version: 07.10.03.00
Build: 20751
7.0 Known problems and workarounds
===================================
None 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.
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.
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.
a compatible level of the transport.
Fix Level Delivered Transport Minimum Transport Level
----------- ------------------- -----------------------
FP0003 ITMK710_00148 ITMK710_00148
FP0002-IF0003 ITMK710_00127 ITMK710_00127
FP0002-IF0002 ITMK710_00109 ITMK710_00109
FP0002-IF0001 ITMK710_00108 ITMK710_00108
FP0002 ITMK710_00108 ITMK710_00108
FP0001-IF0001 ITMK710_00106 ITMK710_00105
FP0001 ITMK710_00105 ITMK710_00105
IF0001 ITMK710_00104 ITMK710_00103
710 GA ITMK710_00103 ITMK710_00103
----------- ------------------- -----------------------
FP0003 ITMK710_00148 ITMK710_00148
FP0002-IF0003 ITMK710_00127 ITMK710_00127
FP0002-IF0002 ITMK710_00109 ITMK710_00109
FP0002-IF0001 ITMK710_00108 ITMK710_00108
FP0002 ITMK710_00108 ITMK710_00108
FP0001-IF0001 ITMK710_00106 ITMK710_00105
FP0001 ITMK710_00105 ITMK710_00105
IF0001 ITMK710_00104 ITMK710_00103
710 GA ITMK710_00103 ITMK710_00103
8.2 Additional Information:
---------------------------
---------------------------
1. Linux 32 bit(li6243) support has been removed from
7.1.0-TIV-ITM_SAP-FP0003 SAP agent.
2. Windows 32 bit(winnt) support has been removed from
7.1.0-TIV-ITM_SAP-FP0003 SAP agent.
3. Java version is updated to JAVA 8.
4. Upgraded agent code compilation to Visual Studio 2013
for Windows platform.
5. TEMA version is upgraded to ITM 630 FP7 SP10 from 623 FP3 for
7.1.0-TIV-ITM_SAP-FP0003 SAP Agent.
9.0 Copyright and trademark information:
==================================
A current list of IBM trademarks is available on the Web at "Copyrightand 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 are 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.
errors. Changes are periodically made to the information herein; these
changes are 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.
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.
registered trademarks of Oracle and/or its affiliates.
UNIX is a registered trademark of The Open Group in the United States
and other countries.
and other countries.
Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.
other countries, or both.
Other company, product, or service names may be trademarks or service
marks of others.
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.
-----------------------------------------------------------------
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:
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.
- 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.
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JRN","label":"Tivoli Composite Application Manager for Applications"},"ARM Category":[{"code":"a8m500000008b8nAAA","label":"ITCAM-for-Applications-\u003ESAP Agent"}],"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.1.0"}]
Was this topic helpful?
Document Information
Modified date:
30 March 2022
UID
ibm16565067