---------------------------------------------------------------------------
7.1.1-TIV-ITM_SAP-FP0008
---------------------------------------------------------------------------

Date: May 30, 2023

Contents:
-------------
 1.0 General description
 2.0 Problems fixed
 3.0 Architecture and prerequisites
 4.0 Download Instructions
 5.0 Installation instructions
 6.0 Additional installation information
 7.0 Known problems and workarounds
 8.0 Additional product information
 9.0 Copyright and trademark information
 10.0 Notices

1.0 General description

This Fix Pack resolves the APARs and defects listed in the 'Problems fixed' section below. This Fix Pack also includes the superseded fixes listed in section 2.4.

2.0 Problems fixed in 7.1.1-TIV-ITM_SAP-FP0008

The following problems are addressed by this Fix Pack.

APAR: IJ45253
Abstract: The Attribute Group KSAORASUM (Database Summary) and the Attribute Group KSAORADTL (Database Details) is showing the data referring to Transaction Code DB02OLD  instead of Transaction Code DB02 on TEPS.
Additional Information: The SAP Standard Function Module is deprecated which is exclusively 
used for Transaction code DB02OLD. The new Standard Function Module has been implemented to fetch the data from the Transaction Code DB02 and same will be displayed for Attribute Group KSAORASUM (Database Summary) and the attribute group KSAORADTL (Database Details) on TEPS.
Note: 

APAR: IJ46117
Abstract: Wrong origin for object ZITM_AUTH in ABAP package /IBMMON/ITM.
Additional Information: The SAP "Software Update Manager" (SUM) tool, which is used to perform the release changes and updates, finds the Object ZITM_AUTH from ABAP package /IBMMON/ITM and tries to delete it as it is marked with origin "SAP", which is incorrect.

2.2 Defects
---------------------
No Defects

None

2.4 Superseded fixes:
----------------------------------
7.1.1-TIV-ITM_SAP-FP0007
7.1.1.6-TIV-ITM_SAP-IF0004
7.1.1.6-TIV-ITM_SAP-IF0003
7.1.1.6-TIV-ITM_SAP-IF0002
7.1.1.6-TIV-ITM_SAP-IF0001
7.1.1-TIV-ITM_SAP-FP0006
7.1.1.5-TIV-ITM_SAP-IF0001
7.1.1-TIV-ITM_SAP-FP0005
7.1.1-TIV-ITM_SAP-FP0004
7.1.1.3-TIV-ITM_SAP-IF0001
7.1.1-TIV-ITM_SAP-FP0003
7.1.1-TIV-ITM_SAP-FP0002
7.1.1.1-TIV-ITM_SAP-IF0002
7.1.1.1-TIV-ITM_SAP-IF0001
7.1.1-TIV-ITM_SAP-FP0001
7.1.1-TIV-ITM_SAP-IF0001

--------------------------------
7.1.1-TIV-ITM_SAP-FP0007
--------------------------------

No APARs

Defects
-----------
No Defects

Enhancements
-------------------
Enhancement:
Abstract: S/4 HANA 2021 support is available.
Additional Information: Support for monitoring of S/4 HANA 2021 (SAP Basis version 756) is provided.

---------------------------------------------------------
7.1.1.6-TIV-ITM_SAP-IF0004
---------------------------------------------------------
APARs

---------------------
No APARs

Defects
---------------------
No Defects

Enhancement
Abstract: S/4 HANA 1709 support is available.
Additional Information: Support for monitoring of S/4 HANA 1709 (SAP Basis version 752) is provided.

Enhancement: RFE 130567
Abstract: S/4 HANA 1809 support is available.
Additional Information: Support for monitoring of S/4 HANA 1809 (SAP Basis version 753) is provided.

Enhancement: RFE 140873
Abstract: S/4 HANA 1909 support is available.
Additional Information: Support for monitoring of S/4 HANA 1909 (SAP Basis version 754) is provided.

Enhancement
Abstract: S/4 HANA 2020 support is available.
Additional Information: Support for monitoring of S/4 HANA 2020 (SAP Basis version 755) is provided. As a prerequisite, SAP Note 2767860 "Generation of RFC destinations with invalid name" should be implemented on the SAP system.

---------------------------------------------------------
7.1.1.6-TIV-ITM_SAP-IF0003
---------------------------------------------------------

