theguard! ApplicationManager System AIX Data Collector

Transcription

1 theguard! ApplicationManager System AIX Data Collector Status: 1/30/2008

2 Table of Contents Introduction...4 The Performance Features of the ApplicationManager Data Collector for UNIX...5 Overview of the UNIX Operating System...6 Special Features of the AIX 5L Operating System with Virtualization...9 The System AIX Data Collector...11 Using the System AIX DC to Monitor Hardware and Software Resources...12 Monitoring and Information about the Hardware (Host)...13 Monitoring and Information about the Partitions' Hard Disk (Disk)...14 Monitoring the Errorlog...15 Monitoring and Information about the Partitions' Memory (Memory)...16 Monitoring and Information about the Partitions' Processors (Processor)...17 Information about a Partition's Operating System (OS)...18 Monitoring and Information about File Systems (FileSystemGroups)...20 Monitoring and Information about Application Processes (Process Groups)...22 Monitoring and Information about Individual Swap Space Units...23 Monitoring and Information about Individual Virtual Processors...23 Monitoring and Information about Logical Volume Groups...24 Monitoring and Information about Logical Disks (Logical Volumes)...25 Standard Reporting and Service Level Analysis...26 Application Processes and Business Systems...26 Case Study of a Monitored System...27 Availability and Platforms...31 Table of Figures Figure 1: Multi-user and Multiprocess System (schematic)... 6 Figure 2: General Structure of UNIX... 7 Figure 3: DC tree (overview) Figure 4: Current usage in percent of all of the virtual processors' system resources Figure 5: Properties of the Host object displayed in ApplicationManager's Managed Monitor Figure 6: Properties of the Disk object displayed in ApplicationManager's Managed Monitor Figure 7: Error messages of the AIX Errorlog in ApplicationManager Figure 8: Properties of the Memory object displayed in ApplicationManager's Managed Monitor Figure 9: Properties of the Processor object displayed in ApplicationManager's Managed Monitor Figure 10: Properties of the OS object displayed in ApplicationManager's Managed Monitor Figure 11: Properties of the Process List object displayed in ApplicationManager's Managed Monitor Figure 12: Properties of the User Group List object displayed in ApplicationManager's Managed Monitor Figure 13: Properties of the User List object displayed in ApplicationManager's Managed Monitor Figure 14: User-defined FileSystem groups Figure 15: Definition of FileSystem groups through selection Figure 16: Definition of FileSystem groups through patterns (regular expressions) Figure 17: User-defined FileSystem groups Figure 18: Application process groups; TOTAL for all processes. Process groups such as SAP, Siebel, Oracle, etc., can be freely defined Figure 19: Property of the system's Swap Space displayed in the ApplicationManagers' Managed Monitor Figure 20: Properties of the Logical Volume object displayed in ApplicationManager's Managed Monitor Figure 21: Properties of the Volume Group object displayed in ApplicationManager's Managed Monitor Figure 22: Properties of the Logical Volume object displayed in ApplicationManager's Managed Monitor Figure 23: Performance Monitor - All processors are idle Figure 24: Performance Monitor Starting the "load" test tool Copyright REALTECH 2008 Page 2 of 31

3 Figure 25: Example of the Event Browser for process group events for dynamic processes Figure 26: Performance Monitor of processes, using the "load" test tool example Figure 27: Performance Monitor - Overview of all usage information of the test tool run Copyright REALTECH 2008 Page 3 of 31

4 Introduction There's more to efficient application management than maximizing availability. Targeted tuning can increase the performance and stability of business-critical applications without having to invest in additional hardware (processors, RAM, disk space). A number of data collectors have been developed for theguard! ApplicationManager that provide comprehensive monitoring and generate detailed data analyses. Data collectors do more than simply collect events according to pre-defined rules. They deliver every performance value and the current status of each application object in real time. They also provide insight into configuration attributes, such as the release status or the application's parameter settings. Data collectors model an application in objects and sub-objects, enabling a dedicated handling of alerts, monitoring, or status messages. This model ensures that information is clearly structured and that messages are easy to allocate to a problem. Pre-defined and reusable policies for each type of application facilitate the implementation of the solution and the adaptation of monitoring to dynamic landscapes. The ease with which thresholds are set ensures the early recognition of potential errors. Comprehensive reaction management enables flexible alerting for more than 100 different devices and alarm consoles. The automatic discovery of new application instances and objects, including the automatic allocation of policies, enables automatic monitoring even in those cases in which system administrators have completely reconfigured the application, for example, by adding new instances or objects. Central reporting at the application instance and application object level provides for a detailed and effective capacity management of all resources. Integrated Service Level Management ensures that the service levels for application availability and performance are achieved, while Operational Level Agreements (OLAs) can be easily defined at the application object level. Copyright REALTECH 2008 Page 4 of 31

