tivoli® manager for...

Tivoli® Manager for R/3**

Release Notes Version 2.1

Tivoli Manager for R/3 Release Notes (September 2000)

Copyright NoticeCopyright © 1997, 2000 by Tivoli Systems Inc., an IBM Company, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of Tivoli Systems. Tivoli Systems grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the Tivoli Systems copyright notice. No other rights under copyright are granted without prior written permission of Tivoli Systems. The document is not intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose.Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

TrademarksThe following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RS/6000, Tivoli, Manage. Anything. Anywhere., The Power To Manage. Anything. Anywhere., TME, NetView, Cross-Site, Tivoli Ready, Tivoli Certified, Planet Tivoli, Tivoli Enterprise.

In Denmark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation.

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

R/3 is a trademark of SAP AG.

Oracle is a registered trademark of Oracle Corporation.

Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others.

NoticesReferences in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli System’s or IBM’s valid intellectual property or other legally protectable right, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user.Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.

Tivoli Manager for R/3 Release Notes v

Contents

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Additional Information .......................................................................................... 1

Accessing Publications Online...................................................................... 2

Ordering Publications.................................................................................... 2

Providing Feedback about Publications ........................................................ 2

Contacting Customer Support ....................................................................... 3

New Features ......................................................................................................... 3

System Requirements............................................................................................. 4

Software Requirements ................................................................................. 4

Operating System Platform Support..................................................... 4

Tivoli Product Support ......................................................................... 5

Support for R/3 Releases ...................................................................... 7

Support for SAP Internet Transaction Server....................................... 7

Support for SAPGUI Distribution ........................................................ 8

Hardware Requirements ................................................................................ 8

Installation Notes ................................................................................................... 8

Prerequisites .................................................................................................. 9

Summary ....................................................................................................... 9

Uninstalling Manager for R/3 ..................................................................... 12

Defects Fixed ....................................................................................................... 13

Known Product Defects, Limitations, and Workarounds .................................... 13

Product Notes....................................................................................................... 17

R/3 Transports ............................................................................................. 17

Considerations for Upgrading the Syslog Event Adapter ........................... 18

Accessing Product Documentation ............................................................. 19

vi Release Notes Version 2.1

Tivoli Manager for R/3 Release Notes 1

1.Release Notes

This Release Notes document provides important information about Tivoli Manager for R/3 (Manager for R/3) Version 2.1. These notes are the most current information for the product and take precedence over all other documentation.

Please review these notes thoroughly before installing or using this product.

You will notice that both Tivoli and TME 10 are used in our sales, marketing, and product information materials. These terms are interchangeable. We will be removing references to TME 10 in future product releases.

These Release Notes include the following topics:

■ “New Features” on page 3

■ “System Requirements” on page 4

■ “Installation Notes” on page 8

■ “Defects Fixed” on page 13

■ “Known Product Defects, Limitations, and Workarounds” on page 13

■ “Product Notes” on page 17

Additional InformationThe following sections describe how to access publications online, order publications, provide feedback about publications, and contact customer support.

2 Release Notes Version 2.1