APAR: IJ25293
Abstract: Application support mismatch after applying IF02.
Additional Information: After applying mySAP agent version 7.1.1.6-TIV-ITM_SAP-IF0002, the TEP browser application support version file is not updated. As a result it displays constant warnings on TEP
browser and TEPD client with warning message "Application Support Mismatch". Client version displayed is 07110601 and Servers Version is 07110602.

Defects
---------------------
No Defects

Enhancements
---------------------
No Enhancements

---------------------------------------------------------
7.1.1.6-TIV-ITM_SAP-IF0002
---------------------------------------------------------

APAR: IJ23094
Abstract: IBM Agent for SAP 07.11.06.00 causing ABAP dumps.
Additional Information: ABAP dump was 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.

Defects
---------------------
No Defects

Enhancement: 141272
Abstract: Improve logging messages for SAP agent.
Additional Information: To print execution time of RFC function module in detailed tracing (Not with default trace level). Through agent logs, this helps to find out exact time taken by Function Module to execute.

---------------------------------------------------------
7.1.1.6-TIV-ITM_SAP-IF0001
---------------------------------------------------------

No APARs

Defect: 139045
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 creates a copy of backup file for any system.

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 Authorization Object 'S_DEVELOP' has the authority to perform Generic table operations such as:

  3. "Missing authority check in Report"
     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 execute the Reports.
  
  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. "Direct database modification"
     For improved security, additional internal security layer is implemented for database access.

  6. "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". This authorization group is added to the profile /IBMMON/AUTH and assigned to user IBMMON_AGENT.
     The user with the Authorization Object 'S_TABU_DIS' with authorization group ZITM has the authority to access database tables.

Enhancement: 138930
Abstract: Modified "KSAHOSTS" attribute group to support ICAM UI.
Additional Information: Added new attribute "RESTYPE" (attribute group : KSAHOSTS) to produce the values in the following format to support MSN values for ICAM UI:
 -sysid:hostname:Sys
 -sysid:hostname:Ins
 -sysid:hostname:PI
 -sysid:hostname:Slm  

---------------------------------------------------------
7.1.1-TIV-ITM_SAP-FP0006
---------------------------------------------------------

APAR: IJ14075  
Abstract: Help related to creation of workspaces, views, reports, queries and situations.
Additional Information: Help related to creation of workspaces, views, reports, queries and situations for each attribute group is added.

APAR: IJ07570
Abstract: Alert Severity is displayed as '-1' in Historic Data collection for CCMS alerts.
Additional Information: Original Severity of CCMS alerts is stored in Historic Data Collection. Previously '-1' was stored as alert severity in HDC for Closed Alerts.

Defects
---------------------
No Defects

Enhancement: 127520
Abstract: User IBMMON_AGENT should only have the access to execute the Function Modules related to SYS, SLM, LDS, SOL, PI nodes. Password for IBMMON_AGENT will be generated randomly. The functionality of directory traversal is enhanced by using logical file path.

Additional Information: 

1) A new Authorization Object ZITM_AUTH is created in the profile /IBMMON/AUTH and assigned to user IBMMON_AGENT. The user with Authorization Object ZITM_AUTH will only be having authority to access
   the attributes tagged under "SYS","SLM","LDS","SOL,"PI" node. For other users, "RFC Error Check Agent Log" message will be displayed on TEP.

2) Default password for IBMMON_AGENT is replaced with random generation of password. User can modify the password of their choice according to their password policy.

3) Direct read and write access of directories are replaced with logical file paths.
Note: If SAP system is installed on Unix/Linux or WINDOWS NT operating system, the ConfigBackup.csv file gets created either on application server inside the work directory at /usr/sap/<SYSID>/<INSTANCE>/work/<FILENAME> or inside the global directory at /usr/sap/<SYSID>/<INSTANCE>/global/<FILENAME>. According to SAP environment, filename might truncate.

Enhancement: 129087
Abstract: Display performance parameters of Oracle Database.
Additional Information: Performance parameters of Oracle Database such as Data Buffer Quality, Data Dictionary Cache Quality, Long Table Scans, and Sorts on Disk are displayed.

------------------------------------------
7.1.1.5-TIV-ITM_SAP-IF0001
------------------------------------------