5 The Performance Features of the ApplicationManager Data Collector for UNIX The operating system, its components and their reliability, availability, and usability, in short the system's overall "availability," is the basis of a properly functioning server. Companies generally run their business-critical applications on one or more servers. These servers must function properly to ensure the availability of the applications. Technical problems result in failures. Defects or insufficient system resources, such as a faulty CPU and or faulty hard drives, insufficient swap space etc., result in processing bottlenecks. Failures and/or bottlenecks can render applications unmanageable and incur high costs. The operating system data collector hereafter referred to as OS DC for UNIX operating systems enables a comprehensive monitoring of a live server running a UNIX operating system. With the OS DC, a number of operating system parameters, such as processes and process groups, running on a server can be monitored in parallel and compared to each other. All of a server's important hardware and software resources, such as, processors, memory, virtual memory, file systems, processes, etc. are defined and analyzed individually 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. With ApplicationManager's event and threshold monitoring resource, bottlenecks and system overloads can be detected and reported at an early stage. Together with two other data collectors, File Parser DC: Custom DC: Configuration file and security-related system file management User-defined system object monitoring OS DC provides the best security for your system. Administrators and/or other authorized users can access a machine by simply clicking on the managed node. The Application Launcher function, which is integrated in the interface, enables the context-based configuration of a detail analysis application, in this case a Telnet session. The OS DC is a powerful application that consists of a number of objects, event categories and performance counters. All of the information is described in the data collector's online documentation. This document provides an overview of the most important functions. Copyright REALTECH 2008 Page 5 of 31

6 Overview of the UNIX Operating System UNIX is a multi-user multiprocess system, meaning several users can use the same computer at the same time several processes, meaning executable programs, can be started at the same time by one user ID UNIX Applications Most business-critical applications are client/server applications (2, 3 or 4-tier). The application server processes (hereafter referred to as application processes) run on UNIX, while the client interface is either a browser or a Windows application on a front-end PC. Applications consist of several application processes that may even communicate with each other beyond the computers' boundaries. The services of these processes, which are started by a system user, must always be highly available and highly performing, to respond to client requests as best as possible. Figure 1: Multi-user and Multiprocess System (schematic) Copyright REALTECH 2008 Page 6 of 31

7 Using the UNIX system Each user who logs in to a UNIX system opens a so-called shell, the environment in which the users' commands are interpreted and executed. General structure The operating system is the interface between the hardware and the user and/or the applications. Figure 2: General Structure of UNIX The hardware is the basis. The hardware consists of the memory, where the processes are stored during their execution (swapping is also an option), the CPU's central computing unit, the hard disks on which the files and programs are permanently stored, and the network that connects your computer to other computers. The UNIX operating system runs on the hardware. Its main task is to control and manage the hardware and provide all of the programs with a standard system call interface. The system calls, which only run in kernel mode, enable user programs, processes, files, and other resources to be generated and managed. The basic tasks of the UNIX operating system are: Process Management o Load, start, interrupt, and end processes o Allocate processor time to processes (scheduling) o Synchronize the workload distribution on multiprocessor machines Memory Management o Allocate, manage, and release memory to processes o Monitor and protect the memory from other processes accessing it o Temporarily move processes (swapping) to mass storage devices Copyright REALTECH 2008 Page 7 of 31

8 Device and file management, and I/O control o Organize and manage the data on the mass storage devices in a hierarchical file structure o Manage access permissions to the file system o Efficiently allocate I/O devices and switching units (data channels, control units) to prevent conflicts. Initialize and monitor the execution, schedule I/O processes, convert data, and logically control the file system. o Manage computer peripherals such as terminals, mass storage devices, I/O ports, the network, etc. o Convert common read/write operations to device-specific control signals o Coordinate concurrent accesses to I/O resources Authentication and Access Control o Manage users and their access permissions to system resources o Log users in to and out of the system o Protect system resources from users that do not have the correct permissions Log Processing and Error Handling o Record important functions and events such as error statuses in the system log o Recognize error statuses and process them accordingly User interfaces o The shell and additional/other service programs, among other things, administration programs o Text-based (console) and graphical user interface for communication between man and machine Copyright REALTECH 2008 Page 8 of 31

