Data Collector Suite for SAP - SAP Beratung | IT ... · PDF fileclassic core applications such as FI/CO, SD, and HR, mySAP ERP comprises APO (Advanced Planner and Optimizer), BW (Business

Data Collector Suitefor SAP

Status: November 14th, 2008

Copyright © REALTECH 2008 Page 2 of 25

theGuard! ApplicationManager – Data Collector Suite for SAP

Contents

Contents ........................................................................................................................................................... 2Introduction ....................................................................................................................................................... 3Overview of SAP R/3, mySAP ERP, and SAP NetWeaver ................................................................................. 4

SAP R/3, SAP R/3 Enterprise, and Web Application Server ........................................................................... 5The ApplicationManager Data Collector Suite for SAP....................................................................................... 7The SAP Data Collector Family ......................................................................................................................... 9

Features of the SAP Data Collector Suite..................................................................................................... 11General Information Model ....................................................................................................................... 11Monitoring the Object Status..................................................................................................................... 12Monitoring and Analyzing SAP Transactions and User Activity.................................................................. 13Managing Processes ................................................................................................................................ 14Managing Buffers ..................................................................................................................................... 14Managing Jobs......................................................................................................................................... 14Monitoring IDOCs and RFCs .................................................................................................................... 14Monitoring Spools..................................................................................................................................... 14Monitoring and Analyzing User and Security Aspects................................................................................ 15Monitoring Shortdumps ............................................................................................................................ 16Monitoring Updates .................................................................................................................................. 16Monitoring Enqueue ................................................................................................................................. 16Monitoring ICM (Internet Communication Manager) .................................................................................. 17Monitoring SLD (System Landscape Directory)......................................................................................... 17Intelligent Suppression of Events.............................................................................................................. 18Monitoring Specific Services for mySAP Architectures.............................................................................. 19Monitoring Specific Services for new SAP NetWeaver Components.......................................................... 19Monitoring GRMG (available with SAP R/3 Enterprise DC) ....................................................................... 19Monitoring the MI (available with SAP R/3 Enterprise DC) ........................................................................ 19Monitoring the CTS (available with SAP R/3 Enterprise DC) ..................................................................... 20Monitoring SAP ITS.................................................................................................................................. 20Monitoring the System Logs ..................................................................................................................... 21Monitoring Work Processes ...................................................................................................................... 22Sending SAP System Messages .............................................................................................................. 22Displaying SAP Profile Parameters........................................................................................................... 23Administration of the ABAP-Suite and storage of its settings..................................................................... 23Viewing and Analyzing SAP System Performance .................................................................................... 24Preconfigured Monitoring Policies............................................................................................................. 24

Compatibility and General Availability .............................................................................................................. 25



Introduction

There's more to efficient application management than maximizing availability. Targeted tuning can increase theperformance and stability of business-critical applications without having to invest in additional hardware(processors, RAM, and disk space).

A number of data collectors have been developed for theGuard! ApplicationManager that providecomprehensive monitoring and generate detailed data analyses. Data collectors do more than simply collectevents according to pre-defined rules. They deliver every performance value and the current status of eachapplication object in real time. They also provide insight into configuration attributes, such as the release statusor the application's parameter settings. Data collectors model an application in objects and sub-objects, enablinga dedicated handling of alerts, monitoring, reporting, service level management, or status messages. This modelensures that information is clearly structured and that messages are easy to allocate to a problem.

Central reporting at the application instance and application object level provides for a detailed and effectivecapacity management of all resources.

Integrated Service Level Management ensures that the service levels for application availability andperformance are achieved, while Operational Level Agreements (OLAs) can be easily defined at the applicationobject level.

REALTECH has been managing SAP systems for years. Our consultants and developers not only understandtechnologies, they also have in-depth knowledge of the SAP architecture, and running and optimizing SAPsystems.

is a worldwide SAP software, technology, andsupport partner.



Overview of SAP R/3, mySAP ERP, and SAP NetWeaver

In most companies, the SAP R/3 systems running business-critical applications are very important. One of theirmain tasks is to securely process thousands of user requests in near real time. Business-critical data such asopen receivables is always consistently organized in the SAP R/3 database. The SAP landscape's high level ofscalability keeps response times to a minimum even when the system load is high.

mySAP ERP is a software solution that fully maps and supports a company's business processes. In addition toclassic core applications such as FI/CO, SD, and HR, mySAP ERP comprises APO (Advanced Planner andOptimizer), BW (Business Warehouse), and CRM (Customer Relationship Management). Business processesare extended across company boundaries with SAP EP (Enterprise Portal) and SAP XI (ExchangeInfrastructure).

Companies are aware of the benefits of software-supported business processes. The demands on the ITinfrastructure in terms of software-component availability and the front- and back-end performance of the criticalcompany data are raised to a new level of importance. This also raises the demands on application and systemmanagement. Simply reporting a failure is often not enough. To minimize downtime, proactive monitoring of thecritical transactions and system parameters is required so that incidents can be recognized in a timely mannerand possible failures prevented. Service providers running SAP systems for their customers require a fine-tunedsystem administration, detailed and controllable SLAs, and the ability to measure efforts for subsequent activityallocation.



SAP R/3, SAP R/3 Enterprise, and Web Application Server

SAP R/3 Web Application Server (until SAP R/3 4.6 also known as SAP Basis) is the technological basis for avariety of SAP business solutions. In addition to the classic SAP Application Server, as of SAP 6.30, the WebApplication Server is equipped with a J2EE server and is a key component of the SAP NetWeaver technology.An SAP system must have at least one central instance and a database, and can be scaled by adding moreapplication servers.

A classic R/3 system is based on a three-tier client-server architecture. The central instance plays a special rolefor the application servers. It is responsible for the system-wide services, such as the enqueue and messageservices.

The message service provides the communication between an R/3 system's instances. It controls and assignsfree process resources on demand at the application level. For example, SAP GUI consoles that log in to thesystem through the message service are connected to the application server with the least load (loadbalancing). This is done to ensure optimal resource usage across the system and guarantee response times ofless than a second.

The enqueue service places logical locks on database tables for as long as it takes to complete a businesstransaction. This locking mechanism is essential to ensuring the consistency of business-critical data.



The following services are available at the application level of an R/3 system (based on the configuration ofeach application sever):

Dialog Service (Dialog) (D)

Updates (V)

Locking Management (Enqueue) (E)

Background Processing (Batch) (B)

Message Server (M)

Gateway (G)

Spool Service (Output) (S)

These services are performed by the work processes. They are coordinated by the dispatcher process, of whichthere is exactly one for each instance. The dispatcher starts and manages these processes. When a dispatchergoes down, the whole instance goes down.

The dispatcher works at the interface between the presentation and the application layer. All of the requests thatare received from the presentation layer, meaning from the SAP GUI, are received by the dispatcher andassigned to a work process that is available for this instance.

For more information, refer to the SAP Portal help http://help.sap.com/.

http://sap.com/



The ApplicationManager Data Collector Suite for SAP

The SAP data collector enables SAP applications and systems to be managed automatically from a centrallocation. With ApplicationManager, a number of central instances and/or application servers (hereafter referredto as SAP instance) can be managed and analyzed in parallel.

The monitoring functions comprise the general SAP status, users, processes, buffers, locks, jobs, transactions,and connections to other systems. They can be run from a common console. Starting with an overview, detailscan be added as needed to analyze a problem. This "single point of view" gives system administrators acomprehensive tool that provides them with a constant view of the entire system, enabling them to guarantee itsoperability and optimize it using the detailed analyses.

The SAP data collector suite is a very powerful application that consists of two basic components: the SAP DataCollector and the ABAP-Suite.



The data collector suite follows two approaches:

Outside-In Approach: The SAP data collector monitors and examines the system from the outside.

Inside-Out Approach: The ABAP/4 suite analyzes internal processes and reports them to the outside.

The SAP data collector is an operating system component that continuously controls the operability of the SAPinstances and/or the underlying databases from the outside (outside-in approach). This is key to guaranteeingthe high-availability of business-critical applications. SAP's own CCMS monitoring is, of course, monitored bydefault. The data collector reads the application server's SAP monitoring infrastructure through the officialinterface. This solution is robust, stable, and optimally scaled.

The ABAP/4 suite, a component that runs inside the SAP system (inside-out approach), goes beyond the SAPstandard internal process and status monitoring function. This additional information is sent to the SAPmonitoring infrastructure where it can be viewed (optionally) with the SAP GUI or the Solution Manager. Thishigh level of configurability also enables customer-specific and problem-oriented monitoring.

The data collector suite guarantees availability and performance, and enables you to perform analyses foractivity allocation and capacity planning by user group, transaction group, and job group with full clientoperability.

Manual checks like those requested by the official SAP-System-Administration-Assistant can be automatedusing theGuard! ApplicationManager. This guarantees quick return on investment and high security.



The SAP Data Collector Family

A variety of SAP products and versions are in use. To support all of the versions, REALTECH offers a range ofdata collectors that are tailored to the special features of each component. The standard data collectors are:

SAP R/3 3.1 DC

SAP R/3 4.0 DC

SAP R/3 4.5 DC

SAP R/3 4.6 DC

SAP R/3 Enterprise DC

The latter covers the SAP Web Application Server up to SAP 7.10 and R/3 Enterprise 4.7.

There are special data collectors for APO, BW, and CRM systems that monitor a number of other features inaddition to the standard features. The following special data collectors based on SAP Basis 4.6 are available:

SAP APO DC

SAP BW DC

SAP CRM DC

SAP R/3 Enterprise DC

Since SAP Web Application Server 6.10, the monitoring of these systems is integrated in the SAP R/3Enterprise data collector.

The following data collectors are available to monitor SAP systems (application servers on UNIX or Windows)with an underlying DB2 database on OS/390:

SAP R/3 4.6 (DB2) DC

SAP R/3 Enterprise (DB2) DC

Applications and Technologies like SAP XI / PI und SAP Web Application Server for Java (e.g. the basis forSAP Enterprise Portal) can be monitored using the following data collectors:

SAP XI DC (ABAP-Suite transport)

SAP Web AS DC

The collectors are described in detail in individual documents.



Finally, a special range of data collectors is available to monitor SAP systems running on an AS/400. Thesedata collectors are installed on Windows platforms and monitor the SAP system remotely using RFC:

SAP R/3 4.0 (DB400) DC

SAP R/3 4.5 (DB400) DC

SAP R/3 4.6 (DB400) DC

SAP R/3 Enterprise (DB400) DC

Each of these data collectors can monitor a multitude of different SAP instances. This requires only onecorrectly installed ABAP-Suite.

The SAP ITS is monitored by its own SAP ITS data collector.

SAP Enterprise Portal and SAP XI are currently supported by a combination of operating system data collectorsand file parsers. Specific data collectors for the J2EE server are in development.

There are data collectors for all of the operating systems supported by SAP (UNIX, Linux, Windows, andAS/400). You can find the latest information about platform support at www.realtech.com.

http://www.realtech.com/


Features of the SAP Data Collector Suite

The following are examples of the possibilities that theGuard! ApplicationManager offers in terms of SAP systemmanagement. The list is by no means exhaustive. Do not hesitate to contact us if you would like to know moreabout monitoring your IT landscape or have other questions you would like to discuss. You can find our contactdetails on the last page of this document.

General Information Model

All of the components and architectural features of an R/3 instance and its attributes or categories are gatheredand analyzed within the framework of the CIM model (Common Information Model) as managed objects (MOs).This structures the information and enables the policies and reactions to be controlled individually.

The right screen displays exemplary eventsof an SAP R/3 Enterprise data collector.Several of these may require the systemadministrator's immediate attention. Theclear structure of the information enableserrors to be quickly recognized.

Properties provide a quick andcomprehensive overview of the mostimportant system properties of all of theconnected SAP systems. Here you can viewimportant information about the system,such as the version and patch level of thedifferent software components, theunderlying database, or the values ofindividual profile parameters. Runtimeinformation, such as the list of logged inusers, is also viewed here.




Monitoring the Object Status

The below figure displays the status of a few objects underneath an SAP Enterprise data collector in theManaged Monitor of theGuard!! ApplicationManager (a complete list of objects can be found in Appendix A). Acomprehensive overview of the system status is immediately visible, starting with the status of the SAPinstance’s health.

In this example, the SAP R/3 instance R21_02 is OK, but there is a problem with the performance objects inclient R21_22. A job may not have been run as scheduled. The R/3 system administrator can tackle the specificproblem without having to analyze it first.


Monitoring and Analyzing SAP Transactions and User Activity

During the day, SAP users work in parallel to similar dialog transactions. Their performance is one of the keycriteria when it comes to evaluating the performance of an SAP system.

In the ABAP-Suite component “Performance data collector”, SAP transactions and jobs that can be bundled ingroups as performance objects, and their performance attributes can monitored and analyzed. Similarly, all useractivities, Task types, IP ranges and report names can be monitored and analyzed.

SAP client-specific and client-spanning data can be defined for each SAP client. Because a system canhave a number of different clients and hence different user groups, the service "SAP" can be analyzed in thesame way.

The information can be analyzeactivities or show that the SLA


d by Reporting or by comparing it to defined service levels, and used to allocates were achieved.



Managing Processes

The different process types (dialog, batch, spool, etc.) can be constantly monitored and analyzed using differentattributes such as load, CPU usage, etc.

This enables you to distribute the processes optimally across the hardware resources.

Managing Buffers

The different buffer types (CUA, program, and table) can be constantly monitored and analyzed using a varietyof attributes such as load, hit ratio, etc.

This enables you to configure the buffers for the best throughput.

Managing Jobs

The SAP data collector's job management function provides an overview of your total production workload fromone point. This function enables you to monitor the status of each job for a number of attributes.

Job-Monitoring can be configured client-specific inside the ABAP-Suite.

Similar to transaction groups, jobs can be collected into groups and their performance monitored and analyzed.You can distribute jobs optimally and ensure they are smoothly processed.

Monitoring IDOCs and RFCs

Intermediate Document (IDOC) is a standard data structure that enables data to be exchanged electronicallywithin SAP systems or between SAP systems and third-party systems. The IDOCs' process levels can bemonitored with theGuard! ApplicationManager and selection criteria for specific IDOCs saved. RFC connectionsto other systems can be checked regularly. In addition to the classic Remote Function Call (RFC), there are newvariants (tRFC = transactional RFC, qRFC = queued RFC) that can be monitored separately. This guaranteesthat data exchanges between SAP and other applications flow smoothly.

Monitoring Spools

All of a system's spool jobs can be monitored on all clients. Specific monitoring thresholds can be defined. It isalso possible to monitor a specific printer.



Monitoring and Analyzing User and Security Aspects

There are a number of ways to monitor SAP R/3 system users. The number of logged in users is displayedaccording to a number of criteria:

System-wide/Instance-specific logged in users across clientsas well as for specific SAP-clients.

Users that belong to specific payroll numbers.

Concurrent users.

Users added to the system.

In combination with theGuard! Reporting, you can monitor and analyze the system over a longer period of time.The below example of a report shows that there were never more than six concurrent users logged in to thesystem, which in this case means that no more than six client licenses were needed at the same time.

Different user aspects were also monitored, for example, if critical users were logged in to the system or if userswere still logging in with their initial password. Other aspects that were reported were user log-ins and log -outs,incorrect log in attempts, or users that had not successfully logged in for a while.

Checks can be adjusted in a flexible way so that you can exclude certain SAP clients from the critical usercheck.

This makes managing and optimizing users and licenses much easier.



Monitoring Shortdumps

The collector can monitor the number of ABAP short dumps that occurred in the system. A parameter can be setto determine the number of short dumps that can trigger an alarm. In addition to the standard attributes, themessages also contain the name of the report that belongs to the short dump. Shortdumps are requestedindividually for each database and application server.

Shortdump-Monitoring can be configured client-specific inside the ABAP-Suite.

The collection rate can be adjusted in a flexible way so that all short dumps within a collection interval can beevaluated.

Monitoring Updates

This option checks if the system's update processes have been started. There are three statuses:

Update in progress.

Update deactivated by the system.

Update deactivated by a user.

The system also checks for unprocessed update records. These can be unprocessed update records (initial) orfaulty update records.

Update-Monitoring can be configured client-specific inside the ABAP-Suite.

Moreover, the update error messages include the user name who has initiated the update.

Monitoring Enqueue

Among other things, the system monitors if lock entries are held too long, and/or how many entries there are.This monitoring is carried out across all clients.



Monitoring ICM (Internet Communication Manager)

The ICM (Internet Communication Manager) is an essential part of the new SAP Web Application Server (SAPWAS). It is negotiating ABAP and Java Requests from the Inter-/Intranet. Any failure of the ICM impacts thewhole system immediately.The SAP R/3 Enterprise data collector monitors the Internet Communication Manager (ICM) for:

ICM Core availability

State of ICM Server Threads

State of ICM Servers (HTTP, SMTP, HTTPS, …)

Monitoring SLD (System Landscape Directory)

Today, many SAP systems depend heavily from the central SAP system landscape directory called SAP SLD.As an example, SAP XI routing information is based on information of the SLD. Thus, the SAP R/3 Enterprisedata collector monitors the availability of the System Landscape Directory (SLD) and the LandscapeComponent Repository (LCR) in various respects.

Existence and Accessibility

Type of RFC destination SAPSLDAPI

Name / Address of SLD

Existence of Business Systems in SLD

Availability of Business Systems attached to the central system



Intelligent Suppression of Events

SAP Systems often create floods of event messages though there is just a single root-cause. This makes itnecessary to reduce messages for system optimization.The ABAP-Suite therefore lets you suppress similar events automatically at the source with a definable filter.You can configure the suppression easily by:

Changed message text

Changed severity

The comparison and filtering is done inside the SAP system at source level.Benefits: Fewer alarms, better overview, less network traffic and still a reliable system catching allimportant messages!

Even more, since version 3.0 theGuard! ApplicationManager provides an intelligent and configurable eventsuppression for all application types (SAP, Oracle, Web, Mail, Operating systems) using extended policies.Such, savings of additional 30% of IT operation costs can be achieved easily.



Monitoring Specific Services for mySAP Architectures

APO, BW, and CRM are based on the R/3 architecture and the classic SAP application server. The suite of datacollectors for these architectures comprises all of the above-mentioned checks and analyses, as well asadditional services, such as LiveCache for SAP APO or load processes for SAP BW. The features are describedin each of the data collectors' documents.

SAP CRM and SAP Enterprise module components, such as TREX (Text Retrieval and Information Extraction)or IPC (Internet Pricing Configurator), run outside of the classic architecture. Use the suite to monitor yourspecial RFC connections, and operating system data collectors to monitor processes and services.

Monitoring Specific Services for new SAP NetWeaver Components

SAP Enterprise Portal (EP) and SAP XI are fully based on the new SAP Web Application Server (SAP WAS).While SAP EP is using the J2EE Server of the SAP WAS exclusively, SAP XI is using both servers (ABAP andJ2EE).

Process, Service and Log file monitoring are described in each of the following data collector documents. Thenew data collectors are named:

SAP Web AS DC for the J2EE part of the SAP Web Application Server

SAP XI DC for the SAP Exchange Infrastructure (SAP XI)

SAP NetWeaver applications are strongly linked to other SAP systems. That's why it is recommended tocombine the SAP data collector suite with theGuard! NetworkManager. In addition, the ability to graphicallydisplay such interconnected systems and their information can be particularly useful when monitoring availabilityand performance, and carrying out analyses. This is done using theGuard! ServiceCenter's business maps. Thisenables you to achieve a perfect business service management for all of the applications on the SAPNetWeaver stack.

Monitoring GRMG (available with SAP R/3 Enterprise DC)

GRMG (Generic Request and Message Generator) is a new service for probing systems and applications from acentral system.User, who configure and activate this service, can process all connections (e.g. to a particular XI Adaptor) as a“Managed Objects” inside theGuard! ApplicationManager. States and Events are clearly shown and Messagesare processed as usual.

Monitoring the MI (available with SAP R/3 Enterprise DC)

The MI (Mobile Infrastructure) is a technology solution of SAP NetWeaver. The SAP MI runs locally on a mobiledevice and synchronizes with the data stock of SAP NetWeaver.The monitoring contains the Worklist Monitor that displays the synchronization messages. In case of errormessages ApplicationManager can create red and yellow alert messages.



Monitoring the CTS (available with SAP R/3 Enterprise DC)

The CTS (Change and Transport System) provides tools for transporting changes between SAP systems andtheir clients within the system landscape.The monitoring includes status changes of CTS objects in ApplicationManager, as well as messages of the CTSin the following categories:

Transports

Transport environment

Configuration

Communication

Authorizations

Workflow

Quality Assurance

Miscellaneous

Monitoring SAP ITS

SAP ITS (Internet Transaction Server) is a special, scalable Web server that enables SAP systems to beaccessed through a Web browser. It is modular and built in the form of an A and W gate.

In terms of monitoring, the SAP ITS data collector provides insight into a number of the components' settings:

Connection data

Security settings

Number of allowed instances

Number of allowed sessions

Memory requirements

Template caching

Worker threads

Flow logic production mode

The following services and attributes, among others, are monitored:

Available sessions

Active instances

Number of requests

The features of SAP ITS monitoring are described in a separate document.



Monitoring the System Logs

Client-specific and system-wide monitoring of entries in:

Syslog (SM21)

Auditlog (SM20)

The following data is reported by ApplicationManager events for every entry in one of the logs:

Occurrence (number of log entries that have been combined to a single event)

Message text (message of the log entry)

Date

Time

WP Type (work process type)

WP Number (work process number)

Client

User

Terminal (terminal in which the user is logged in)

TCode (transaction code)

Report (program name)

Message number (contains of “Syslog message group“ and “Sub-name“)

Problem class

Development class (packet)

Syslog message group (message group)

Sub-name

Audit class (not applicable to Syslog)

Audit severity level (not applicable to Syslog)

RFC Destination (RFC destination of the used Application Server)

Multiple log entries of one criterion, occurring within a poll cycle, are combined to a single message by the datacollector!



Monitoring Work Processes

The „Workprozess Monitor“, based on SM50 allows for a comprehensive monitoring of the work processesrunning in your system. The monitoring is realized with a rule set that can be freely defined. The followingparameters can be used as filter criterions to define the rule set:

Number/Unit of work processes that have to match the monitoring criterion

Workprozess Type that has to be monitored:o Backgroundo Dialogo Enqueueo Spoolo Update

Monitoring criterion:o Elapsed Time (sec)o CPU usage (%)o Average CPU usage (%)o Overall CPU usage (%)o Number of Dumpso Average number of Dumpso Overall number of Dumpso Number of Processeso Number of Processes (%)

For every rule you can define a severity, an optional message text, as well as a period in which this rule has tobe matched to start event generation. You can group the rules and combine them with each other.

Sending SAP System Messages

SAP system messages are short messages that are sent to an SAP GUI user. This function is virtually the sameas Netsend.

With a simple click of the mouse, system administrators can send system messages from theApplicationManager GUI to users that are logged in to the SAP system without having to log in themselves.System messages can also be used as a reaction to certain incidents, such as events or thresholds that havebeen exceeded. This enables you to inform SAP users automatically and in a timely manner about seriousmalfunctions, thus preventing programs and updates from aborting.



Displaying SAP Profile Parameters

Profile parameters define the behavior of an SAP system. To fine-tune system performance, the parameters areset to ensure that system resources are used optimally. Incorrectly set values can cause erratic system behavioror create performance bottlenecks.

Administration of the ABAP-Suite and storage of its settings

The additional software “ABAP-Suite Configuration and Distribution Assistant“ (CDA), that is free of charge,allows for a central administration of the ABAP-Suites. You can update ABAP-Suites and backup ABAP-Suitesettings from a central point of control. Moreover, you can transfer ABAP-Suite settings from one system toanother, helping you to consolidate the ABAP-Suite monitoring landscape.

For system administrators, it is importantto know how certain parameters are setfor a specific instance. This informationcan be easily accessed from thetheGuard! ApplicationManager's GUI bymouse-click. Parameter values can becompared and analyzed betweensystems.



Viewing and Analyzing SAP System Performance

The theGuard! ApplicationManager's performance monitor can be used to monitor and compare the responsetimes of different SAP application servers in real time. The same applies to collected data, such as users, bufferhit rates, and other performance data.

This provides a quick overview of the performance of each of the systems in the landscape. Bottlenecks arequickly recognized.

With Application Launcher, you can start the SAP GUI for the appropriate R/3 instance from theGuard!ApplicationManager and, for example, go straight to transaction ST03 to analyze the performance bottleneckmore closely.

The information can be analyzed by Reporting or by comparing it to defined service levels, and used to allocateactivities or show that the SLAs were achieved.

Preconfigured Monitoring Policies

All of the SAP data collectors have many comprehensive preconfigured policies, including thresholds, fordifferent object types, such as instance or client. Customer-specific or modified policies are also easy to migrateto other data collectors in the SAP data collector family.



Compatibility and General Availability

The SAP data collectors are available on a variety of operating system platforms as described in the officialplatform matrix.

The ABAP-Suite has a different release cycle and is downward compatible with the data collector release. Thus,you can use the youngest ABAP-Suite version without changing the data collector release.

For more information aboutREALTECH’s software solutions:

www.realtech.com

REALTECH AGIndustriestr. 39c

69190 Walldorf GermanyTel +49.6227.837.591Fax +49.6227.837.837

mailto:[email protected]://www.realtech.com

http://www.realtech.de/

mailto:[email protected]

http://www.realtech.it/

Documents

Data Collector Suite for SAP - SAP Beratung | IT ... · PDF fileclassic core applications such as FI/CO, SD, and HR, mySAP ERP comprises APO (Advanced Planner and Optimizer), BW (Business