APAR: IJ11005
Abstract: To see the Long Running Jobs present in SAP System for more than 24 hours.
Additional Information: This APAR is opened to read all active jobs that are running for long time. Batch jobs fetching is kept configurable at SAP side according to the critical constant value set. Critical constant value is a limit on total number of entries returned by Function Module. User can set this limit in "Maintain ITM Generated Alerts" under Transaction code /N/IBMMON/ITM_CONFIG under alert Message "Excessive data collected for report, nnnn rows deleted". If critical constant value is not set by user, a default value of 2500 entries will be fetched. Default sample period interval for fetching Batch Jobs is 1 hour. User can set time interval till maximum of 4 hours in "Maintain Default Sample Periods" under "R/3 Batch Jobs" in
Transaction code /N/IBMMON/ITM_CONFIG.

Below are the configurations for the same.
1. Create an entry in table - /IBMMON/ITM_CNFG with PARM_NAME = "BATCH_JOBS_PERF" and VALUE_CHAR = "YES" to maintain a configuration parameter. Total number of entries fetched will be equivalent to critical constant value which includes jobs with Active and Cancelled status within default sample period interval.
2. Create an entry in table - /IBMMON/ITM_CNFG with PARM_NAME = "BATCH_JOBS_PERF" and VALUE_CHAR = "YES_LONG_RUN" to maintain a configuration parameter. This will fetch all Cancelled jobs for the request within default sample period interval and all Active jobs in system without any sample
   period constraints up to critical constant value.
3. Create an entry in table - /IBMMON/ITM_CNFG with PARM_NAME = "BATCH_JOBS_PERF" and VALUE_CHAR = "YES_ALL" to maintain a configuration parameter. This will fetch jobs with all statuses for the request within the default sample period interval and all Active jobs in system without any sample period constraints up to the critical constant value.
4. If there is no configuration parameter added, it will fetch all jobs with all statuses for the request within default sample period interval.

APAR: IJ10736
Abstract: Performance improvements for Function Module - /IBMMON/ITM_MAIALRT_INX
Additional Information: This is with reference to PMR TS001184443 SAP Agent - no data for SAP Solman work spaces. This APAR is opened to improve the performance of the Function Module /IBMMON/ITM_MAIALRT_INX.
The performance of Function Module is improved by keeping the data fetching configurable on Critical Constant. The total number of rows fetched will be equal to the Critical Constant set in ITM Maintenance Transaction (Transaction Code: /N/IBMMON/ITM_CONFIG). The critical constant set is irrespective of the
critical constant operator (i.e. GT, GE, NE, EQ, LT, LE). This feature is enabled by maintaining a configuration parameter in the table - /IBMMON/ITM_CNFG with PARM_NAME = "MAI_ALERTS_PERF" and VALUE_CHAR = "YES".

Defect Description: SAP Agent hangs at startup when message server is inactive

Additional Information: When SAP Agent is configured in logon group mode and started when SAP Message Server is down or unavailable, the agent connects to SAP when Message Server becomes available.

Defect Description: PI node is not getting discovered after connecting SAP agent to 711FP5 build.
Additional Information: Authorization object S_XMB_AUTH and S_ADMI_FCD with full authorizations is added in profile /IBMMON/AUTH and assigned to user IBMMON_AGENT. With these authorizations, PI node is discovered after connecting SAP agent to 711FP5 IF01 build.

Defect Description: Incorrect Alert Severity and Priority is displayed for MAI Alerts after making configuration entry in CNFG table.
Additional Information:  After sorting the alerts according to Alert group Id, Alerts are fetched with correct Alert severity and Priority even after adding a configuration parameter with parm_name = “MAI_ALERTS_PERF” and VALUE_CHAR = “YES” in table /IBMMON/ITM_CNFG.

Enhancement: 56536
Abstract: User IBMMON_AGENT should only have the access to execute the Function Modules related to INS node
Additional Information: A new Authorization Object ZITM_AUTH is created in the profile /IBMMON/AUTH and assigned to user IBMMON_AGENT. The user with Authorization Object ZITM_AUTH will only be having authority to access the attributes tagged under "INS" node. For other users, "RFC Error Check Agent Log" message will be displayed on TEP.

Enhancement: 53926
Abstract: KSAALERTS Attribute Group should show CCMS Alerts with Alert status as "ACTION_REQUIRED" (Alert Status 30)
Additional Information: CCMS Alerts with Alert status "ACTION REQUIRED" (Alert Status 30) will be fetched. This feature will be enabled when a Configuration Parameter is maintained in the Table - /IBMMON/ITM_CNFG with PARM_NAME = "CCMS_ALERT30E_EN" and VALUE_CHAR = "YES".
In addition to this deletion of old alerts can be stopped by adding a configuration parameter in the Table - /IBMMON/ITM_CNFG with PARM_NAME = "CCMS_ALERT30E" and VALUE_CHAR = "YES". This configuration parameter can be maintained only if the above configuration parameter (CCMS_ALERT30E_EN) is maintained.
On the Agent System, following parameters have to be added in sa_<Agent_instance>.config file present in $CANDLEHOME/config directory on Linux/AIX platform or KSAENV_<Agent_instance> file present in %CANDLE_HOME%\TMAITM6 or %CANDLE_HOME%\TMAITM6_x64 folder on Windows platform.
Restart the agent after the parameters are added in this file.

