IBM Tivoli Monitoring for Applications: mySAP, 5.1.0-TIV-ITM_SAP-IF0019

(C) Copyright International Business Machines Corporation 2010.

All rights reserved.

Component: IBM(R) Tivoli(R) Monitoring for Applications: mySAP.com(R),
Version 5.1.0

Component ID: 5724B97SP

Interim Fix 19, 5.1.0-TIV-ITM_SAP-IF0019

Date: March 12, 2010

Table of contents

1.0 General description
2.0 Problems fixed
3.0 Architecture
4.0 Prerequisites
5.0 Image directory contents
6.0 Installation instructions
7.0 Known problems and work arounds
8.0 Additional product information
9.0 Notices

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

It includes all updates to the three event adapters (CCMS,IDOC and
Syslog) made since IBM Tivoli Monitoring for Applications, Version
5.1.0: mySAP.com Limited Availability Fix 06 was published on
June 30, 2005.

It also includes all updates to the resource model data collector
(mySAPdp.jar) since September 19, 2006.


2.0 Problems fixed
===================
This fix addresses the following problems.

2.1 APARs
---------
APAR: IZ68071
Abstract: 'CONFIGURE EVENT ADAPTER' fails for CCMS adapter
Additional information: When executing the 'Configure Event Adapter'
task for the CCMS adapter, it fails with return code 1.

2.2 Defects
-----------
None.

2.3 Enhancements
----------------
Add SAP Logon Group support for the CCMS adapter.

2.4 Superseded fixes
--------------------
5.1.0-TIV-ITM_SAP-IF0018
5.1.0-TIV-ITM_SAP-IF0017
5.1.0-TIV-ITM_SAP-LA0016
5.1.0-TIV-ITM_SAP-LA0015
5.1.0-TIV-ITM_SAP-LA0014
5.1.0-TIV-ITM_SAP-LA0013
5.1.0-TIV-ITM_SAP-LA0009
5.1.0-TIV-ITM_SAP-LA0008 - Note: see section 2.4 for more information.
5.1.0-TIV-ITM_SAP-LA0004


2.5 APARS and defects included from superseded fixes
----------------------------------------------------

5.1.0-TIV-ITM_SAP-LA0018
------------------------
APAR: IZ53739
Abstract: CCMS ADAPTER IS NOT USING THE DAYLIGHT SAVINGS TIME ZONE
Additional information: The aid_alerttime event slot is incorrect in
CCMS alerts when daylight saving time is enabled.

APAR: IZ54873
Abstract: WR3MONAC ON WINDOWS IS NOT CLOSING CCMS ALERTS
Additional information: wr3monac.exe crashes.

APAR: IZ54917
Abstract: Syslog adapter generates ABAP CONVT_NO_NUMBER dump

Defect: 177456
Abstract: When configuring the CCMS event adapter, the
ABH0599W warning message appears. This is applicable
to mySAP releases 700, 701 and 710.

5.1.0-TIV-ITM_SAP-LA0017
------------------------
APAR IZ46910
Abstract: WR3STATI REPORTS INCORRECT STATISTICAL TIMES
Additional information: The Tivoli Enterprise Data Warehouse
Collector reports incorrect values when the mySAP
transaction runtime, waittime, CPUtime or DBtime is
more than 2.097.152 milliseconds(ms).

APAR IZ45292
Abstract: AID_ALERTDATE/AID_ALERTTIME SLOTS CONTAIN INCORRECT
DATE/TIME in CCMS alerts
Additional information: CCMS alerts were not being closed because
of an incorrect date and time in the AID_ALERTDATE and
AID_ALERTTIME slots.

Defect: 174589
Abstract: Add support for discovery of SAP 7.10 J2EE server
Additional Information: Discovery of the J2EE server was not handling
the SAP 7.10 version information properly. As a result,
running the Verify JMX task resulted in the following
error message:
"ABH8011E Context variable ABH_NodeID is missing from the
mySAPJ2EEClusterNode object".

Note: In NetWeaver SAP 7.10, the Dispatcher has been
removed; this function is now handled by the ICM. This
means a Dispatcher is not represented by an icon on the
Tivoli Desktop. As a result, the resource models for the
dispatcher object do not work and are not supported for
SAP 7.10. See technote #1377394 for more information.

5.1.0-TIV-ITM_SAP-LA0016
------------------------
APAR: IZ17121
Abstract: INSTALLATION HANGS FOR 5.1.0-TIV-ITM_SAP-LA0004 AND
5.1.0-TIV-ITM_SAP-LA0006

APAR: IZ23693
Abstract: SAP_IDOC_XMIT EVENT IS MISSING ENDPOINT NAME