9 Special Features of the AIX 5L Operating System with Virtualization AIX 5L supports Logical Partitioning (LPAR) to consolidate servers and balance the load. This enables a physical server (e.g., an IBM eserver pseries 690, 16-way SMP) to be split into several logical partitions (virtual server), and memory, CPU, I/O channels and/or hard disks to be flexibly assigned. Because of the POWER5 (P5) processor's architecture, which has 2 logical processors, more logical partitions can be created than the number of available physical processors. This is why the virtual servers are also called micro partitions. Different IBM operating systems can be installed on these partitions. From AIX 5.2 onwards, resources can be added to all of the partitions dynamically without rebooting the system. Applications such as SAP instances or Oracle instances run on a micro partition. Copyright REALTECH 2008 Page 9 of 31

10 When LPAR is used, all of a partition's physical units must be monitored and their load analyzed in addition to monitoring the virtual units and their configuration and load. This is necessary because the virtualization is not dynamic down to the resource processor. For example, memory must be reconfigured manually to redistribute it between the partitions. This is why the load of all of the physical and virtual resources must be comprehensively monitored and logged. The new AIX data collector does just that. The AIX DC is licensed per virtual server and/or partition. Because all of the other database data collectors SAP NetService, and so forth can also be run within a partition, theguard! ApplicationManager fully supports the AIX 5L platform with LPAR. Copyright REALTECH 2008 Page 10 of 31

11 The System AIX Data Collector The System AIX data collector consists of two Managed Object Types (MOT). The first MOT, the Host MOT, provides a physical overview of the machine. The second MOT, the OS MOT, provides information that is directly related to the operating system. The clear separation of hardware and software makes it easier to integrate future platform developments in the REALTECH CIM model. The below figure displays the structure underneath a micro partition: Host: The model name describes the model of the used hardware. Disk: This partition's physically available hard disks Errorlog: The error log of the operating system Memory: The available memory that is allocated to a partition Processor: The partition's physically configured processors, which can also be CPU shares OS: The partition's operating system. FileSystemGroup: The FileSystem groups configured by the user ProcessGroup: The application processes as grouped by the users SwapSpace: The swap partitions that are used by the operating system VirtualProcessor: The processors used by the operating system scheduler VolumeGroup: The volume groups that are managed by the operating system o Volume: The logical volumes in the next higher volume group Only information referring to the local system is gathered and displayed. Figure 3: DC tree (overview) The managed objects, the concrete physical objects of the MOTs, are hierarchically arranged and clearly structured. The above figure displays the managed object for the MOT "Disk," MO "hdisk2." Presenting the information in this way displays the current status at a glance. Monitoring parameters can be set individually for each component. Copyright REALTECH 2008 Page 11 of 31

12 Using the System AIX DC to Monitor Hardware and Software Resources To ensure the operating system and hence the live applications runs smoothly, monitoring hardware and software resources such as processors, memory, hard disk space, virtual memory, processes, etc. is very important. The resources are monitored for sufficient capacity and performance. If only one of the resources is overloaded or depleted, the performance of the entire system decreases dramatically. This can have a negative impact on the server's live environment, and in many cases, even results in erratic behavior. In the worst case, the stability of the entire system is at risk. By continuously monitoring the system resources, the System AIX DC reports overloads and highly used resources at an early stage, before important resources are overloaded or depleted. This enables the system administrator to react early to resource bottlenecks and remove them before they impact or bring down the live system. The System AIX DC provides a variety of statistical values regarding the current usage and performance of the monitored server's hardware and software resources. Thresholds, which are used to generate alerts when they are violated, can be defined for all of the statistical values. Resource bottlenecks are detected at an early stage and can be removed in a controlled manner. Operability and performance monitoring can be carried out at the same time. All of the statistical values can be monitored and compared in the Real-time Performance Monitor. These values can be used to optimize the performance and the capacity. Figure 4: Current usage in percent of all of the virtual processors' system resources Copyright REALTECH 2008 Page 12 of 31