Recommended values for parameters to be added-
* =======================================================
* Time Interval and Threshold Settings For CCMS Alerts
* =======================================================
MAX_CCMS_ALERT_THRESHOLD=3500
CCMS_ALERT_SHORT_INTERVAL=0
CCMS_ALERT_LONG_INTERVAL=0
DELETE_IDX_AT_AGENT_RESTART=N
DELETE_IDX_AT_SAP_SYSTEM_RESTART=N

Optional Settings:
CCMS_ALERT_SHORT_INTERVAL_OVERLAP=Y
SAVE_OPEN_AND_CLOSED_CACHE=N

where,
MAX_CCMS_ALERT_THRESHOLD - This parameter indicates that agent will cache 3500 alerts. If this value is not set by the user then by default value 3500 is set.

CCMS_ALERT_SHORT_INTERVAL - This parameter indicates the short interval duration in minutes. 
If the configuration parameter is not set, by default 0 value is set and no short calls will be triggered by the SAP Agent. Only the integer value between 15 to 60 minutes is acceptable for this configuration parameter.

CCMS_ALERT_LONG_INTERVAL - This parameter indicates the long interval duration in hours. It is recommended to set the parameter value to 0. Only the integer value between 0 to 24 hours is acceptable for this configuration parameter.

DELETE_IDX_AT_AGENT_RESTART - This parameter enables the feature of IDX file deletion when SAP Agent is restarted. IDX file stores the timestamp. It is recommended to set the parameter value to ‘N’. When set to 'N', it will collect all alerts from the timestamp stored in idx file. If required, then you 
can set the value to ‘Y’ if you want to collect all  alerts after the SAP agent restart. 

DELETE_IDX_AT_SAP_SYSTEM_RESTART - This parameter enables the feature of IDX file deletion when SAP System is restarted. It is recommended to set the parameter value to ‘N’. When set to 'N', it will collect all alerts from the timestamp stored in idx file. If required, then you can set the value to ‘Y’ 
if you want to collect all alerts after the SAP system restart. 

CCMS_ALERT_SHORT_INTERVAL_OVERLAP - This parameter indicates that SAP agent will overlap the Short interval calls with the respect to time interval. This parameter will be used only if CCMS_ALERT_SHORT_INTERVAL is set with some value between 15 to 60 minutes.

SAVE_OPEN_AND_CLOSED_CACHE - This parameter indicates whether user wants to preserve CCMS Alerts Cache after the Agent is stopped and reload CCMS Alerts after agent is started. This works only when the value for DELETE_IDX_AT_AGENT_RESTART parameter is set to ‘N’.

Note - After the agent instance is reconfigured, please verify if the above entered parameters are present in sa_<Agent_instance>.config file on Linux/AIX platform or KSAENV_<Agent_instance> file on Windows platform. If they are not present, please add them and restart the agent to activate this feature.

------------------------------------------
7.1.1-TIV-ITM_SAP-FP0005
------------------------------------------

APAR: IV99653
Abstract: System Down events not generated.
Additional Information: This APAR is opened in order to trigger the System Down Alert on SAP Basis 740 and above, in absence of CI(Central Instance) along with the configurations of Dialog Instance and ASCS (ABAP SAP central Services) on different hosts in HA (High Availability) like mode.

Defect Description: SAP Agent should  provide an Alert when Message Server goes down.
Additional Information: When Message server goes down, the situation 'R3_Alert_System_down' is triggered and SAP Agent provides an Alert 'Lost connection to Message Server'.

Defect Description: SAP Agent should provide an alert when Message server goes down in case of Dialog instance and ASCS(ABAP SAP central Services) are on different hosts in HA(High Availability) like mode.

Additional Information: The Dialog instance and ASCS(ABAP SAP central Services) are on different hosts in HA(High Availability) like mode. When Message server goes down in HA(High Availability) like mode, the situation 'SAP_System_Down' is triggered and SAP Agent provides an Alert 'Unable to connect to SAP System'.

