Monitor SAP PI ASUG para interfaces SAP PI Implementadas

Process Integration Monitoring Best Practice

Version 1.0

Date: December 09 Author: VNSG PI Task Group

P r o c e s s I n t e g r a t i o n M o n i t o r i n g B e s t P r a c t i c e

PROCESS INTEGRATION MONITORING - BEST PRACTICE.DOC PAGE 2 OF 58

Document properties and versioning

Version & Date SUG Contributors

Version 0.1

May 8, 2009

Scope SAP PI Monitoring draft document created by VNSG task group in collaboration with Special Interest Group SAP Solution Manager. To be reviewed by SAP, DSAG, VNSG and ASUG members. VNSG taskgroup authors and contributors Peter Schults Ctac (Chair) Meindert Jansen HMB (SIG SSM) Raymond Boekel Atos Origin Mark van Dooren Capgemini BAS Dirk-Jan Kloezeman Ordina Fred Verheul NL4B Occo Vreezen T-Systems

General remark First concept, document to be discussed and enhanced by DSAG, VNSG and ASUG members

Version 0.2

October 15, 2009

General remark Comment of DSAG and SAP reviewed and added in document Authors and contributors Herman Steinroetter BP Holger Himmelmann, CBS Corporate Business Solutions Rudiger Bellof Evonik Marco Dorn SAP Udo Paltzer SAP

Version 0.3 November 11, 2009

General remark Lay out edited by VNSG Peter Schults Occo Vreezen

Published on the SAP Collaboration Workplace

Version 0.4 December 1, 2009

General remark Comment of DSAG and SAP reviewed and added in document Authors and contributors Holger Himmelmann, CBS Corporate Business Solutions Peter Schults Ctac



Index

Document properties and versioning .............................................................................. 2 1 Introduction............................................................................................................... 5 2 Introduction............................................................................................................... 7 3 System landscape decisions .......................................................................................... 8 3.1 Simple interface Landscape ..................................................................................... 8 3.2 Medium Interface Landscape .................................................................................... 8 3.3 Complex interface Landscape ................................................................................... 9