13 The different servers' resource usage and performance data can be compared. This information is particularly useful for optimization tasks such as the efficient distribution of the load across several servers. The statistical values can also be collected in the ApplicationManager database and evaluated using REALTECH Reporting. This information can be used to generate long-term trend analyses, for example, for the usage of system resources such as CPU, memory, and disk space, and used as a basis for cost and capacity planning. Monitoring and Information about the Hardware (Host) Figure 5: Properties of the Host object displayed in ApplicationManager's Managed Monitor The Host information object provides information about the local system, such as its available hard disks. Furthermore, the processor utilization by the system, as well as the assignment of the processors to the LPAR can be monitored with counters. The performance criteria for the monitoring of a host object are: Kernel time total, in percent (sys time total) User time total, in percent (user time total) Waiting time total, in percent (user time total) Idle time total, in percent (idle time total) Assigned computing time of the object per processor, in percent (entitlement percent) Assigned computing time total (entitlement) Assigned computing time of the object, in percent (processor entitlement percent) Copyright REALTECH 2008 Page 13 of 31

14 Monitoring and Information about the Partitions' Hard Disk (Disk) Figure 6: Properties of the Disk object displayed in ApplicationManager's Managed Monitor The properties displayed here relate to the system's available hard disks. The progression of statistical values, for example the fill level, can be used in the appropriate policy to generate an alert or send a notification. Adding more swap space increases the availability and performance of the applications when bottlenecks occur. The performance criteria for the monitoring of a disk object are: Free disk space in kilobytes. Free disk space in percent. Used disk space in kilobytes. Used disk space in percent. Total size of the disk space in kilobytes. The number of blocks read since the hard disk became available to the operating system. The number of blocks written since the hard disk became available to the operating system. The difference between the read blocks since the last time the counter was read. The difference between the read blocks in kilobytes since the last time the counter was read. The difference between the written blocks since the last time the counter was read. The difference between the written blocks in kilobytes since the last time the counter was read. Copyright REALTECH 2008 Page 14 of 31

15 Monitoring the Errorlog Figure 7: Error messages of the AIX Errorlog in ApplicationManager The Managed Object Type Errorlog allows for evaluating entries of the descriptor en_class (AIX) with the following classes of the ApplicationManager (AM). Hardware entries (AM) = Hardware Error class (AIX) Software entries (AM) = Software Error class (AIX) Operator entries (AM) = Messages from the errlogger command (AIX) Undetermined entries (AM) = Undetermined (AIX) With the extensive configuration possibilities for the Errorlog in AIX,, moreover a variety of important error messages can be displayed in ApplicationManager as events. Copyright REALTECH 2008 Page 15 of 31

16 Monitoring and Information about the Partitions' Memory (Memory) Figure 8: Properties of the Memory object displayed in ApplicationManager's Managed Monitor The properties displayed here relate to the system's memory. The progression of statistical values, for example the fill level, can be used in the appropriate policy to generate an alert or send a notification. Adding more memory (dynamic partitioning DLPAR) increases the availability and performance of the applications when bottlenecks occur. The performance criteria for the monitoring of a memory object are: Free real memory in kilobytes Free real memory in percent Used real memory in kilobytes Used real memory in percent Total size of the real memory in kilobytes Size of reserved memory in kilobytes Size of the virtual memory that is used by the operating system for addressing in kilobytes Number of dirty pages since the operating system started working Number of missing pages since the operating system started working Number of swapped in pages since the operating system started working Number of swapped out pages since the operating system started working The difference between the number of dirty pages since the operating system started working and the last time the counter was read The difference between the number of missing pages since the operating system started working and the last time the counter was read The difference between the number of swapped in pages since the operating system started working and the last time the counter was read The difference between the number of swapped out pages since the operating system started working and the last time the counter was read Copyright REALTECH 2008 Page 16 of 31

17 Monitoring and Information about the Partitions' Processors (Processor) Figure 9: Properties of the Processor object displayed in ApplicationManager's Managed Monitor The managed object Processor is a small information object that provides general information, such as the processor type. Each processor conceals part of the physical CPU, which is assigned in the Hypervisor of, for example, a p570. When the machine is micro partitioned, anywhere between 10% and 100% of a CPU can be concealed. Copyright REALTECH 2008 Page 17 of 31

18 Information about a Partition's Operating System (OS) Figure 10: Properties of the OS object displayed in ApplicationManager's Managed Monitor Figure 11: Properties of the Process List object displayed in ApplicationManager's Managed Monitor Copyright REALTECH 2008 Page 18 of 31

