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

Downloadable files


Abstract

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

Download Description

Copyright International Business Machines Corporation 2013.

All rights reserved.


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

Component ID: 5724B97SO

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

Date: October 31, 2013

Contents:

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

1.0 General description
========================

This fix pack resolves the APARs and defects listed in the
"Problems Fixed" section below. This fix pack also includes the
superseded fixes listed in section 2.4.

2.0 Problems fixed in 7.1.0.1-TIV-ITM_SAP-IF0001
=====================================================
The following problems are addressed by this fix.

2.1 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 are 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 comparision of previous and new collection of alert. Wth the
new ccms alert data collection, using DONE status to perform
auto-closure 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:
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 comparision 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
will fetch closed alerts from remote system from table
ALALERTDB. However while collecting these old alerts SAP agent
will also take care of performance issue or delay caused during
data collection.
To avoid any further delay in closed alerts data collection SAP
agent will collect 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.
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 will be 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
will write 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 will collect the status details
of IDOCS according to the IDOC number.


2.2 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 is not working for CCMS alerts in first
call some times
Additional Information: Issue fixed with Siutaitons 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 are murged into
one graph view name "Average Responce Time Greater Than 1000
Miliseconds". 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 correclty on TEP workspace
Additional Information: IDOC Number displayed on TEP workspace not
matching with SAP IDOC number. Issue fixed in ABAP.

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.

2.3 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 will retrieve all MTE states and if its
unchecked then only red and yellow state will be retrieved.
Note: By default its 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: 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 ’ will be seen for this job.

Enhancement: 38903
Abstract: Allow "IDOC number" to set as display item in situations
Additional Information: Priviously "IDOC number was not available to
set as display item in situaions. 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.

2.4 Superseded fixes
---------------------
7.1.0.1
7.1.0-TIV-ITM_SAP-IF0001
-------------------------

2.5 APARS, Defects and Enhancements included from superseded fixes
------------------------------------------------------------------
7.1.0.1
--------
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 a agent specific
configuration file
Example: <candle home>\tmaitm6\ksaenv_<sid>
2. For Non-Windows: Set SYSLOG_FREQUENCY=180 in a 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 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.


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 were Unexpected
spaces observed under formula column for few situation 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 Uitility 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 prerequisites 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 get 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 amount 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 mySAP agent 7.1 FP1 User Guide
for more details on new CCMS design.

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 he got the 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
--------------------------
APAR: IV18311
Abstract: SAP ON AIX HAS A DIFFERENT STYLE DATE FORMAT
Additional Information: SAP Gateway Connections Request Time
displays an incorrect value on the Tivoli Enterprise Portal
when the SAP system is on an AIX operating system.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Defect: 185556
Abstract: 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

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

Defect: 166690
Abstract: SAP Agent Sys log 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 trancate in ipv6 env
Additional Information: In the KSA Active Users workspace, the
"Terminal" column that contains the IPv6 address is truncated,
because the length of 20 in docksa must be updated to 64.

Defect: 89710
Abstract: Dev621: Wrong topology
in <local_SID>-<remote_SID>_CCMS_alerts
Additional Information: The currect 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"

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 User's
Guide, Version 7.1 Fix Pack 1 User Guide:
Link:
publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcama.doc_7.2/sapagent71fp1_user.pdf

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

You can also find system requirements for ITCAM for Applications 7.1 at
publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp?topic=%2Fcom.ibm.itcama.doc_7.1%2Fprerequisites%2Fapps71_systemreqs.html

ITCAM for Applications 7.1 Information Center:
publib.boulder.ibm.com/infocenter/tivihelp/v24r1/index.jsp?topic
=%2Fcom.ibm.itcama.doc_7.1%2Fwelcome_itcamfapps71.html

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

710 FP001 ISO Part Number:
Physical Part Number: ITCAM Agent for SAP Applications CBBD4ML
Electronic Part Number: ITCAM Agent for SAP Applications CIN1BML
Customer need to download separately 710 FP001 ISO image from
Passport Advantage.


- IBM Tivoli Monitoring, Version 6.2.2 FP2

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