Defect Description: Launch definitions are not visible when previous release Agents are pointed to ITM with 711FP5 support.
Additional Information: The launch definitions of Work Process and XML Message Logs are not visible on TEP when 711FP4 Agent is pointed to ITM having support of 711FP5 release.

Defect Description: Issue for QoP input validation in SAP.
Additional Information: Issue for QoP input validation. QoP input is accepting alphabets, special characters , and multi digits numeric values.

Defect Description: SAP Agent should delete the existing Alert idx file when restarted.
Additional Information: The existing IDX file is used by Agent for fetching CCMS Alerts data according to the existing design. Instead, Agent should delete the existing IDX file and create a new IDX file and then it should fetch the data.

Defect Description: SAP Agent Logon Group Name, SNC Client Name, SNC Server Name and SAP cryptolibrary path should accept spaces.
Additional Information: The configuration parameters Logon Group Name, SNC Client Name, SNC Server Name and SAP cryptolibrary path accepts spaces and can successfully create connection with SAP.

Enhancement: 51748
Abstract: Removal of IDX file automatically every time SAP System is restarted, instead of user deleting it manually.
Additional Information: Deletion of IDX file is automated when SAP System is restarted. After deletion of the file a new IDX file should be created to collect the CCMS alerts.

Enhancement: 83165
Abstract: SAP Agent - Current number of different lock arguments in the lock table.
Additional Information: This is with reference to PMR 86807,022,649. An additional view is added to the 'Lock Entries' attribute group which contains the total count of Lock Arguments in the lock table.

Enhancement: 83166
Abstract: SAP - Current number of elementary locks in the lock table.
Additional Information: This is with reference to PMR 86807,022,649. An additional view is added to the 'Lock Entries' attribute group which contains the total count of Elementary locks in the lock table.

Enhancement: 83167
Abstract: SAP - Current number of lock owners in the lock table.
Additional Information: This is with reference to PMR 86807,022,649. An additional view is added to the 'Lock Entries' attribute group which contains the total count of Lock Owners in the lock table.

Enhancement: 87236
Abstract: Missing Work Process status in ITCAM SAP Agent.
Additional Information: This is with reference to PMR 92148,003,756 - Sap agent not showing ended work process information. An additional attribute 'Work Process Status' is added to the 'Work Processes' attribute group which contains the status of the work process.

Enhancement: 55367
Abstract: Add functionality fields "error code"/"status error" in PI Querys

Additional Information: This is with reference to PMR 71431,100,838 - Attribute required on XML message log workspace. The following attributes have been added to the 'PI/XI XML Message Logs' attribute group to support the XML 
Message Server error codes:
-Message Status Description
-Error Category
-Error ID

------------------------------------------
7.1.1-TIV-ITM_SAP-FP0004
------------------------------------------

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

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

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

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

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

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

    A) SNC specifications can be used with mySAP agent. The new parameters are as follows:
       sap_conn.sap_snc_mode=true
       sap_snc_mode1.sap_snc_qop=<QOP value default is 8 >
       sap_snc_mode1.sap_snc_client=<Client SNC Name>
       sap_snc_mode1.sap_snc_server=<Server SNC Name>
       sap_snc_mode1.sap_snc_library=<Crypto library path >

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

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

------------------------------------------
7.1.1.3-TIV-ITM_SAP-IF0001
------------------------------------------

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

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

Defects: 120588
Abstract: HDC View Names are Incorrect for SAP qRFC Inbound Queues and SAP qRFC Outbound Queues Attribute group.
Problem: Due to length constraints, view names and objects names are not at par.
Workaround: No workaround as of now.

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

APAR: IV85498
Abstract: A mySap Agent gets error after upgrading SAP ERP system to SAP Basis 740 SP12 in procedure /IBMMON/ITM_NEW_CCMS_ALERTS.
Additional Information: The /IBMMON/ITM_NEW_CCMS_ALERTS function module does not support SAP Basis 740 SP12. The updates are made to support SAP Basis 702 SP17, SAP Basis 730 SP13, SAP Basis 731 SP16, SAP Basis 740 SP11, and SAP Basis 750.

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

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

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

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

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

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

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

No enhancements
   
------------------------------------------
7.1.1-TIV-ITM_SAP-FP0002
------------------------------------------

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

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

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

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

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

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

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