19 The properties displayed here relate to the partition's operating system. Figure 12: Properties of the User Group List object displayed in ApplicationManager's Managed Monitor Figure 13: Properties of the User List object displayed in ApplicationManager's Managed Monitor. Copyright REALTECH 2008 Page 19 of 31

20 The performance criteria to monitor the OS object are divided into two classes: Total swap space o Free swap space in percent o Free swap space in kilobytes o Absolute value of the swap space in kilobytes o Used swap space in percent o Used swap space in kilobytes Total virtual processor o Idle time in percent o Sys time in percent o User time in percent o Wait time in percent o CPU utilization total, in percent The progression of the above statistical values can be used in the appropriate policy to generate an alert or send a notification. Adding more memory (dynamic partitioning DLPAR) increases the availability and performance of this partition's applications when bottlenecks occur. Monitoring and Information about File Systems (FileSystemGroups) Figure 14: User-defined FileSystem groups The utilization of the file systems can be monitored with this feature, which enables you to punctually discern bottle-neck situations. Copyright REALTECH 2008 Page 20 of 31

21 The criteria for monitoring FileSystemGroup objects are collected in a single category FileSystemGroup, which provides the following counters: Free space, in kbyte Free space, in percent Total space, in kbyte Used space, in kbyte Used space, in percent Number of mounted file systems (especially interesting for the search with regular expressions) Moreover, events can be generated with the event category Filesystem changes if a FileSystem is mounted or unmounted. The progression of the statistical values above can be used in the appropriate policy to generate an alert or to create reports. You can create FileSystemGroups and fill them with file systems with the following two methods. The selection can either be done manually or through the specification of a regular expression. Figure 15: Definition of FileSystem groups through selection When manually selecting Filesystem by Selection, you can activate a file system in the LogicalVolumeList of a FileSystemGroup. Figure 16: Definition of FileSystem groups through patterns (regular expressions) Copyright REALTECH 2008 Page 21 of 31

22 theguard! ApplicationManager System AIX Data Collector When selecting with help of regular expressions Filesystem by Pattern, the LogicalVolumeName as well as the LogicalVolumeMountPoint can be searched for. All matching file systems will be entered in the respective FileSystemGroup and monitored. Figure 17: User-defined FileSystem groups The Properties of a FileSystemGroup display a list of contained file systems. This list first of all is interesting for the search with regular expressions. Monitoring and Information about Application Processes (Process Groups) Figure 18: Application process groups; TOTAL for all processes. Process groups such as SAP, Siebel, Oracle, etc., can be freely defined. For each process group, the performance values of the above-described resources, such as memory and CPU, can be evaluated and alerts displayed in real time. It is also possible to generate reports from the long-term log to analyze the availability and increase the performance of the applications. Copyright REALTECH 2008 Page 22 of 31

23 theguard! ApplicationManager System AIX Data Collector Monitoring and Information about Individual Swap Space Units Figure 19: Property of the system's Swap Space displayed in the ApplicationManagers' Managed Monitor The properties displayed here relate to the system's swap space. The progression of statistical values, for example the fill level, can be used in the appropriate policy to generate an alert or send a notification. The performance criteria for the monitoring of a swap space object are: Free swap space in kilobytes Free swap space in percent Swap space usage in kilobytes Swap space usage in percent Total size of the swap space Monitoring and Information about Individual Virtual Processors The performance criteria for the monitoring of a virtual processor object are: VirtualProcessor o Idle time in percent o Sys time in percent o User time in percent o Wait time in percent Copyright REALTECH 2008 Page 23 of 31

24 theguard! ApplicationManager System AIX Data Collector Monitoring and Information about Logical Volume Groups Figure 20: Properties of the Logical Volume object displayed in ApplicationManager's Managed Monitor Figure 21: Properties of the Volume Group object displayed in ApplicationManager's Managed Monitor The properties displayed here relate to the system's volume groups. Displaying the physical partition size (PP Size) and the resulting partitions within a VolumeGroup, makes the point at which the VolumeGroup could not be extended without adding physical storage media immediately visible. The progression of statistical values, for example the fill level, can be used in the appropriate policy to generate an alert or send a notification. Adding more hard disks to the VolumeGroup increases the availability and performance of the applications when bottlenecks occur. Copyright REALTECH 2008 Page 24 of 31