4.0 Image directory contents
=============================
This fix image contains the following files:
- 7.1.0.1-TIV-ITM_SAP-IF0001.README - This README file
- 7.1.0.1-TIV-ITM_SAP-IF0001.tar - Fix archive .tar format
- 7.1.0.1-TIV-ITM_SAP-IF0001.zip - Fix archive .zip format

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

5.0 Installation instructions
=============================

This fix can only be installed over an existing installation of
710 FP0001. Use the following steps to install this fix.

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

- For the purpose of this README, the <CANDLEHOME> symbol is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
on Windows systems.

- Before installing this fix pack on UNIX systems, set the CANDLEHOME
environment variable to the IBM Tivoli Monitoring installation
directory.

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

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

5.2 Local agent update
--------------------------
1. Transfer the appropriate archive file
(7.1.0.1-TIV-ITM_SAP-IF0001.tar or .zip) to a temporary
directory on the system that contains the agent to be updated.
For the purpose of this README, the <TEMP> symbol represents the
fully qualified path to this directory. Note: On Windows systems
, this path includes the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all supported
operating systems.

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

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

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

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

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

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

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

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

Note: if the itmpatch command gets this error:
"The application has failed to start because its side-by-side
configuration is incorrect. Please see the application event
log for more detail." it's necessary install the "visualstudio
redistribution package" before to run run the itmpatch command.

For a 32bit architecture,
the name of this package is vcredist_x86.exe, available at
www.microsoft.com/en-us/download/details.aspx?id=5582

For a 64bit architecture,
the name of this package is vcredist_x64.exe,available at
www.microsoft.com/en-us/download/details.aspx?id=2092


5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file
(7.1.0.1-TIV-ITM_SAP-IF0001.tar or .zip) to a temporary
directory on the IBM Tivoli Enterprise Monitoring Server system.
For the purpose of this README, the <TEMP> symbol represents the
fully qualified path to this directory. Note: On Windows systems,
this path includes the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
operating systems.

3. To add the agent fix bundles into the remote deploy depot, use
the "tacmd addBundles" command found in $CANDLEHOME/bin on UNIX
systems or in %CANDLE_HOME%\bin on Windows systems. For more
information on the "tacmd addBundles" command, see the IBM Tivoli
Monitoring Command Reference.

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

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

where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the fix
directory does not contain any prerequisites that the fix
might require. See Section 3.1 for the prerequisites
for this fix.
-i is the directory that contains the deployment bundles to be
added to the depot.

4. After "tacmd addBundles.." from step 3 above, control files
on the Tivoli Enterprise Monitoring Server and the
Tivoli Enterprise Portal Server must be updated.
These updates must be done manually.

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

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

ksa_patchdepot.bat - Windows
ksa_patchdepot.sh - UNIX

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

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

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

ksa_patch_resource_teps.bat - Windows
ksa_patch_resource_teps.sh - UNIX

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

5. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the
"tacmd login" and "tacmd updateAgent" commands, see the IBM
Tivoli Monitoring Command Reference.

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

> $CANDLEHOME/bin/tacmd listSystems

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

> $CANDLEHOME/bin/tacmd updateAgent -t sa
-n <Managed system name>
-v 07100101

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

> %CANDLE_HOME%\bin\tacmd listSystems

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

> %CANDLE_HOME%\bin\tacmd updateAgent -t sa
-n <Managed system name>
-v 07100101

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (sa), not three characters (ksa).
- The node (-n) for the "tacmd updateAgent" command is the
managed system name of the operating system (OS) agent to be
updated. The target node for the "tacmd updateAgent" command
is always an OS agent.

5.4 Agent support update
------------------------------
Use the following steps to update the Tivoli Enterprise Monitoring
Server, Tivoli Enterprise Portal Server, or Tivoli Enterprise Portal
Desktop.
Note: If SDA feature is enable at the HUB TEMS, then below steps are
are not required. SDA will install only browser support and if
customer is using TEP Desktop then install the support manfully
as shown below.

This fix (7.1.0.1-TIV-ITM_SAP-IF0001) includes changes to the
agent support files that must be installed. If you installed these
updates, there are no additional installation steps. If you did not
install these updates, use the following steps to update the Tivoli
Enterprise Monitoring Server, Tivoli Enterprise Portal Server, or
Tivoli Enterprise Portal Desktop.