Defect: 91470
Abstract: R3_Instance_Down2_Crit flyover not seen in Navigator view > Agent Ins: node.
Additional Information: The R3_Instance_Down2_Crit flyover help does not appear in the Navigator view > Agent Ins node. Because the situation is not associated to Ins: node.
 
Defect: 54092    
Abstract: Group Key attribute has no data for three workspaces under :Lds > System.
Additional Information: The Group Key attribute is not required to be displayed on TEP for these particular LDS > System workspaces. Therefore, this attribute is hidden.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

APAR: IV72669
Abstract: Sap-Agent is throwing errors on one of the workspaces. The logs are generating the following errors when loading the workspace: (5527A4D8.000A-C:ksarfcdataaccessor.cpp,224,"FetchItmData") Error : InvokeFunctionModule for Function Module /IBMMON/ITM_LDS_SYS_OVERVIEW failed. Exit -1 And the RFC log produces the following: Function module "LMDB_GET_STEXT_TO_PRODVERS" not found.

Additional Information: SAP removed Standard Function module 'LMDB_GET_STEXT_TO_PRODVERS' in Solution Manager 7.1 SP12. This standard function module 'LMDB_GET_STEXT_TO_PRODVERS' is used by
/IBMMON/ITM_LDS_SYS_OVERVIEW  to send data to System workspace of LDS subnode. Since this standard Function Module was removed  in Solution Manager 7.1 SP12 , Function Module /IBMMON/ITM_LDS_SYS_OVERVIEW failed.
Alternative class method ‘CL_DIAGLS_FACTORY’ is used in the Function Module /IBMMON/ITM_LDS_SYS_OVERVIEW to fetch the data.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

APAR: IV60254
Abstract: TRANSACTION PERFORMANCE and R/3 TRANSACTION PERFORMANCE modules are not sending data for HDC.
Additional Information: Code has been changed in Transaction performance logic that creates KSATRANS file to display historical data on TEP for Transaction performance.

APAR: IV60989
Abstract: Empty workspace for BUSINESS PROCESS MONITORING and SYSTEMMONITORING in TEP.
Additional Information: Code changes are done to handle exceptions for the SAP standard DSWP_BPM_SOLUTION_ID_CONVERT function module and for the /IBMMON/ITM_MAIBP_MONITORING
MAI BPM function module.

APAR: IV61450
Abstract: Remove Period start and Period end attributes of XML message logs.
Additional Information: The attributes Period Start and Period End are used by the agent internally and should not be visible to users. In order to hide these attributes from attribute view, the USAGE and COST 
tags have been set to appropriate values. Also, the queries that define the attribute view are modified to remove the Period Start and Period End attributes.

APAR: IV59319
Abstract: SAP agent not picking up alerts from solution manager.
Additional Information: This is DOC APAR and the third-party OS command adapter should be configured and mail notification should be enabled using appropriate steps.

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

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

Note: This issue is reproducible only with multi instance SAP system.

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

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

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

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

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

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

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

APAR: IV63525
Abstract: The output of the function module IBMMON/ITM_QOUT_GET_QUEUES returns 0 entries.
Additional Information: The /IBMMON/ITM_QOUT_GET_QUEUES function module stopped collecting the data even though the data was present in the SAP system. Due to this, SYSID ‘+++’ was displayed on the Tivoli Enterprise Portal. The function module has been rectified for collecting the data from the SAP
systems having versions greater than 46C and SP level SPKB46C39.

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

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

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

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

Enhancement: 67334
Abstract: Additional functionality to handle the MAI missing Alerts in the Function Module /IBMMON/ITM_MAIALRT_INX.
Additional Information: Function module /IBMMON/ITM_MAIALRT_INX is modified to fetch the MAI Alerts which are missed by ITM SAP Agent as these MAI Alerts are inserted into table /IBMMON/ITM_ALIX with some delay by SAP.
Note: 
1) SAP system time and ITCAM SAP Agent machine time should be in sync up to accuracy of seconds.
2) In order to have full collection of MAI Alerts, there is an additional overlap time being added to the sampling time frequency given by the ITCAM SAP Agent.

This additional overlap time is configurable parameter on the SAP side.
Note:
a)By default the additional overlap time will be 1 min i.e. 60 seconds.
b)Maximum additional overlap time that can be configured will be 5 mins i.e. 300 seconds.
c)If the user wants the additional overlap time greater than 1 min i.e. 60 seconds and less than or equal to 5mins i.e. 300 mins, then he should follow the below steps.

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

3.0 Architecture and prerequisites