4 Service Organization Setup ......................................................................................... 11 5 Interface Components and Monitoring............................................................................. 12 6 Runtime WorkBench Monitoring Components.................................................................... 13 6.1 RWB (http://:/dir)................................................................................. 13

6.1.1 Component Monitoring .................................................................................... 13 6.1.1.1 Integration Server Details ........................................................................... 14 6.1.1.2 Business Process engine ........................................................................... 15 6.1.1.3 Mapping runtime ...................................................................................... 15 6.1.1.4 Adapter Engine ....................................................................................... 16 6.1.1.5 Communication Channel Monitoring .............................................................. 16 6.1.1.6 Engine Status ......................................................................................... 16 6.1.1.7 Message Backlog Monitoring ....................................................................... 17 6.1.1.8 EOIO Monitoring ...................................................................................... 17

6.1.2 Message Monitoring ....................................................................................... 18 6.1.2.1 Message Overview Page............................................................................ 19

6.1.3 End-to-end monitoring..................................................................................... 21 6.1.4 Performance Monitoring................................................................................... 22

6.1.4.1 Monitoring the overall performance................................................................ 22 6.1.5 Index administration ....................................................................................... 23 6.1.6 Alert configuration.......................................................................................... 23 6.1.1 Alert inbox ................................................................................................... 25 6.1.2 Cache Monitoring .......................................................................................... 26

6.2 Adapters in the PCK............................................................................................. 27 6.2.1 Adapters on the standalone J2SE Engine ............................................................. 27

7 Abap Monitoring functions ........................................................................................... 28 7.1 SXMB_MONI: XML messages on the Integration Server and Engine .................................. 28 7.2 ccBPM Monitoring ............................................................................................... 29 7.3 Alerting Framework.............................................................................................. 30

7.3.1 Display Alerts ALRTDISP ................................................................................. 30 7.3.2 Processing Alerts ALRTPROC........................................................................... 31 7.3.3 Alert Categories Display ALRTCATDEF ............................................................... 32 7.3.4 Process of a TEST Alert (RSALERTTEST)............................................................ 32

7.4 ICM Monitoring ................................................................................................... 33 7.5 Gateway Monitoring ............................................................................................. 33 7.6 Queue Monitoring................................................................................................ 33

7.6.1 Monitoring System Performance ........................................................................ 35 7.7 Job monitoring of housekeeping jobs ........................................................................ 36

7.7.1 Jobs with a fixed job name ............................................................................... 36 7.7.2 Jobs with a fixed ABAP program name................................................................. 36 7.7.3 Background jobs running on the J2EE engine ........................................................ 36 7.7.1 Adapters in the Integration Server: IDoc Adapter ..................................................... 37 7.7.2 Sync-Async Bridge......................................................................................... 38



7.8 IDoc Packaging Monitoring..................................................................................... 38 7.9 Message Packaging Monitor................................................................................... 38

8 Business Activity Monitoring (BAM) ................................................................................ 39 9 Monitoring PI with Solution Manager............................................................................... 41 9.1 Monitor Diagnostics agents status ............................................................................ 41 9.2 Solution Manager Diagnostics Agent(s)...................................................................... 41

10 CCMS Computing Center Management System .............................................................. 43 10.1 Monitoring component XI .................................................................................... 43 10.2 Availability Monitoring ........................................................................................ 45

11 Administrator Monitoring Functions.............................................................................. 48 11.1 JAVA monitoring environment .............................................................................. 48 11.2 SAP Management Console ................................................................................. 49

12 Proxies ............................................................................................................... 51 13 Third Party Monitoring Tools...................................................................................... 52 13.1 HP OpenView ................................................................................................. 52 13.2 Gensys ......................................................................................................... 52 13.3 BMC............................................................................................................. 53 13.4 ARIS Process Performance Monitoring .............................................................. 53

13.5 Seeburger Message Tracking Tool .................................................................... 54

14 Appendix ............................................................................................................. 57 14.1 XI readiness check ........................................................................................... 57 14.2 Activate Message overview component................................................................... 57 14.3 PI Monitoring with SAP NetWeaver Administrator....................................................... 57 14.4 Interface monitoring with Solution Manager .............................................................. 57

15 Useful links .......................................................................................................... 58



1 Introduction

The aim of this document is to have a best practice for the topics monitoring and exception handling. These topics are becoming increasingly important for businesses running SAP solutions using the process integration components. Enterprises become more and more involved in end-to-end processes with their customers and partners and thus need integration scenarios. These processes are at the very core of the enterprise and need attention in case of exceptions. It is crucial to trace the root cause of any problems that arise, to identify the proper action and to assign and inform the responsible person. In the SAP product family there is a variety of business activity monitoring and exception handling solutions available to meet the needs of enterprises running SAP. However, there is a tendency to centralize and consolidate the monitoring and error-handling activities for all SAP and non-SAP components in the value chain and not just for the process integration aspects (e.g. interfaces to the outside world). Therefore, SAP is launching a monitoring and exception handling roadmap. In current day-to-day business, enterprises use third-party products for their central IT-monitoring and exception handling. These products interact with the SAP components as complementary products. This implies that various concepts are used in which SAP products and non-SAP products work together. Another important factor for monitoring and exception handling is the importance on the interfaces of the enterprise. This has an impact on the investment in the monitoring/exception handling structure, time frames and organization. So, this is where international best practices for this topic are needed.

Why this document? As a part of international collaboration of SAP user groups, a pilot is held in the area of process integration. This is a joint venture of the ASUG (American SAP User Group), the DSAG (German SAP Users Group) and the VNSG (Dutch SAP Users Group) Special Interest Groups. This venture is hosted and supported by the Global Customer Communities Team of SAP AG. In a survey held amongst all PI users in these countries (USA, Germany and the Netherlands) it was obvious that monitoring/exception handling was the number one topic. It was decided that the user community needed a best practice to help the individual businesses to properly assess the investment in monitoring/exception handling with respect to risk, availability and continuity in the business processes of the integrated processes in the value chains. This document is a first attempt to tackle these topics.

Your valuable input is needed We highly appreciate your input to improve this document. The area in itself is constantly evolving. Therefore, it is relevant for every company which is running SAP. Your knowledge and experience will help other enterprises in the worldwide user community, which was also the idea behind the initiative of the aforementioned international collaboration of Special Interest Groups.



A guide to the reader of this document How important is the monitoring/exception handling concept for your business? This determines the balance between investments in precautions and costs as a result of risks taken (e.g. a million dollar order could not be processed in time due to an unmonitored failing file interface). The following parameters determine the playground for the proper monitoring concept. The first parameter is the importance of the interface for the business (timeframe to correct errors and money involved in the transaction data). The second parameter is the integration of your processes. If your enterprise is highly dependent on end-to-end processes in the value chain of your business you require end-to-end process monitoring. If your interfaces are not that important, you will use technical monitoring and an IT help desk which will solve the exceptions. The third parameter is how dominant SAP is in your value chains. In an SAP-centric enterprise you will tend to use the SAP-monitoring concepts and tooling (SAP Solution Monitor, Business Activity Monitoring or CCMS alerting). If not, you will use third-party tools like HP Open View or Seeburger monitoring tools and others. In addition, you may need the process monitoring aids on a strategic level in SAP BI in the Business Objects suite of solutions or in depth process drill downs using the IDS Scheer Process Performance Management (PPM) component to find out how many orders are processed correctly the first time around and why others fail and in which step.

This best practice document gives you an overview of the various SAP monitoring tools and the most effective ways to use them. As explained above, there is a variety of SAP tools, each with specific characteristics and goals. More detailed alerting and monitoring tools are provided for SAP IDoc packages, Message packing, ICM, gateway, queue and housekeeping job monitoring.

To centralize monitoring and exception handling, SAP Solution Manager (technical monitoring and alerting) and Business Activity Monitoring for integrated processes are handled. The appendix contains information on additional supporting mechanisms, such as the XI readiness check, activate message overview, PI monitoring with SAP NetWeaver administrator and how to monitor interfaces with SAP Solution Manager.

Acknowledgement This first draft was compiled by a task group of the Special Interest Group Process Integration of the Dutch SAP Users Group (VNSG). The task group was led by Peter Schults. Group members were: Mark van Dooren, Fred Verheul, Ramon Boekel, Dirk-Jan Kloezeman and Meindert Jansen. The following persons were involved in creating this document: Occo Vreezen, Hans de Labije (VNSG) and Huub Montanus, (Process Integration SIG Chair).



2 Introduction This document provides guidelines based on best practices on how to set up monitoring in a system landscape with PI as the interface component. Information about interaction with Solution Manager as a monitoring component will also be provided.

Monitoring decisions and preparations: - How is your Service organization setup? - How complex is your system landscape? - Who is monitoring? - What action(s) should be taken? - Available monitoring components - Monitoring frequency

Depending on the organization structure, monitoring is in most cases divided in technical and functional areas. We suggest the following division:

- Technical support area - all activities to make sure al infrastructures are up and running. - Functional support area - all activities to ensure that business processes are up and

running.



3 System landscape decisions

3.1 Simple interface Landscape

3.2 Medium Interface Landscape



3.3 Complex interface Landscape



Monitoring components

Simple Medium Complex

RWB Monitoring Functions

SAP Standard

ABAP Monitoring Functions

SAP Standard

PI Alerting Setup

Configuration Required

CCMS Setup Configuration Required

Solution Manager Functions


Thirth Party Monitoring Products


NetWeaver Administrator Tools

SAP Standard

SAP Management Console

SAP Standard

Business Activity Monitoring (BAM)




4 Service Organization Setup When we talk about Monitoring, we like to differentiate system and application monitoring. System monitoring is about the environment the application is running in, while application monitoring is really focused on the application itself. The goal is to detect signs of instability and do proactive maintenance before any major impact the end users, hence better your business. It also provides a good understanding of the platform usage, whether the infrastructure is under-used or over-loaded. For example, it may give good data points to adjust the hardware or sizing of your landscape.

System monitoring may cover anything external to the application: OS, networking, CPU, IO, memory, etc. This is a market that other vendors have built expertise on with products like IBM Tivoli, BMC Patrol or Microsoft SCOM.

Application monitoring focuses on availability and performance of the application itself. One would typically mimic user actions on a regular basis as a "health check" and build metrics on error rate and response time



5 Interface Components and Monitoring

This graphic shows the components that make up SAP Process Integration 7.1. SAP Process Integration consists of the following functional components:

Integration Builder o Enterprise Service Repository (ESR) o Service Registry (SR) o Integration Directory

System Landscape Directory (SLD) Integration Server

o Central Adapter Engine (Advanced Adapter Engine) o Integration Engine o Business Process Engine (ccBPM)

Runtime Workbench SAP Netweaver Administrator (NWA) Non-central Adapter Engines Load Balancer Tool (e.g. SAP Web Dispatcher) Solution Manager (not an integral part of PI)

Most of these components have to exchange information during runtime of Process Integration. Thus, it is essential that each component can be accessed and that the communication between them is set up correctly.



6 Runtime WorkBench Monitoring Components

6.1 RWB (http://:/dir) The Runtime Workbench runs on the Integration Server, but it also allows the monitoring of distributed PI components, such as local Advanced Adapter Engines or proxy runtimes from SAP business systems.

6.1.1 Component Monitoring PI component monitoring in SAP NetWeaver Administrator gives you an overview of your current integration landscape and provides you with information about the availability of the selected component and details about component self-tests.

You use component monitoring in the following cases: To get an overview of the status of the individual PI components. To call the configuration data of individual components. To use test messages to check whether the runtime components are functioning

correctly. To test whether cache connectivity is functioning correctly To archive the Message Security Settings or Whole Messages. To check the status of your communication channels or the Java Proxy Runtime

configured in them.



To display current technical data for your Adapter Engine If you want to prioritize message processing on your Adapter Engine.

You use the runtime workbench to display and monitor the following components:

Integration Server Integration engine Business Process engine Mapping runtime Adapter engine

ABAP Proxy Systems Non Central Adapter Engines J2EE Adapter System landscape Integration directory Integration repository Runtime workbench

6.1.1.1 Integration Server Details



6.1.1.2 Business Process engine

6.1.1.3 Mapping runtime



6.1.1.4 Adapter Engine

6.1.1.5 Communication Channel Monitoring A first indicator about the status of the communication channels is already given by the result of the self-test in the Component Monitoring of the Runtime Workbench for a selected Adapter Engine. If you see a red light in the Communication Channel (CC) monitoring this already indicates that there are CC in error.

6.1.1.6 Engine Status New functionality is added to the Workbench to monitor the Messaging System which is part of the Adapter Framework running on the Java stack. Before, these monitors existed partially but were not accessible or cluster enabled. All these monitors for the Messaging System can be accessed in the Component Monitoring of the Runtime Workbench by choosing your Adapter Engine and then clicking on the Engine Status button on the Status tab. A new window will be opened showing several tabs.



6.1.1.7 Message Backlog Monitoring The message backlog monitor for the adapter engine shows how many messages are in the queue for a specific sender or receiver service. The monitor is Cluster Independent therefore showing the backlog for the queues across all configured J2EE server nodes.

6.1.1.8 EOIO Monitoring A number of these monitors are aimed to simplify the monitoring of Exactly Once in Order (EOIO) scenarios. To identify the reason for a backlog you can use the EOIO Sequences tab. This monitor displays the EOIO message with status HOLD with their respective predecessor messages and is not node-specific.



6.1.2 Message Monitoring Every message that runs into an error in the Adapter Framework and/or the Integration Server Pipeline gets persisted. In this way it is possible to monitor errors and to restart erroneous messages (asynchronous messages only). Both the IS pipeline and the Adapter Framework, have retry mechanisms, but after the retries are done and the error still persists, it becomes necessary to analyze the underlying problem.

With XI 3.0 SPS 20 / PI 7.0 SPS12 a new overview message monitor was introduced providing an overview of message processing during a specific time period. For each sender, receiver or interface the messages will be grouped by different status as for instance Error, Successful, Scheduled. From there you can simply navigate to individual messages and take corrective actions if necessary. This new monitor is a very powerful tool simplifying message monitoring and should be the central entry point for administrators being responsible for message monitoring. A separate overview page exists for the Integration Server, the central Adapter Framework and all connected decentral adapter engines.



6.1.2.1 Message Overview Page Use the message overview to see the number of messages that are in a certain processing status in a specific time period. This time period always refers to the receipt of the message. These are the various status groups:

Scheduled Successful With Errors Canceled with Errors

From this screen you are able to zoom in to the messagedetails.

From this point you are able to display the actual message content.



6.1.3 End-to-end monitoring You use end-to-end monitoring in the following cases:

If you want to monitor message processing steps in a number of SAP components (to be configured).

If you want to monitor the path of individual messages through these SAP components, from start to end.



6.1.4 Performance Monitoring

6.1.4.1 Monitoring the overall performance



6.1.5 Index administration

6.1.6 Alert configuration To provide central monitoring with all errors reported during message processing in ABAP runtime and the Java-based Adapter Engine, Alert Framework is used. The objective is to prevent delays in the processing of critical situations, because the time between discovering and responding to such situations is reduced considerably. You use the alert configuration to have the system inform you of errors during message processing. You can receive the alert by e-mail, fax, or SMS. In each case you will also find the alert in your alert inbox.

Configuration of alerts to reflect the needs of specific processes Part of SAP Web AS When using the alerting framework it is recommended to maintain solved issues to

Complete status. There are also some cleanup jobs supplied to remove old alerts from the database.



Define Alert Categories gives the option to separate the recipients per interface.



6.1.1 Alert inbox

Displaying the message details will link you to the RWB (Runtime Workbench) message monitor.



6.1.2 Cache Monitoring (http://:/rwb/FrontComponent/FC_Secure.jsp?doAction=showCacheMonitoring With this function you can view the status of the different cache instances of the system. Integration Server, Adapter Engine Mapping runtime.



6.2 Adapters in the PCK

6.2.1 Adapters on the standalone J2SE Engine



7 Abap Monitoring functions

7.1 SXMB_MONI: XML messages on the Integration Server and Engine

To verify the successful execution of message execution for standard message monitoring we recommend using the central view of the RWB. Only if you need additional information like e.g. the outbound adapter status or the performance header of the message execute transaction SXMB_MONI.



This monitor provides detailed information about the message processing and message mapping components.

7.2 ccBPM Monitoring

Monitoring of ccBPM processes ccBPM (cross component Business Process Management) uses the workflow and runs in the so-called Business Process Engine (BPE). During the post-installation steps, a job for the restarting of erroneous Business Processes has been created.

During the development of the ccBPM processes, error processing should be part of the development process. The PI Alerting mechanism can be used to inform the responsible persons about failures in this process.



Possible errors with ccBPM; mapping errors, missed deadlines.

7.3 Alerting Framework

On the ABAP site there are also functions available to display and configure alerting on the PI system:

7.3.1 Display Alerts ALRTDISP



7.3.2 Processing Alerts ALRTPROC



7.3.3 Alert Categories Display ALRTCATDEF

7.3.4 Process of a TEST Alert (RSALERTTEST)

Sample email message



7.4 ICM Monitoring ICM is the Internet Communication Manager. It is responsible for all incoming and outgoing HTTP calls and thus of high importance for Process Integration.

Transaction: SMICM

7.5 Gateway Monitoring

Process Integration mainly uses the gateway of the Web Application Server to communicate with the J2EE Engine. At the gateway, several programs of the J2EE Engine are registered, the most important being AI_RUNTIME_, the program used for mapping requests.

Transaction:SMGW

7.6 Queue Monitoring

Queues (qRFC inbound queues) are the core of the Integration Server. Within queues all messages are processed, including Logical Routing, Technical Routing, Mapping and the call of



the appropriate adapter. Queues are thus a neuralgic point for PI: either if they are blocked or if they do not process messages fast enough.

Transaction:SMQ2



7.6.1 Monitoring System Performance

This area is probably already covered by typical basis administration tools / jobs. However, it should be mentioned shortly to complete the performance section.

Transaction ST06.



7.7 Job monitoring of housekeeping jobs

7.7.1 Jobs with a fixed job name

Log in to your Integration Server and call transaction SM37. If you have used a dedicated user for all housekeeping jobs, enter this user. If you have used different users, search for the job names provided in the following checklist. Have a quick glance at the job log of each job.

SAP_BC_XMB_DELETE_ (deletion of XML messages if not archived) SAP_BC_XMB_HIST_DELETE_ (deletion of history entries) ARV_BC_XMB_WRP (archiving of XML messages if not deleted) ARV_BC_XMB_DEL (deletion of archived XML messages if not deleted) SXMS_DELAYED_MSG_PROC (job for delayed message processing, only if is

used) Only if ccBPM is used:

ARV_WORKITEM_WRP (archiving of work items, only if ccBPM is used) ARV_WORKITEM_DEL (deletion of archived work items, only if ccBPM is used) SWWERRE (restart of erroneous ccBPM process, only if ccBPM is used) SWWDHEX (monitors deadlines of ccBPM processes, only if ccBPM is used) SWWCLEAR (deletion of job logs, only if ccBPM is used)

7.7.2 Jobs with a fixed ABAP program name

Log in to your Integration Server and call transaction SM37. If you have used a dedicated user for all housekeeping jobs, enter this user. If you have used different users, search for the ABAP program names provided in the following checklist. This is needed because the choice of the job name is free for these jobs.

RSXMB_RESTART_MESSAGES (automatic restart of erroneous, asynchronous messages).

RSWWWIDE (deletion of work items if not archived, only for ccBPM) RSWF_XI_INSTANCES_DELETE (deletion of archived work items, only if ccBPM is

used) SXMS_PF_REORG (reorganizes performance data) SXMS_PF_AGGREGATE (aggregates performance data) SXMS_REFRESH_ADAPTER_STATUS (refresh of outbound adapter status, only if the

Idoc adapter and BPE are used) Only if alerting is configured:

RSALERTPROC (deletion of alert and alert logs from database)

7.7.3 Background jobs running on the J2EE engine

Also on the J2EE engine a number of background jobs are running which have to be monitored regularly.

Procedure



Log on to the RWB and call your central or decentral Adapter Engine in the Component Monitoring. Select the button Background Processing. A new window opens displaying the background processes being executed in your Java environment. Check the log of the deletion job. This job deletes PI messages from the persistence layer of the J2EE engine and runs per default once a day. Verify a successful execution of the job and the number of messages it processed. If archiving is used on the Java side also check the successful execution of the Archiving job. Also the restart job on the Adapter Framework can be monitored here. Per default this job is not scheduled.

7.7.1 Adapters in the Integration Server: IDoc Adapter

SM58 this transaction only shows outgoing tRFC calls. For problems with incoming IDocs it is necessary to check the sending systems.



7.7.2 Sync-Async Bridge

The Sync/Async Bridge (bridge between synchronous and asynchronous communication) is used if for example a synchronous request needs the information of an asynchronous function module. It is not possible to call it directly and thus you have to define a sync/async bridge. Technically it is realized via ccBPM.

7.8 IDoc Packaging Monitoring IDoc Packaging can be used to collect outbound IDocs and to send them in a package rather than one by one to the receiving system

Transaction: IDXP

7.9 Message Packaging Monitor



1) You can switch on the Integration Engine parameter RUNTIME-> LOGGIN_AMF_ERR in transaction SXMB_ADM to receive some packaging information in transaction SXMB_MONI. When this parameter is set you can determine the package ID used for a message in field EOReferenceOutbound in the Runtime header of a message. 2) Also new transactions were introduced to monitor the packaging behavior. Via transaction XMSPKSTATCNF you can configure:

How statistical information will be collected. The level of aggregation desired and the reorganization information.

After having configured Message Packaging Monitoring you can use transaction XMSPKSTATMON to do the actual monitoring. This transaction contains very detailed level information about packaging behavior.

Transaction: XMSPKSTATMON

8 Business Activity Monitoring (BAM)

Tying Strategy to Business Operations. Source SAP



A holistic performance management initiative mandates that you seamlessly integrate and synergize both levels operational and strategic. This approach serves your current and future business-planning mandate by helping you differentiate your company through innovation as you increase efficiency by optimizing business processes.



9 Monitoring PI with Solution Manager SAP Solution Manager is used to manage the entire SAP solution landscape, which seems to be a challenging task. Companies can minimize risk and increase the reliability of their IT solutions. SAP Solution Manager helps reduce the TCO throughout the solution life cycle. PI monitoring functionalities can be integrated within Solution Manager.

9.1 Monitor Diagnostics agents status SAP introduced a number of monitoring tools that can be used to monitor your solution landscape. Solution Manager Diagnostics (SMD) and Wily Introscope are two important tools for monitoring the J2EE stack of your PI solution. Both tools are connected to PI via so-called agents which collect the data required for analysis. Therefore, it is essential to check the status of these agents from time to time. This can be best done by logging into the corresponding systems and checking the collected data.

9.2 Solution Manager Diagnostics Agent(s) Start your Solution Manager Diagnostics. Choose your Solution Landscape and the system to be monitored and navigate to Root Cause Analysis > Workload > Java > Java Memory Analysis. This path might differ depending on the SP used. Select all instances of your installation. Choose a suitable timeframe (e.g. last week) and press the Analyze button.



If the data cannot be displayed or is missing for some period of time troubleshoot your SMD agent.



10 CCMS Computing Center Management System

Monitoring and administration of SAP System Landscapes Configuration possible within Runtime Workbench

10.1 Monitoring component XI Use transaction RZ20 to access the CCMS Monitor sets. Navigate to SAP CCMS Monitor Templates -> Exchange Infrastructure (figure 1) to open the XI monitoring view (figure 2).

Figure 1: SAP CCMS Monitor Templates

Figure 2: Exchange Infrastructure monitoring



The Exchange Infrastructure component comprises the following sub components (figure 2): IEngine__, QRFC Queues, Java Components and __Business Process Engine

Integration engine The integration engine item contains the following two sub items: system errors and application errors (Figure 3). The section System errors comprises several components which in turn contain several sub components that need monitoring.

Figure 3

Thresholds can be assigned to these sub components. Click on the sub component and select properties (or press Shift+F7). The screen Monitoring: Properties and Methods is displayed (figure 4). Using the Change button, the thresholds can be adapted.

Figure 4



After saving this information, the sub components are displayed again. Select a sub component, and then select Start analysis method (Cntr+F10). The following screen contains information (mostly XML messages with errors) that can be further analyzed (figure 5).

Figure 5

It does not make sense to describe all these components in detail in this document, as this information is customer specific.

10.2 Availability Monitoring Availability monitoring can be divided into Heartbeat monitoring and Availability monitoring. This can be done using GRMG (Generic Request and Message Generator) and CCMSping.

Figure 6

This section in CCMS can be reached via the SAP CCMS Web Admin Monitor Templates (figure 7)



Figure 7

CCMSPing must be installed via an agent on each SAP server that is monitored via the CEN.

When double clicking on Availability: Web Services (GRMG), the screen for GRMG monitoring is opened (figure 8)

Figure 8

In this monitoring template, all java components are monitored. For XI, these are a.o. the SLD, Integration Directory, Integration Repository, Runtime Workbench, Java Adapter engine and of course all other java components.

When you click on the sub components, and then on the button Start analysis method (CNTR+F10), the Generic Request and Message Generator is displayed (figure 9). In this screen, you can indicate what java components have to be monitored by means of a periodic XML request.



Figure 9

Since such a periodic XML request is sent to the java components, the availability can be calculated. Figure 10 shows that the SLD was 100% available during the monitored period.

Figure 10



11 Administrator Monitoring Functions

11.1 JAVA monitoring environment

Netweaver Application Server Java (http://:/index.html)

SAP NetWeaver Administrator A powerful administration, configuration and monitoring tool, which bundles key administrative tasks to keep your SAP NetWeaver system landscape running. SAP NetWeaver Administrator can be used in a central or local scenario. Here you access the local NetWeaver Administrator.



11.2 SAP Management Console

Netweaver Application Server Java (http://:/sapmc/)

The SAP Management Console (SAP MC) provides a common framework for centralized system management. It allows you to monitor and perform basic administration tasks on the SAP system centrally, thus simplifying system administration. Using the SAP MC you can:

Monitor and control (start, stop, or restart) the SAP system and its instances with a single tool.

Display SAP log and trace files, start profiles, instance parameters, the system environment, SAP environment, Internet Communication Manager (ICM) queue statistics, and so on.

Display and control Java processes. Monitor system alerts. Display the list of all access points to an SAP system. Display information about the AS Java threads, sessions, caches, aliases, Enterprise

JavaBeans (EJB) sessions, remote objects. Display Java Virtual Machine garbage collection and heap memory information of the

application server. Save the current console configuration in a file to reuse it later or to forward it to other

users.

Start third-party tools (such as Telnet), if available, to manage an application server



12 Proxies ABAP-proxies can be used for interfaces from and to SAP systems. These are generated ABAP classes that can be implemented for sending and receiving PI messages. ABAP proxies offer the advantage of direct communication between the R/3 application server and the PI Integration Engine. The Adapter Engine is not used, which always improves performance. When using inbound proxies, Fault Messages can be used. These can feed back the status of the receiving system into PI, which then becomes visible in the PI monitoring tools. When processing proxies, the Analysis Application Log is often used. This is a standard SAP tool, for logging applications. In case of errors in the ABAP proxies, this is visible in the Monitor for Processed XML Messages in the sending and/or receiving system.

Monitoring tools Monitor for Processed XML Messages Analysis Application Log

Automation Since implementing a proxy is always a customer-specific task, it is possible to think about errors alerts in the design phase. The Alert mechanism can be used for this.



13 Third Party Monitoring Tools

13.1 HP OpenView HP OpenView is a portfolio of software and services that help companies manage all aspects of their enterprise over the Internet, from Hewlett Parkard. This popular suite of software applications assists in the network management of an organization's IT infrastructure and IT assets. Besides including many optional software modules developed by HP, the HP OpenView can also be integrated with third-party products and software components connecting well-defined framework and communicate with one another.

HP OpenView is a family of modular, integrated products that can be assembled to address the individual management challenges of each unique SAP environment. HP OpenView complements the management tools provided by SAP, including the SAP Solution Manager and the SAP Computer Center Management System (CCMS). While SAP Solution Manager is optimized to manage the SAP application life cycle from a business perspective (e.g. customization, deployment, support), HP OpenView products are optimized to integrate the SAP environment into the overall business-centric enterprise IT service management solution. Working together, information coming from SAP CCMS can be routed to HP OpenView Operations where it is aggregated with other information collected by HP OpenView Operations. HP OpenView Operations is also able to route information to SAP Solution Manager, enabling IT infrastructure information and additional integrated non-SAP application information to be seen within the SAP application or business process context. This allows for smooth process integration between the IT-centric operations and administration teams and the SAP-centric teams. Both teams share the same view of the environment.

13.2 Gensys Gensys 7 supports IT departments and Service Providers in documenting, monitoring and managing complex IT infrastructures, even if these are external to your own organisation



13.3 BMC BMC solutions help customers implement Business Service Management (BSM) and ITIL processes. BMS solutions support all major ITIL processes, starting with a best-in-class configuration management database (CMDB), closed-loop change and configuration management processes, incident and problem management, and the service desk. BMC solutions also integrate with SAP Solution Manager. BMC solutions focus on supporting ITIL processes throughout the entire environment including SAP.

13.4 ARIS Process Performance Monitoring

ARIS PPM provides you with a key technology to assess your business processes in terms of speed, cost, quality, and quantity and to identify optimization opportunities. ARIS PPM continuously optimizes internal and external business processes, thereby making a key contribution to business success. The software is also successfully used by individual departments to monitor service level agreements relating to core processes, such as order processing or maintenance and upgrade. Process discovery delivers graphical visualization of the performance



of business workflows, down to individual transaction level. Best practices are thus revealed and can be reused.

13.5 Seeburger Message Tracking Tool

Seeburger MessageTracking is a business integration server component designed to enable specialist staff / business partners to perform easy research on, and submit status queries about, electronically exchanged messages such as orders, delivery papers etc.

Configuration of search mask



Search Query

Search results

Detailed Message information



Detailed View

Print or download



14 Appendix

14.1 XI readiness check

The communication and accessibility of these components can be checked using the XI Readiness Check (SAP Note 817920 XI/PI Readiness Check). However, the Readiness Check points at errors in and between the tools that might lead to errors in exchanged messages later on, but it does not specifically monitor a PI system for erroneous messages or performance problems.

14.2 Activate Message overview component

Message overview not activated for component 'Integration Engine CXI'; see SAP Note 1031773

14.3 PI Monitoring with SAP NetWeaver Administrator

http://help.sap.com/saphelp_nwpi71/helpdata/en/45/c7ca8e89e45592e10000000a1553f7/frameset.htm

14.4 Interface monitoring with Solution Manager

http://help.sap.com/saphelp_sm32/helpdata/en/2e/df0742af7f6324e10000000a1550b0/content.htm

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/04c6d8ea-0c01-0010-698f-f670daea40a7

http://help.sap.com/saphelp_sm32/helpdata/EN/d7/28cbcf6dfd455ca8257bf5939a7c48/content.htm

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70cd1603-6761-2b10-f0bf-8dd799ef7263



15 Useful links

Process Integration Monitoring: http://help.sap.com/saphelp_nwpi71/helpdata/en/9a/701f428303ca7ee10000000a1550b0/frameset.htm

Process Integration 7.1 Trouble shooting guide: http://service.sap.com/~sapidb/011000358700000063822008E

SAP course BIT480 - PI - Operations http://www.sap.com/services/education/curriculum.epx?context=%5b%5bBITPIT1%5d%5d%7c

PI Admin Check: https://websmp202.sap-ag.de/~sapidb/012006153200000666252007E/Admin_Check_Version2.pdf

Nothing speciifc to support but here are the steps for error handling

Step-By-Step How to configure https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2328

Trouble shooting in Alerts https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2327

Triggering XI Alerts from a User Defined Function https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/4077

Alerts from adapter modules https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/5084

Alerts with variables from the messages payload https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1382

How to raise alerts from ABAP Proxy https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/5447

Documents

Monitor SAP PI ASUG para interfaces SAP PI Implementadas