Accessing Publications OnlineThe Tivoli Customer Support Web site (http://www.tivoli.com/support/) offers a guide to support services (the Customer Support Handbook); frequently asked questions (FAQs); and technical information, including release notes, user’s guides, redbooks, and white papers. You can access Tivoli publications online at http://www.tivoli.com/support/documents/. The documentation for some products is available in PDF and HTML formats. Translated documents are also available for some products.

To access most of the documentation, you need an ID and a password. To obtain an ID for use on the support Web site, go to http://www.tivoli.com/support/getting/.

Resellers should refer to http://www.tivoli.com/support/smb/index.html for more information about obtaining Tivoli technical documentation and support.

Business partners should refer to “Ordering Publications” for more information about obtaining Tivoli technical documentation.

Ordering PublicationsOrder Tivoli publications online at http://www.tivoli.com/support/Prodman/html/pub_order.html or by calling one of the following telephone numbers:

■ U.S. customers: (800) 879-2755

■ Canadian customers: (800) 426-4968

Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoli products and documentation, and we welcome your suggestions for improvements. If you have comments or suggestions about our products and documentation, contact us in one of the following ways:

■ Send e-mail to [email protected].

■ Fill out our customer feedback survey at http://www.tivoli.com/support/survey/.


Contacting Customer SupportIf you need support for this or any Tivoli product, contact Tivoli Customer Support in one of the following ways:

■ Submit a problem management record (PMR) electronically from our Web site at http://www.tivoli.com/support/reporting/. For information about obtaining support through the Tivoli Customer Support Web site, go to http://www.tivoli.com/support/getting/.

■ Submit a PMR electronically through the IBMLink™ system. For information about IBMLink registration and access, refer to the IBM Web page at http://www.ibmlink.ibm.com.

■ Send e-mail to [email protected].

■ Customers in the U.S. can call 1-800-TIVOLI8 (1-800-848-6548).

■ Customers outside the U.S. should refer to the Tivoli Customer Support Web site at http://www.tivoli.com/support/locations.html for customer support telephone numbers.

When you contact Tivoli Customer Support, be prepared to provide the customer number for your company so that support personnel can assist you more readily.

New FeaturesManager for R/3 Version 2.1 provides the following new features:

■ A user-configurable IDOC Event Adapter to monitor SAP IDOCs (Intermediate Documents) for error status codes and report them as TEC events.

■ Japanese language support for the Syslog Event Adapter.

■ Transparent support for HP-UX 11.00 running in 64-bit mode.

■ Support for OS/390 environments that use data sharing.

■ Support for integration with the Tivoli Manager for DB2 and the Tivoli Manager for Oracle to extend R/3 database server status reporting.

■ Improved R/3 application server status monitoring.

■ Tasks that perform the following actions:


• Configure extended R/3 database server status reporting

• Start and stop R/3 Internet Transaction Servers (R/3 ITS servers)

• Create SAPGUI file packages from an R/3 installation server for Windows SAPGUI versions 4.5B and later

■ Monitors for R/3 ITS server status, R/3 UNIX and R/3 Windows NT file systems, saplpd and saprouter daemons, R/3 message server status, extended memory, heap memory, and user sessions.

■ Enhancements to Tivoli GEM Instrumentation for Tivoli Manager for R/3 Version 2.1 (Tivoli GEM instrumentation).

System RequirementsThis section describes the system requirements, including software and hardware, that Manager for R/3 supports for Tivoli servers, managed nodes, and TMA endpoints.

Software RequirementsThis section describes the Manager for R/3 software requirements.

Operating System Platform Support

Manager for R/3 supports the following platforms in 32-bit mode:

Platform Required Level

AIX AIX 4.3.x

Note: Tivoli’s support of AIX is limited to AIX on IBM systems. Tivoli does not support AIX on other hardware.

HP-UX ■ HP-UX 10.20

■ HP-UX 11.00

Sun Solaris ■ Sun Solaris 2.6

■ Sun Solaris 2.7


Manager for R/3 supports the following platform in 64-bit mode:

Tivoli Product Support

This section describes required and optional Tivoli products that Manager for R/3 supports.

Required Tivoli Products

Manager for R/3 requires the following Tivoli products:

■ Tivoli Management Framework

■ Tivoli Enterprise Console, including the Tivoli Enterprise Console Adapter Configuration Facility

■ Tivoli Distributed Monitoring, including the Universal Monitoring collection

■ Tivoli Application Proxy

The following table lists the supported releases, required patches, and additional patch information for each required product:

Windows NT Windows NT 4.0 with Service Pack 5, 6, or 6A


HP-UX HP-UX 11.00


Product Release Required Patches Patch Notes

Tivoli Management Framework

3.6.1 None 3.6.1-TMF-0004 requires 3.6.1-TMF-0044

Tivoli Management Framework

3.6.2 3.6.2-TMF-0008 None


Optional Tivoli Products

Manager for R/3 supports the following optional Tivoli products:

■ Tivoli Software Distribution 3.6.1 or 3.6.2

■ Software Installation Service 3.6.1 with the following product patch:

3.6.1-SIS-0005

■ Tivoli Global Enterprise Manager 2.2.1

Tivoli Enterprise Console

3.6.1 None If you are using the Syslog Event Adapter in a Japanese environment, the following patch is required to properly display TEC events:

3.6.1-TEC-0013

Tivoli Enterprise Console

3.6.2 None If you are using the Syslog Event Adapter in a Japanese environment, the following patches are required to properly display TEC events:

■ 3.6.2-TEC-0001

■ 3.6.2-TEC-0004

Tivoli Distributed Monitoring

3.6.1 ■ 3.6.1-DMN-0008

■ 3.6.1-DMN-0013

To ensure that a warning response from a monitor generates a TEC event (see “Known Product Defects, Limitations, and Workarounds” on page 13), the following patch is required:

3.6.1-DMN-0026

Tivoli Distributed Monitoring

3.6.2 None None

Tivoli Application Proxy

1.1 1.1-APX-0005 None

Product Release Required Patches Patch Notes


• Tivoli GEM Event Enablement

• Tivoli GEM console

• Tivoli GEM server

■ Tivoli Manager for DB2 1.1 (for managed nodes only)

■ Tivoli Manager for Oracle 1.2 (for managed nodes only)

Support for R/3 Releases

This sections lists the R/3 releases that Manager for R/3 supports. This support is limited to the extent that SAP supports its R/3 releases. This means that Manager for R/3 automatically drops support for an R/3 release when SAP drops support for that release. The following list identifies supported R/3 releases and end-of-support dates, if applicable, based on SAP’s published release strategy.

■ R/3 3.0F, until the end of September, 2000

■ R/3 3.1H, until the end of October, 2000

■ 3.1I

■ R/3 4.0B

■ R/3 4.5B

■ R/3 4.6A, until the end of September, 2000

■ 4.6B

■ 4.6C

Support for SAP Internet Transaction Server

Manager for R/3 supports the same SAP Internet Transaction Server (ITS server) general availability release levels that SAP supports. The

Important Notice

SAP’s approach to alert processing has changed significantly in R/3 releases 4.6x. For more information about this change and possible implications to using the Alert Event Adapter, refer to the section about using the Alert Event Adapter in "Chapter 6. Managing R/3 Events" in the Tivoli Manager for R/3 User’s Guide.


supported ITS server release levels apply to Windows NT only. The following table describes the ITS server release levels and the related R/3 release that Manager for R/3 supports:

Support for SAPGUI Distribution

Manager for R/3 provides SAPGUI distribution for the following SAP-supported platforms:

■ UNIX (AIX, HP-UX, Sun Solaris)

■ Windows NT

■ Windows 95/98

Hardware RequirementsIn addition to space requirements for the management platform, a minimum of 10 MB of free disk space is required for all systems. An additional 10 MB of free disk space is required if you plan to install Tivoli GEM Instrumentation for Tivoli Manager for R/3 Version 2.1.

Installation NotesThis section summarizes the procedure, including prerequisite steps, for installing Manager for R/3.

ITS Server Release Related R/3 Release

2.1 3.1I and 4.0B

4.5B 4.5B

4.6A, until the end of September, 2000

4.6A, until the end of September 2000 as noted in “Support for R/3 Releases” on page 7

4.6B 4.6B

4.6C 4.6C


PrerequisitesSatisfy the following requirements before installing:

1. Ensure that you are running on a supported operating system and that you install all prerequisite software. See “Software Requirements” on page 4.

2. Configure the Tivoli Management Regions (TMRs). For information, refer to "Chapter 2. Planning for and Installing Manager for R/3" in the Tivoli Manager for R/3 User’s Guide.

3. If you are running R/3 application servers on TMA endpoints, ensure that the TMA endpoints are properly configured and functional. Refer to the TME 10 Framework Planning and Installation Guide.

4. Ensure that the Application Proxy is installed. For installation instructions, refer to "Chapter 2. Planning for and Installing Manager for R/3" in the Tivoli Manager for R/3 User’s Guide.

5. Configure the TEC event server. For more information, refer to "Chapter 2. Planning for and Installing Manager for R/3" in the Tivoli Manager for R/3 User’s Guide.

6. Optionally, if you plan to manage R/3 resources with Tivoli GEM, ensure that the Tivoli GEM server is configured and that the Tivoli GEM consoles are installed.

7. Optionally, if you want to extend Manager for R/3 database server status reporting, install Tivoli Manager for DB2 or Tivoli Manager for Oracle, as appropriate.

SummaryThe following steps outline the general installation procedure. For complete details about how to install Manager for R/3, refer to "Chapter 2. Planning for and Installing Manager for R/3" in the Tivoli Manager for R/3 User’s Guide.

The installation procedure you follow depends on whether you are installing Manager for R/3 for the first time, whether you have Manager for R/3 Version 1.5 or 1.5.1 installed, or whether you have Manager for R/3 Version 2.0 installed. Follow one of these procedures:


■ For a new installation, follow these steps:

1. Back up the Tivoli database.

2. Install Application Proxy Version 1.1 or upgrade to Application Proxy Version 1.1 if you have not already done so.

3. Install Application Proxy Patch 1.1-APX-0005.

4. Back up the Tivoli database, saving the backup file with a different file name than the previous backup file.

5. Install Tivoli Manager for R/3 Version 2.1.

6. Back up the Tivoli database, saving the backup file with a different file name than the previous backup file.

7. Optionally, if you want to manage R/3 resources with Tivoli GEM, install Tivoli GEM Instrumentation for Tivoli Manager for R/3 Version 2.1 as described in "Chapter 10. Tivoli GEM Instrumentation" in the Tivoli Manager for R/3 User’s Guide.

8. Back up the Tivoli database, saving the backup file with a different name than the previous backup file.

■ If you have Manager for R/3 Version 1.5 or Version 1.5.1 installed, the method you choose depends on whether you want to preserve Version 1.5 or Version 1.5.1 configuration data for managed nodes or whether you want to do a fresh installation.

To preserve Version 1.5 or Version 1.5.1 configuration data for managed nodes (RFC logon parameters, Alert Event Adapter parameters, and monitor profiles), follow these steps:






5. Install Manager for R/3 Version 2.0 and migrate configuration data as described in the Tivoli Manager for R/3 Release Notes for Version 2.0.


7. Upgrade to Version 2.1 as described in "Chapter 2. Planning for and Installing Manager for R/3" in the Tivoli Manager for R/3 User’s Guide, Version 2.1.

Note: For information specific to upgrading the Syslog Event Adapter, see “Considerations for Upgrading the Syslog Event Adapter” on page 18.


9. Optionally, if you want to use Tivoli GEM to manage R/3 resources, install Tivoli GEM Instrumentation for Tivoli Manager for R/3 Version 2.1 as described in "Chapter 10. Tivoli GEM Instrumentation" in the Tivoli Manager for R/3 User’s Guide.


To do a fresh installation of Version 2.1, follow these steps:


2. Uninstall Manager for R/3 Version 1.5 or Version 1.5.1 as described in the Tivoli Manager for R/3 Release Notes for Version 1.5.1.






7. Install Manager for R/3 Version 2.1.


9. Optionally, if you want to use Tivoli GEM to manage R/3 resources, install Tivoli GEM Instrumentation for Tivoli Manager for R/3 Version 2.1 as described in "Chapter 10. Tivoli GEM Instrumentation" in the Tivoli Manager for R/3 User’s Guide.


■ If you have Manager for R/3 Version 2.0 installed, follow these steps:



3. Upgrade to Version 2.1 as described in "Chapter 2. Planning for and Installing Manager for R/3" in the Tivoli Manager for R/3 User’s Guide, Version 2.1.

Note: For information specific to upgrading the Syslog Event Adapter, see “Considerations for Upgrading the Syslog Event Adapter” on page 18.


5. Optionally, if you want to use Tivoli GEM to manage R/3 resources, install or upgrade to Tivoli GEM Instrumentation for Tivoli Manager for R/3 Version 2.1 as described in "Chapter 10. Tivoli GEM Instrumentation" in the Tivoli Manager for R/3 User’s Guide.


Uninstalling Manager for R/3Manager for R/3 provides two scripts, R3Mgr_uninstall21.pl and create_uninstall_task.sh, that facilitate uninstalling Manager for R/3


Version 2.1. Refer to "Chapter 2. Planning for and Installing Manager for R/3" in the Tivoli Manager for R/3 User’s Guide for complete details.

Defects FixedThe following defects have been corrected in this release of Manager for R/3:

■ APAR IY07786. The automatic discovery function created App Server List profile managers without setting either database mode or dataless mode. This resulted in a failure when opening the R3 Server Monitors profile manager because the App Server List profile managers are subscribers to the R3 Server Monitors profile manager. The R3 App Server profile managers are now created in database mode.

■ APAR IY09698. Memory leaks in the Syslog Event Adapter.

■ APAR IY09976. Distributed Monitoring events with different event severities were treated as duplicate events in the SAP_SERVER_MONITORS event class. TEC rules were changed so that these events are not treated as duplicates.

■ APAR IY11511. The Syslog Event Adapter for R/3 release 4.x needs to report the client and transaction code.

■ APAR IY11633. Typographical error for the sub_origin variable in the sap_default.rls file.

■ APAR IY11641. Event filtering of Syslog events was not working properly on TEC 3.6.2.

■ APAR IY11719. The Syslog Event Adapter log file, r3slogIID.log, continues to grow until the file system is filled.

Known Product Defects, Limitations, and Workarounds

This section describes known defects in this release of Manager for R/3. Where applicable and known, suggested workarounds are identified. Note that this might not be a complete list of defects.


■ The r3mibIID daemon does not start automatically on UNIX reboot.

Workaround: Start r3mibIID manually.

■ The r3slogIID daemon does not start automatically on UNIX reboot.

Workaround: Start r3slogIID manually.

■ The r3idocIID daemon does not start automatically on UNIX reboot.

Workaround: Start r3idocIID manually.

■ Manager for R/3 does not support routing events to a single remote TEC event server from both managed nodes and TMA endpoints in interconnected TMRs.

Workaround: None. Refer to the Tivoli Manager for R/3 User’s Guide for information about supported configurations for multiple TMRs.

■ When using the automatic discovery function, the R/3 system policy region might not contain all R/3 application servers in the R/3 system.

Workaround: The automatic discovery function might be experiencing resource contention problems for an R3System object. Run automatic discovery again to discover the missing R/3 application servers.

■ Unable to deploy the message server status monitor because the message server is running on a machine without an R/3 application server.

Workaround: Use the desktop to create a virtual R3AppServer object pointing to the managed node or TMA endpoint that is running the message server. On the Create R/3 Application Server dialog, enter any two digits to represent the instance ID. Deploy the message server status monitor to this virtual R3AppServer object. After creating the virtual R3AppServer object, be sure to remove it from the appropriate App Server List profile manager.

■ When using Distributed Monitoring to generate TEC events, the warning response from a monitor does not generate a TEC event.


Workaround: Apply the following Distributed Monitoring patch:

3.6.1-DMN-0026

■ On Windows NT, when running the wr3exist executable, the entry point _lc_collate_cp could not be found.

Workaround: The named entry point is provided in the msvcrt.dll file in the \winnt\system32 directory. The entry point cannot be found because the version of the msvcrt.dll file is older than the version required by Manager for R/3.

To correct this problem, replace the \winnt\system32\msvcrt.dll file with a later version. To assist you, Manager for R/3 ships a later version of Microsoft’s msvcrt.dll file in the %BINDIR%\..\..\lib\w32-ix86 directory. This version provides the needed entry point and allows wr3exist to run.

■ When deleting multiple R/3 objects from an R/3 system policy region, not all objects are deleted or objects appear as black boxes.

Workaround: This problem occurs because the delete process does not correctly lock resources. Based on activity in the R/3 system, another process might refresh the R/3 system objects list while the delete process is still running.

The long-term solution to this problem is to apply a Tivoli Framework patch. The patch number was not available for inclusion in this Release Notes document prior to publication.

You might be able to workaround this problem. If your only symptom is that not all R/3 objects have been deleted, delete the objects again. If your symptom includes R/3 objects appearing as black boxes, call Tivoli Customer Support.

■ When using TEC event forwarding, duplicate FATAL and CRITICAL events are sent to the TEC event server to which you are forwarding events. The duplicate events occur because Manager for R/3 is using a rule in the sap_tecad.rls file to forward all of its TEC events, and TEC is also using a rule in the tecad_nv390fwd.rls file to forward all FATAL and CRITICAL events. Both rules are in effect, causing duplicate events to be forwarded.

Workaround: None.


■ TEC events for the saposcol monitor have inconsistent values in the hostname event slot. The monitor is distributed to an R3AppServer object. If the R3AppServer object is based on a managed node, the hostname event slot contains the R/3 application server triplet name. If the R3AppServer is based on a TMA endpoint, the hostname event slot contains the TCP/IP host name.

Workaround: None. APAR IY11845 has been opened against Tivoli Distributed Monitoring to address this problem.

■ When running the Display OS/390 Information task or when running monitors from the OS/390 monitoring source on an R/3 4.5B system, errors are reported indicating that the database logical destination could not be established.

Workaround: Apply the ABAP fix that is described in SAP OSS note 164660.

■ When using the IDOC Event Adapter in a Japanese environment, the SAP_IDOC_STATUS event msg slot does not correctly show Japanese characters.

Workaround: Japanese language support is fully enabled for the Syslog Event Adapter only. The IDOC Event Adapter attempts to report information in Japanese because the RFC logon parameters were configured for Japanese. To set the language used by the IDOC Event Adapter back to English, edit the r3idocIID.conf file, changing the ABH_Language value from J to E. The r3idocIID.conf file is located in one of the following directories:

• Managed node: $BINDIR/TME/SAP/2.2C

• TMA endpoint: $LCF_BINDIR/../TME/SAP/2.2C

After editing the r3idocIID.conf file, stop and start the appropriate IDOC Event Adapter to incorporate the change.

■ When running Manager for R/3 and Manager for MQSeries in an AS/400 environment, Manager for MQSeries tasks run against an AS/400 TMA endpoint fail.

Even though Manager for R/3 does not support the AS/400 operating system, you might have installed both Manager for R/3 and Manager for MQSeries in your environment. Manager for R/3


uses the dependency set feature of gateways to install files that Manager for R/3 requires on TMA endpoints. The method by which this is done forces the dependency files to be installed on a TMA endpoint, even an AS/400 TMA endpoint, whenever any task is run against that TMA endpoint. However, one of the files in the Manager for R/3 dependency set is incompatible with AS/400 file naming conventions. This file naming incompatibility causes installation of the dependency set files from the gateways to the AS/400 TMA endpoints to fail, resulting in Manager for MQSeries tasks failing on AS/400 TMA endpoints.

Workaround: Remove the Manager for R/3 dependency set from gateways that manage AS/400 TMA endpoints. To do this, run the following sequence of commands on the appropriate gateways. The first command removes the Manager for R/3 dependency set from the gateway. The second command ensures that the gateway is not still running the Manager for R/3 dependency set.

wdepset -e @DependencyMgr:sap_run_task_dep \-r depset @DependencyMgr:sap_tool_dep

wgateway gateway_name dbcheck

Note: Removing the Manager for R/3 dependency set from a gateway will result in the inability to run the Manager for R/3 automatic discovery function on TMA endpoints managed by that gateway.

Product NotesThis section contains important information that you should consider when using Manager for R/3.

R/3 TransportsThe Tivoli Manager for R/3 User’s Guide provides instructions for installing ABAP programs into an R/3 landscape using an R/3 transport. The transport files used in Manager for R/3 Version 2.1 are as follows:


Considerations for Upgrading the Syslog Event Adapter

When upgrading Manager for R/3 from Version 2.0 to 2.1, the following steps are required to upgrade the Syslog Event Adapter:

■ Upgrade the Syslog Event Adapter executable.

The Syslog Event Adapter executable is upgraded when you install the Tivoli Manager for R/3 Version 2.1 (Upgrade from Version 2.0) patch.

■ Upgrade the ABAPs.

To upgrade the ABAPs, you must load the new transport files.

Different results can occur based on the order in which you perform these steps. If you upgrade the ABAPs first, the Version 2.0 Syslog Event Adapter attempts to run with the new ABAPs. However, the Version 2.0 Syslog Event Adapter is not compatible with the Version 2.1 ABAPs. The Version 2.0 Syslog Event Adapter will produce errors, which might result in unconstrained log file growth, causing the /tmp file system to fill up.

If you upgrade the Syslog Event Adapter executable first, the Version 2.1 Syslog Event Adapter runs with the Version 2.0 ABAPs. The Version 2.1 Syslog Event Adapter detects that is it incompatible with the Version 2.0 ABAPs and logs an error. The Version 2.1 Syslog Event Adapter will continue to run, but it will not successfully report Syslog messages until the Version 2.1 ABAPs are loaded.

It is highly recommended when upgrading Manager for R/3 from Version 2.0 to Version 2.1 that you stop all Syslog Event Adapters,

Transport Data File Cofiles File

Base TV1R000169 TV1K000169

OS/390 Extension (This transport must be installed after the base transport.)

TV1R000114 TV1K000114


upgrade the ABAPs, then upgrade the Syslog Event Adapter (install the upgrade patch) before restarting the Syslog Event Adapters.

Accessing Product DocumentationIn addition to the printed documents you receive with the product, the CD contains a README file and the Tivoli Manager for R/3 User’s Guide in hypertext markup language format (.htm) and portable document format (.pdf). The .htm and .pdf files (sa21ug.htm and sa21ug.pdf) for the User’s Guide are contained in the /DOC directory.

View the sa21ug.htm file using your default Web browser. View or print the sa21ug.pdf file using the Adobe Acrobat Reader.

Notes:

• If you do not have Adobe Acrobat Reader, you can obtain it free by clicking the Get Acrobat Reader icon at the Adobe Web site, http://www.adobe.com, and following the steps that are provided.

• The Tivoli Manager for R/3 User’s Guide and the Tivoli Manager for R/3 Release Notes are also available in .htm and .pdf format at the following location on the Tivoli Web site: http://www.tivoli.com/support/documents/.

You need a user ID and password to access this Web site. To obtain an ID for use on the support Web site, go to http://www.tivoli.com/support/getting/.