==========================================
This Fix Pack is supported on all operating systems listed in the IBM Tivoli Composite Application Manager Agent for SAP Applications.

Installation, Configuration, Reference, and Troubleshooting guides, Version 7.1.1 Fix Pack 8:
Link: SAP Applications Agent

3.1 Prerequisites for this fix:
--------------------------------
For SAP agent version 7.1.1 Fix Pack 8, SAP NetWeaver RFC SDK libraries 7.50 PL11 are prerequisite. Download the required RFC libraries from SAP support portal. No backward compatibility support has been provided with this fix for SAP NetWeaver RFC SDK libraries of any previous versions of 7.20 and 7.50.
As this fix is cumulative, it can be installed on any fix level for this version, release, and modification level above the prerequisite. 

4.0 Download Instructions

============================
The installation package "ITCAM_SAP_APP7.1.1.8_MLMP.tar.gz" can be downloaded from Passport Advantage using Part Number M0C5JML.

5.0 Installation instructions

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

When you download this fix pack image 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.

  5.1 Before installing the fix: 
  -----------------------------
  - The prerequisites listed under section 3.1 entitled, 'Prerequisites for this fix' must be installed for upgrade.
  - In this README, the <CANDLEHOME> symbol indicates 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.
  - 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
  -As there is no uninstall utility for this fix pack, be sure to back up 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.

  2. Expand the archive file by 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 the supported operating systems.

  3. Use the procedures in the 'IBM Tivoli Composite Application Manager Agent for SAP Applications Version 7.1.1 Fix Pack 7 Installation and Configuration 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. In 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 by using the 'tar' command on UNIX systems or an extract utility on Windows systems. This step creates a directory structure that contains fixes for all of the supported operating systems.

  3. To add the agent fix pack bundles into the remote deploy depot, use the 'tacmd addBundles' command found in $CANDLEHOME/bin on UNIX systems or in %CANDLE_HOME%\bin on Windows systems.
For more  information on the 'tacmd addBundles' command, see Appendix A. Commands reference of the 'IBM Tivoli Monitoring Command Reference'.
     On UNIX systems, if the fix was expanded to <TEMP>/<PARTNUMBER>:
     > $CANDLEHOME/bin/tacmd addBundles -i 
                 <TEMP>/<PARTNUMBER>/unix -t sa  
     
On Windows systems, if the fix was expanded to <TEMP>\<PARTNUMBER>:
     > %CANDLE_HOME%\bin\tacmd addBundles -i 
                 <TEMP>\<PARTNUMBER>\WINDOWS\Deploy -t sa  

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

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

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

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

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

     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 07110800
     Note:
     - The component (-t) for the 'tacmd updateAgent' command is 
       specified as two characters (sa), not three characters (ksa).
     - The node (-n) for the 'tacmd updateAgent' command is the managed
       system name of the operating system (OS) agent to be updated. The
       target node for the 'tacmd updateAgent' command is always an OS
       agent.
 
5.4 Agent support update:
------------------------
  Use the following steps to update the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, or Tivoli Enterprise Portal Desktop.

  1. Transfer the appropriate archive file to the Tivoli Enterprise Monitoring Servers, Tivoli Enterprise Portal Servers, or Tivoli Enterprise Portal Desktops. 

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

  3. Use the procedures in the 'IBM Tivoli Composite Application Manager Agent for SAP Applications Version 7.1.1 Fix Pack 7 Installation and Configuration Guide' to install the support.

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

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