1. Transfer the appropriate archive file
7.1.0.1-TIV-ITM_SAP-IF0001.tar or .zip) to the Tivoli
Enterprise Monitoring Servers, Tivoli Enterprise Portal Servers,
or Tivoli Enterprise Portal Desktops.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. Expand the archive file (ksa_tems_teps_tepd_if0001.tar or .zip)
that contains the updates for the Tivoli Enterprise Monitoring
Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise
Portal Desktop using the "tar" command on UNIX systems or an
extract utility on Windows systems. This step creates a directory
structure that includes a subdirectory called CD-ROM, with the
necessary updates.

4. Use the Application Support Installer(ASI) GUI or the silent
installation method to install the application support files.

GUI installation option
------------------------
The GUI can be started by using one of the following commands
from within the CD-ROM directory where setup.jar is located.

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

On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]

When prompted by the Application Support Installer for the
installable media directory, select the CD-ROM directory, not the
component directory. The installer can install updates for
multiple components at the same time.

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

1. Aquire a platform-specific pre-packaged JRE version
of the Application Support Installer (ASI). See IBM
Tivoli Monitoring Application Support Installer,
6.2-tiv-itm_asi-if0002 at
www-01.ibm.com/support/docview.wss?uid=swg24034924
for download and installation instructions.

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

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

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

Continue through the remaining GUI panels selecting SAP Agent
07.10.01.01 support to complete the installation.

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

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

5.5 Installing SAP agent transport
------------------------------------
This procedure installs the SAP transport into the SAP system. You
are not required to uninstall the previous transport before
installing this transport.

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

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

1) K710_00106.ITM and R710_00106.ITM
These files are non-Unicode versions of the transport.

2) K710_00106U.ITM and R710_00106U.ITM
These files are Unicode versions of the transport.

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

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

c. Copy your transport files to the SAP Transport System data
directory as follows:
non-Unicode transport
1) Copy the K710_00106.ITM file to the cofiles directory.
2) Copy the R710_00106.ITM file to the data directory.
or
Unicode transport
1) Copy the K710_00106U.ITM file to the cofiles directory.
2) Copy the R710_00106U.ITM file to the data directory.

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

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

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

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

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

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

Usage: itmpatch -h <installation home> [OPTIONS]

itmpatch -h <installation home>
-t { <patch_file_directory> | <patch_file> }

itmpatch -h <installation home>
-i { <patch_file_directory> | <patch_file> }

where:

-h Specifies the IBM Tivoli Monitoring installation directory
-i Specifies the path to the directory or patch file to be installed
-t Generates a report of the actions to be taken by the patch

For example, on UNIX systems:
- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>

- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>

where:
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring
installation directory. On Windows systems, this path must include
the drive letter.
<TEMP> represents the fully qualified directory specification,
where the fix is located. On Windows systems, this path must
include the drive letter.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Note: kincinfo output may differ depending on ITM version.

>kincinfo -i
************ Monday, October 14, 2013 5:40:17 PM ************
User : Administrator Group : NA
Host Name : PS8273 Installer : Ver: 062303000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory

PC PRODUCT DESC PLAT VER BUILD INSTALL DATE

SA KSA(32-bit) CMA/IBM Tivoli Composite Application Manage WINNT
07.10.01.01 20131014 1022

PC SELF-DESCRIBED APPLICATION SUPPORT PACKAGE PLAT APP VER
SA KSA(32-bit) CMA/IBM Tivoli Composite Applica -
KSAJSTMS CMS 07.10.01.01

SA KSA(32-bit) CMA/IBM Tivoli Composite Applica -
KSAJSTPS CNS 07.10.01.01

SA KSA(32-bit) CMA/IBM Tivoli Composite Applica -
KSAJSTPW XEB 07.10.01.01

PC APPLICATION SUPPORT DESC PLAT APP VER BUILD INSTALL DATE

SA TEMS App Support/IBM Tivoli Composite Application Manag WICMS
07.10.01.01 201310140303 20131014 1022

SA TEPS App Support/IBM Tivoli Composite Application Manag WICNS
07.10.01.01 201310140303 20131014 1022

SA TEPB App Support/IBM Tivoli Composite Application Manag WIXEB
07.10.01.00 30841 20131014 1022

SA TEPD App Support/IBM Tivoli Composite Application Manag WIXEW
07.10.01.01 201310140303 20131014 1022