APAR: IZ26780
Abstract: SAP_RFC_ERROR_CCMS EVENT RESULTS IN PARSING_FAILED

5.1.0-TIV-ITM_SAP-LA0015
------------------------
APAR: IZ03997
Abstract: ITM51 MYSAP RMS CONSUME FILE DESCRIPTORS IN SOLARIS 9
Additional Information: File descriptor usage grows above the Solaris
9 limitation of 256, leading to the next fopen() to fail,
and consequently, the embedding application, IBM Tivoli
Monitoring (ITM) to crash.

5.1.0-TIV-ITM_SAP-LA0014
------------------------
APAR: IY97327
Abstract: WORK PROCESS RMS IN ERROR DUE TO "**" IN FIELD FROM SAP

Enhancement: Add install option to shorten time for installation.
Additional Information: This fix provides an installation option
to defer the task of pushing updated files to the endpoint.
Instructions are in section 6.0 below.

5.1.0-TIV-ITM_SAP-LA0013
------------------------
APAR: IY99575
Abstract: CCMS ALERTS ARE NOT DELETED AND MYSAP USERID IS LOCKED
AFTER REPEATED INVALID LOGIN ATTEMPTS

5.1.0-TIV-ITM_SAP-LA0009
------------------------
APAR: IY87349
Abstract: "ALERTS PER CCMS ATTRIBUTE" SET TO 0 DOES NOT WORK AS
DOCUMENTED

APAR: IY89104
Abstract: MYSAP_BACKGROUNDWPSTATUS: RETRYING (18)

APAR: IY87350
Abstract: CCMS ADAPTER SHOULD SEND A CRITICAL EVENT AND EXIT WHEN
MEMORY ALLOCATION ERRORS CRIPPLE IT

5.1.0-TIV-ITM_SAP-LA0008
------------------------
APAR: IY88912
Abstract: MYSAP_DATABASECONNECTION RESOURCE MODEL IS NOT CLEANING UP
FILES

Note: Only the resource model data collector (mySAPdp.jar) is
superseded. 5.1.0-TIV-ITM_SAP-LA0008 contains additional fixes for
JMX resource models and J2EE discovery. If you need this support,
you must install 5.1.0-TIV-ITM_SAP-LA0008 before installing this fix.

5.1.0-TIV-ITM_SAP-LA0004
------------------------
APAR: IY67764
Abstract: MYSAP TEC ADAPTERS NOT TRANSLATING UNICODE CORRECTLY

APAR: IY77165
Abstract: NUMEROUS SYSLOG EVENTS BEING SENT TO TEC BECAUSE OF AN
INVALID DATE

Defect: 154622
Abstract: Modify the Syslog adapter to use the J_8C1_SYSLOG_INFO
function module


3.0 Architecture
=================
The following link is for the Tivoli operating system and application
support matrix. Please refer to this matrix for the latest
certification information.

http://www-306.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

4.0 Prerequisites
==================
The following sections provide the prerequisites for this fix.

SAP Release Support:

IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com
provides monitoring and management capabilities based on the SAP
Basis and kernel levels. The product, in general, does not provide
monitoring or management specific to a particular SAP product. To
determine compatibility of the software to the SAP product,
determine the SAP basis/kernel level of the SAP product and check
that against the support list below:

- R/3 Kernel Releases 4.0B, 4.5B, 4.6B, 4.6D, 6.10, 6.20, 6.40,
7.00, 7.0.1, 7.10 - See section 7.0 "Known
problems and work arounds" for 7.xx releases.
- ITS Releases 4.6C, 4.6D
- Support for Unicode on kernel releases 6.20, 6.40
- Application specific monitoring
- APO 3.0
- BW 2.1, 3.0, 3.5
- R/3 4.6C/D and R/3 Enterprise 4.70 ES1 and ES2
- CRM 2.0-3.0
- SCM 3.0
- SCM 4.0, with EBP 3.0 and 4.0
- EBP 3.0-4.0
- Solution Manger 3.0, 3.1 and 4.0
- SAP MCOD systems

Note: The following SAP products/releases have been taken out of
support by SAP:
- R/3 Kernel Releases 4.0B, 4.5B, 4.6B

4.1 Prerequisites for this fix
------------------------------
IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com
Fix Pack 06 (5.1.0-SAP-FP06)
IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com
Limited Availability Fix 06 (5.1.0-TIV-ITM_SAP-LA0006)


5.0 Image directory contents
=============================
This fix contains the following files:

- 5.1.0-TIV-ITM_SAP-IF0019.README - This README file
- 5.1.0-TIV-ITM_SAP-IF0019.tar file.

The tar file contains the following directories and files:

- 5.1.0-TIV-ITM_SAP-IF0019
- 51SAPIF19 - IBM Tivoli Monitoring for Applications, Version 5.1.0:
mySAP.com product files.
- ABAP - IBM Tivoli Monitoring for Applications, Version 5.1.0:
mySAP.com ABAP transport files.
- COLLECT - IBM Tivoli Monitoring for Applications, Version 5.1.0:
mySAP.com warehouse enablement product files
- wr3stati.exe
- wr3snap.exe

When this fix is installed, the following files are replaced or added
on the Tivoli management region:

# installation script
$BINDIR/../generic_unix/TME/ABH/510SAPIF19LCF.init
$BINDIR/../generic_unix/TME/ABH/sh/sap_common_discover.sh
$BINDIR/../generic_unix/TME/ABH/sh/sap_configure_event_adapter.sh

# Adapter binary files: $BINDIR/../lcf_bundle.40
bin/w32-ix86/TME/ABH/wr3monac.exe
bin/%INTERPS%/TME/ABH/wr3moni
bin/linux-ix86/TME/ABH/wr3moni
bin/linux-s390/TME/ABH/wr3moni
bin/generic_unix/TME/ABH/sh/sap_common_adapter_edit.sh
../aix4-r1/TME/ABH/sh/sap_configure_event_adapter_cb.sh

# ABAP Transports: $BINDIR/../generic_unix
TME/ABH/abap/cofiles/K900329.TV2
TME/ABH/abap/data/R900329.TV2
TME/ABH/abap/cofiles/K900791.TV1
TME/ABH/abap/data/R900791.TV1


6.0 Installation instructions
==============================
Apply this fix to your Tivoli management region server, all managed
nodes hosting mySAP Tivoli objects, and all gateways that manage mySAP
endpoints. Apply the fix to your Tivoli management region server first.

Since there is no uninstall utility for this fix, perform a Tivoli
environment backup operation before installing this fix. See the
documentation for the wbkupdb command for details on how to backup
your Tivoli database.

6.1 Copying updated files to endpoints
--------------------------------------
During installation, this fix includes the option to defer the
task of pushing updated files to the endpoint. This normally takes
place during installation; however, you can choose to perform this
task after installation has completed. This task MUST be performed
either during installation or afterwards in order for the fixes to
take effect and the product to function properly.

The Install Options dialog is displayed by clicking the
"Select Install Options" button on the Install Patch dialog.
The Install Options dialog includes the option:
"Copy all updated files to endpoints".
The option is checked by default. When checked, all updated IBM
Tivoli Monitoring for mySAP Application Server endpoint binary files
are automatically pushed to endpoints with mySAP objects. This does
not distribute monitoring profiles. To incorporate the adapter
updates, the installation script stops and restarts event adapters
running on the application servers. This restart process occurs when
the managed node hosting the endpoints is updated.

If the option is unchecked, all updated endpoint-related files must
be pushed down manually after the installation is complete. The
"510SAPIF19LCF.init" script can be used to push updates to all
endpoints where mySAP objects are registered. The script can be run
from either the Tivoli management region or from any managed node
where the prerequisites are installed.

The "510SAPIF19LCF.init" script is located in the
$BINDIR/../generic_unix/TME/ABH directory.
Usage: (from a Tivoli sourced command window)
- cd $BINDIR/../generic_unix/TME/ABH
- ./510SAPIF19LCF.init <mySAPAppServer1> <mySAPAppServer2> ..

Example:
./510SAPIF19LCF.init pine_D04_00 pine_D04_01

Note: Running the 510SAPIF19LCF.init script with no arguments
results in the upgrade of all mySAPAppServers.

6.2 Applying the fix
--------------------
Copy the tar file to the target machine and untar the file on
that machine. Use the following steps to untar the fix file:

1) Extract the fix contents into a working directory. Assume
that the symbol $fix points to this directory.

A) On a UNIX(R) system:
cd $fix
tar -xvf 5.1.0-TIV-ITM_SAP-IF0019.tar

B) On a Windows(R) system:
cd %fix%
tar -xvf 5.1.0-TIV-ITM_SAP-IF0019.tar

Note: If you are extracting the tar image on a Windows system,
the executable for tar is in the Tivoli installation
directory on Windows under bin/w32-ix86/tools/tar.exe.

You must use the tar command to extract the image.
Do not use a zip utility.


2) Use the following steps to install the fix from the Tivoli
desktop.

Note: You must have the install_product and super authorization
roles to successfully install this fix:

a) Click Install -> Install Patch... option from the
Desktop menu to display the Install Patch window.
b) Click Select Media... to display the File
Browser dialog box.
c) Enter the path to the directory containing the fix,
$fix/5.1.0-TIV-ITM_SAP-IF0019/51SAPIF19, in the Path
Name: field and select the 510SAPIF.IND file.
d) Click Set Media & Close to return to the
Install Patch window.
e) The install list now contains the name of the fix.
Click the name of the fix.
f) On the Set Install Options window, check the
"Copy all updated files to endpoints" (default),
if updated files should be pushed to the endpoints and
click Set.
g) Select the clients on which to install the fix. Fixes
typically need to be installed on the Tivoli management
region server and on each managed node.
h) Click Install to install the fix.
i) When the installation completes successfully, if the
installation option "Copy all updated files to endpoints"
was not selected then you must run the 510SAPIF19LCF.init
script manually to upgrade the mySAPAppServer objects.

3) Use the following steps to install the fix from a Tivoli sourced
command window using the wpatch command.

a) From the Tivoli sourced command window:
wpatch -c $fix/5.1.0-TIV-ITM_SAP-IF0019/51SAPIF19 \
-i 510SAPIF.IND @InitEP@=1

where:

@InitEP@ Setting this variable to 1 causes updates to be
copied down to all mySAP endpoints. This is the
default. A subset of mySAPAppServers cannot
be specified.

If @InitEP@ is set to 0, the updates are not
pushed to the mySAP endpoints.

If @InitEP@ is not specified, the default
settings are used; updates are copied to
all mySAP endpoints.

6.3 Applying the Tivoli transport
---------------------------------
This fix includes the latest transports for your mySAP NON-Unicode
and Unicode systems. The SAP Basis administrator installs these
transports on your SAP systems.

The transport files are located at $PATCH/ABAP.

Base transport files:
For SAP Unicode systems - replaces version 149
K900791.TV1
R900791.TV1
For all other SAP systems - replaces version 557
K900329.TV2
R900329.TV2

6.4 Applying the Data Collection Facility component patch
---------------------------------------------------------
From the data collection computer, perform the following steps:

1) Untar the fix pack image on the machine running the Data Collection Facility,
using the instructions provided earlier.

2) Stop wr3stati.exe by issuing
<data_collection_installation_dir>\wr3stati.exe -stop

3) Back up the following current programs:
- wr3stati.exe
- wr3snap.exe

4) Copy the following files from <patch_location>\COLLECT
to <data_collection_installation_dir>:
- wr3stati.exe
- wr3snap.exe


7.0 Known problems and work arounds
=====================================


Abstract: Resource models for the dispatcher object are not supported
for mySAP 7.10
Problem: In NetWeaver SAP 7.10, the Dispatcher has been removed; this
function is now handled by the ICM. This means a Dispatcher
is not represented by an icon on the Tivoli Desktop. As a
result, the resource models for the dispatcher object do not
work and are not supported for mySAP 7.10.
See technote #1377394 for more information.
Work around: None.


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

- When running the adapters from this fix, the associated log files
on the endpoint contain a line which says
"built on Feb 18 2010 at ...".

- The fix for APAR IY89104 entailed changes to the following resource
model: mySAP Background Work Processes Status.
If 5.1.0-TIV-ITM_SAP-LA0009 was not previously installed and you are
running this resource model, monitoring profiles which include this
resource model must be redistributed.

- The setting in the Alerts Per CCMS Attribute parameter is a global
parameter because it affects all attributes in the monitoring tree.
Some attributes, such as CPU utilization, are significant only for
the last reported value. Other attributes, such as ABAP dumps, are
significant for every occurrence. For example, specifying a low
number, such as 1, for the Alerts Per CCMS Attribute parameter might
provide good tuning for CPU utilization alerts, but it also causes
the CCMS event adapter to send a limited number of events for ABAP
dumps. Specifying a high number for the Alerts Per CCMS Attribute
parameter causes the CCMS event adapter to send more events for
ABAP dumps, but it also causes the CCMS event adapter to send a
large number CPU utilization events that are not important.


9.0 Notices
==========
This information was developed for products and services offered in the United
States. IBM may not offer the products, services, or features discussed in this
document in other countries. Consult your local IBM representative for information
on the products and services currently available in your area. Any reference to an
IBM product, program, or service is not intended to state or imply that only that
IBM product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify
the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

The following paragraph does not apply to the United Kingdom or any other country
where such provisions are inconsistent with local law:

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 states do not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement may not apply to you.

Trademarks and service marks
-----------------------------

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks
of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks
is available on the Web at "Copyright and trademark information" at
www.ibm.com/legal/copytrade.shtml.

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

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.

SAP, R/3, mySP.com and mySAP are registered trademarks of SAP AG in
Germany and in several other countries.

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

- IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com
Fix Pack 06 (5.1.0-SAP-FP06)
- IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com
Limited Availability Fix 06 (5.1.0-TIV-ITM_SAP-LA0006)

Please refer to the full README contained in the Description section above for general installation instructions.