5.5 Installing SAP agent transport:
----------------------------------
  Note: From this fix onwards, a single ITM file is provided for importing SAP transport on all the supported SAP versions having BADI or non-BADI implementation.
  This procedure installs the SAP transport into the SAP system. You are not required to uninstall the previous transport before installing this transport.
    1. Go to the ABAP directory in the location where you expanded the fix archive file.

    2. Copy the transport files into the SAP environment as follows:

       a. The following sets of transport files are in the ABAP directory of the SAP agent fix archive:

          1) K711_00151U.ITM and R711_00151U.ITM in /ABAP directory.
             These files are for Unicode versions of the transport.
          2) K711_00151_DELETE.ITM and R711_00151_DELETE.ITM
             These transport files remove the ABAP code. Do not import the DELETE transport unless you stop using the product entirely and want to remove the transports from your SAP systems.

       b. Copy your transport files to the SAP Transport System data directory as follows:
          1) Copy the K711_00151U.ITM file to the cofiles directory.
          2) Copy the R711_00151U.ITM file to the data directory.

    3. Run the following command where:
         SID Target SAP : system ID
         PROFILE_NAME : Name of the tp profile file
         nnn : Number for the target client where the agent is to run
             tp addtobuffer ITMK711_00151U SID
             pf=\usr\sap\trans\bin\PROFILE_NAME
             tp import ITMK711_00151U 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.

    4. Default password for IBMMON_AGENT is replaced with random generation of password. User can modify the password of their choice according to their password policy.

       Use the following procedure to change your password:
        1. Go to SU01 transaction.
        2. In the user field, enter username and click change icon.
        3. Open the Logon Data tab.
        4. In New Password and Repeat Password fields, enter the password of
           your choice.
        5. Click save.

        Important: You must confirm that /IBMMON/AUTH authorization profile is present in the Profile tab.
        Use the following procedure to create the IBMMON/AUTH authorization profile:
         a) Press F4 and Search /IBMMON/AUTH.
         b) Select /IBMMON/AUTH from the search result and click Save.

6.0 Additional installation information

6.1 Verifying the update:
------------------------
  1. To verify that the agent is updated correctly, use the tacmd command to view the current version of the agent after the agent is restarted. You need 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 list Systems command is specified as two characters (sa), not three characters (ksa).
     When the agent update is successful, the agent version must be displayed as 07.11.08.00
     After the agent is restarted, you can also use the GUI to verify that the agent was successfully updated.

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

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

     On non-Windows systems:
     ----------------------
     To validate that all components are installed, run the following command:
     For example:    

     > %CANDLE_HOME%/bin/cinfo -i

     Note: cinfo output might differ depending on ITM version.

     
     *********** Mon Apr  3 12:12:13 IST 2023 ******************
    User: root Groups: root
    Host name : control-plane        Installer Lvl:06.30.07.19
    CandleHome: /opt/IBM/SAP
    ***********************************************************
    ...Product inventory

     ax   IBM Tivoli Monitoring Shared Libraries
         lx8266  Version: 06.30.07.21

    gs   IBM GSKit Security Interface
         lx8266  Version: 08.00.55.17

     jr   Tivoli Enterprise-supplied JRE
         lx8266  Version: 08.07.10.00

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

7.0 Known problems and workarounds

==================================
Prerequisite scanner is not running on Z-suse.
Problem Description: The following message is displayed while upgrading SAP agent from 711FP7 to 711FP8: "There was an error running in Prerequisite Scanner".
Workaround: Skip the prerequisite scanner and continue with installation.

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 the programs to obtain the highest level of support.
Note: The mySAP agent does not run correctly if not installed with a compatible level of the transport.

Fix Level          Delivered Transport      Minimum Transport Level
----------       ----------------------   --------------------------
FP0008               ITMK711_00151             ITMK711_00151

8.2 Additional Information:
---------------------------
 
  1. TEMA version is upgraded to ITM 630 FP7 SP13 from 630 FP7 SP12 for 
     7.1.1-TIV-ITM_SAP-FP0008 SAP Agent.
  2. Changed the unit from “kb to MB” under the attribute caption for the below attributes of Database Details (KSAORADTL) and Database Summary (KSAORASUM)
     i. For KSAORADTL Attribute Group following attributes caption has been changed from "kb to MB"-
     Size, Size\Change\Per Day, Size\Used, Size\Free, Minimum\Free, Maximum\Free, <Max>\Next\Extent,
     Size_64, Size\Change\Per Day_64, Size\Used_64, Size\Free_64, Minimum\Free_64, Maximum\Free_64,
     <Max>\Next\Extent_64
     ii. For KSAORASUM Attribute Group following attributes caption has been changed from "kb to MB"-
     Total\Size, Total\Used, Total\Free, Minimum\Free, Total\Size\MB, Total\Used\MB, Total\Free\MB, Minimum\Free\MB, Total\Size_64, Total\Used_64, 
     Total\Free_64, Minimum\Free_64, Total\Size\MB_64, Total\Used\MB-64, Total\Free\MB_64, Minimum\Free\MB_64
  3. There will be no data for Analysis time (of Database Details and Database summary) and CPU Time(sec) and CPU Usage(%) 
     attributes (of Oracle database performance) workspaces. These attributes data will be blank as no data is coming for it from SAP system.
  4. 711FP8 is not backward compatible. Hence, you must install 711FP8 agent and 711FP8 supports.
  

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.
Not withstanding 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.