25 theguard! ApplicationManager System AIX Data Collector The performance criteria for the monitoring of a volume group object are: Number of free blocks Number of used blocks Total number of blocks Number of free blocks in percent Number of used blocks in percent Monitoring and Information about Logical Disks (Logical Volumes) Figure 22: Properties of the Logical Volume object displayed in ApplicationManager's Managed Monitor The properties displayed here relate to the system's logical volumes. The AIX platform clearly distinguishes between the data system's old approach to virtual file systems and configuring a volume. All of this platform's administration tools use this approach to manage a data system. The progression of statistical values, for example the fill level, can be used in the appropriate policy to generate an alert or send a notification. Adding more blocks to each logical volume increases the availability and performance of the applications when bottlenecks occur. Copyright REALTECH 2008 Page 25 of 31

26 theguard! ApplicationManager System AIX Data Collector The performance criteria for the monitoring of a volume object are: Number of free Inodes on this volume Number of used Inodes on this volume Total number of Inodes on this volume Number of free Inodes on this volume in percent Number of used Inodes on this volume in percent Size of used storage space in kilobytes Size of used storage space in percent Size of unused storage space in kilobytes Size of unused storage space in percent Size of storage space in kilobytes Standard Reporting and Service Level Analysis In addition to monitoring performance and displaying and triggering alarms for critical statuses, theguard! ApplicationManager can also be used to evaluate historical data to verify service levels or plan capacity: Service Level Analysis Configuration of Object Level Agreements (OLAs) for an application s process and/or process group Measuring the availability against the rules and reports Standard Reporting (Performance and Capacity): Availability of an application s process and/or process group Load and resource usage of an application s process and/or process group by the above-mentioned parameters CPU usage Single processor usage Memory Application Processes and Business Systems Applications in the form of process groups are managed objects that can be used on Business Systems in theguard! ServiceCenter to map distributed applications and business processes. Copyright REALTECH 2008 Page 26 of 31

27 theguard! ApplicationManager System AIX Data Collector Case Study of a Monitored System The following Performance Monitor figure shows how the load can be measured on a system. First, the status "Idle" (unused processor capacity, idle processors): Figure 23: Performance Monitor - All processors are idle The following elements were selected for monitoring: Process group ALL, so that all of the changes incurred by adding additional processes are clearly visible Processors 0 2 and TOTAL, to clearly display the incurred processor load Memory, to clearly display the memory requirements The goal is to determine which system resources are affected when a processor-intensive process, such as a test program, is started. Copyright REALTECH 2008 Page 27 of 31

28 theguard! ApplicationManager System AIX Data Collector The below figure displays the processes running on the processor. The system's performance rapidly decreases when the "load" test tool is used, as is clearly displayed in the Performance Monitor. Figure 24: Performance Monitor Starting the "load" test tool If the appropriate rules are defined, the events in the Event Browser show if thresholds were violated and if processes were added to the group and/or deleted from the group if they were scheduled. Figure 25: Example of the Event Browser for process group events for dynamic processes Copyright REALTECH 2008 Page 28 of 31

29 theguard! ApplicationManager System AIX Data Collector The next figure clearly shows the effects and the resources affected (for example, memory) on a heavily used machine. Figure 26: Performance Monitor of processes, using the "load" test tool example Once the test tool has been started and the processors occupied (start-up effect) periodic load peaks occur on the processor and memory occupancy. Copyright REALTECH 2008 Page 29 of 31

30 theguard! ApplicationManager System AIX Data Collector The next figure provides a clearer overview by looking at the virtual CPU only: Figure 27: Performance Monitor - Overview of all usage information of the test tool run When the test tool is finished, the system returns to its idle state. The above example shows how the application processor usage can be traced to the processor level in real time. Adding similar monitors for process groups or combining process values from SAP, Oracle, etc. by dragging and dropping them enables you to determine by period which processors are loaded by which applications. The same applies to the other theguard! ApplicationManager data collectors' performance counters, for example, SAP Job Performance, SAP Transaction Performance, and the performance of other applications. Copyright REALTECH 2008 Page 30 of 31

31 theguard! ApplicationManager System AIX Data Collector Availability and Platforms The System AIX DC is immediately available. Supports the following operating systems for partitions: AIX 5.1, AIX 5.2 and AIX 5.3. For more information about REALTECH s software products see: REALTECH AG Industriestr. 39c Walldorf, Germany Tel.: +49-(0) Fax: +49-(0) customer-services@realtech.com Copyright REALTECH 2008 Page 31 of 31