7.0 Known problems and workarounds
===================================
Abstract: Upgrade fails for for Solaris 11 X86_64 bit, RHEL 6 64 and
SUSE 11 32 bitwith ITM version 622FP9
Problem: Error log
(Tuesday, October 29, 2013, 3:04:01 PM-{DE0}kdyctrl.cpp,1977,
"checkPrereqs") prereq product=[sa] found at endpoint=
[IBMSAP1-V12:LZ] at version=[06220900], prereq version=
[071001000] will be deployed for transaction=
1383039239369000000000041]

As per the above TEMS logs the sa product version is 06220900
found and and the prereq is 071001000 should be present but at
the endpoint the 710FP001 is properly installed and running.

Workaround: Follow Local upgrade. PMR is opened wit ITM team
PMR number is 19209,999,000

Abstract: IDML book certification fails in case of multiple Ins
Problem: If you generate the IDML book in a mulitiple instance
environment, the certification tool fails while certifing the
IDML book.

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


Abstract: An error occurred during password decryption. Return code:44
Problem: When you upgrade the SAP agent to version 7.1 Fix Pack 1, on
Windows 64-bit system, you might receive the following error:
An error occurred during password decryption. Return code:44

Workaround:
In the InstallShield wizard, complete the following steps:
1. After you receive the error message, click OK.
2. On the AFUtil64.exe has stopped working page, click Close
the program.
3. After you receive the following message: An instance of the
service is already running, click OK.
4. Click Finish.
5. After you install the SAP agent successfully, re-configure
SAP agent instances manually.
6. Start the SAP agent instance manually.

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

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

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

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

Fix Level Delivered Transport Minimum Transport Level
----------- ------------------- -----------------------
FP0001-IF0001 ITMK710_00106 ITMK710_00105
FP0001 ITMK710_00105 ITMK710_00105
IF0001 ITMK710_00104 ITMK710_00103
710 GA ITMK710_00103 ITMK710_00103

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


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

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

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

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

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

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

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

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

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

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


Revised - 11/22/2013- Added one known issue.
Revised - 6/11/2014 - Removed broken links.

Prerequisites

IBM(R) Tivoli(R) Composite Application Manager Agent for SAP Applications, Version 7.1.0.1

Installation Instructions

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

Download package


Problems solved

IV51184; IV46719; IV46184; IV43860; IV40032; IV41680; IV38554;

Known side effects

Upgrade issue with ITM 622 FP9 on Non Windows Platforms, PMR opened 19209,999,000

Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central (FC)?
7.1.0.1-TIV-ITM_SAP-IF0001.README 31 Oct 2013 English 64720 FC FTP
7.1.0.1-TIV-ITM_SAP-IF0001.zip 31 Oct 2013 English 60765174 FC FTP
7.1.0.1-TIV-ITM_SAP-IF0001.tar 31 Oct 2013 English 100976640 FC FTP
7.1.0.1-TIV-ITM_SAP-IF0001.README.DEU 31 Oct 2013 German 76718 FC FTP
7.1.0.1-TIV-ITM_SAP-IF0001.README.ES 31 Oct 2013 Spanish 71949 FC FTP
7.1.0.1-TIV-ITM_SAP-IF0001.README.FR 31 Oct 2013 French 74335 FC FTP
7.1.0.1-TIV-ITM_SAP-IF0001.README.JPN 31 Oct 2013 Japanese 73397 FC FTP
7.1.0.1-TIV-ITM_SAP-IF0001.README.PTB 31 Oct 2013 Brazilian Portuguese 69988 FC FTP
7.1.0.1-TIV-ITM_SAP-IF0001.README.CHS 31 Oct 2013 Simplified Chinese 58967 FC FTP
7.1.0.1-TIV-ITM_SAP-IF0001.README.CHT 31 Oct 2013 Traditional Chinese 58920 FC FTP

Product Alias/Synonym

SAP agent 7.1.0 FP0001

Problems (APARS) fixed
IV51184, IV46719, IV46184, IV43860, IV40032, IV41680, IV38554

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

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

Software version:

7.1.0

Operating system(s):

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

Software edition:

All Editions

Reference #:

4036378

Modified date:

2013-11-22

Translate my page

Machine Translation

Content navigation