Click here to load reader

PI Monitoring

  • View
    911

  • Download
    2

Embed Size (px)

Text of PI Monitoring

Session ID: BPI208 Process Integration Monitoring

Prasad illapani, SAP Labs, LLC Andreas Stolz, SAP AG

Learning Objectives

As a result of this workshop, you will be able to:Utilize the CCMS Alert Monitor for Process Integration Make use of the SAP Alert Framework for PI Configure and use the PIs Message Performance Measurement Use TRex for Message Search

SAP AG 2005, SAP TechEd 05 / BPI208 / 3

Motivation Monitoring is a crucial part of an Operation Concept Monitoring should coverAvailability of your Landscape Components Alert error situations

The following Monitoring Tools are available for the Exchange Infrastructure 3.0CCMS Monitoring Alert Framework Runtime Workbench

SAP AG 2005, SAP TechEd 05 / BPI208 / 4

Process Integration and CCMS Process Integration and Alert Framework Additional Techniques

Overview SAP WebAS Java CCMS Configuration CCMS Configuration for Process Integration GRMG Availability Monitoring

XI Architecture Overview

Central MonitoringXI All-in One Server

Integration Directory & Integration Repository

Integration ServerBusiness Process Engine

Integration Engine

System Landscape DirectoryXIProtocol

Adapter EngineXI Protocol

RosettaNet,

Adapters + Connectivity

Local Integration Engine Proxy Runtime Proxy generation RFC/IDoc metadata import Proxy

IDocs RFCs

File DB JMS

3rd Party Apps

Apps of Business Partner

Partner Connectivity Kit Apps of (small) Business Partner

SAP Web AS 6.20

SAP System

SAP AG 2005, SAP TechEd 05 / BPI208 / 7

XI 3.0 Components in SAP Web AS 6.40HTTP(s) HTTP(s)ICM Central Monitoring

J2EE XI ToolsIntegration Builder (IR, ID) Runtime Workbench

ABAP

Business Process Engine JRFC

Mapping runtime

Integration EngineAdapter Engine SLD

OpenSQL for Java SAP AG 2005, SAP TechEd 05 / BPI208 / 8

OpenSQL for ABAP

Central Monitoring

Message Monitoring Component Monitoring Performance Analysis Message Alerting

PMI CCMS

Runtime Workbench

System Landscape Directory

Alerting Framework

Integration Server (SAP Web AS 6.40)Business Process Engine

Integration Engine

SAP ApplicationSAP Web AS 6.40 using XI proxies

Adapter Engine

(local) Adapter Engine

J2SE Adapter Engine

SAP AG 2005, SAP TechEd 05 / BPI208 / 9

CEN Central Monitoring System For each remote system, define 2 RFC destinations in Transaction SM59:for collecting data for executing analysis methods.

To register a remote system, execute Transaction RZ21, select Technical Infrastructure Configure Central System Create Entry for Remote System.

SAP AG 2005, SAP TechEd 05 / BPI208 / 10

Overview SAP WebAS Java CCMS Configuration CCMS Configuration for Process Integration GRMG Availability Monitoring

J2EE Specific CCMS Configuration In Transaction RZ21 create the CSMREG User and the Start File CMSCONF for the CCMS Agent Installation.

SAP AG 2005, SAP TechEd 05 / BPI208 / 12

Register CCMS AgentUsing the Visual Administrator register the CCMS agent at the resp. Abap Stack. Select Dispatcher Services Monitoring. On the CCMS Agent Configuration Tab enter the Local Administrators and CSMREGs password.

SAP AG 2005, SAP TechEd 05 / BPI208 / 13

Verify CCMSR Agent Registration and StatusVerify that the System Group J2EE_Systems is created and the actual J2EE System is added. Transaction RZ21, Menu Technical Infrastructure Configure Central System Maintain System Groups

Verify that the Agents Status is Online. Transaction RZ21, Select Display Overview for Agents for Local System.

SAP AG 2005, SAP TechEd 05 / BPI208 / 14

J2EE Monitoring Template

SAP AG 2005, SAP TechEd 05 / BPI208 / 15

Overview SAP WebAS Java CCMS Configuration CCMS Configuration for Process Integration GRMG Availability Monitoring

Activation of CCMS Monitoring

Activate CCMS Monitoring by setting respective configuration parameter in Transaction SXMB_ADM

Change the value for Parameter CCMS_MONITORING to 1 in the Specific Configuration

SAP AG 2005, SAP TechEd 05 / BPI208 / 17

CCMS System Group Maintenance with TC RZ21 Create system group ExchangeInfrastructure_Systems in TC RZ21, Technical Infrastructure Configure Central System Maintain System Groups

Create System Group Add Systems

SAP AG 2005, SAP TechEd 05 / BPI208 / 18

Activation of qRFC - PrerequisitesActivate qRFC monitoring. In TC RZ21, select Technical Infrastructure Local Method Execution Activate Background Dispatching.

SAP AG 2005, SAP TechEd 05 / BPI208 / 19

Adapter EngineActivate forwarding of Adapter Framework alerts to the CCMS Alert Monitor via the SAPCCMSR agent. In the Visual Administator select Server Services SAP XI AF Core. On the Properties Tab enter true as the value for parameter CCMSEnabled.

SAP AG 2005, SAP TechEd 05 / BPI208 / 20

XI Monitoring TemplateAccess PIs CCMS Monitoring template by running either TC RZ20 or TC S_B6A_52000011 in folder Exchange Infrastructure: Monitoring of personal user menu.

SAP AG 2005, SAP TechEd 05 / BPI208 / 21

Overview SAP WebAS Java CCMS Configuration CCMS Configuration for Process Integration GRMG Availability Monitoring

GRMG (Generic Request and Message Generator) Framework

(An example of GRMG scenario)

SAP AG 2005, SAP TechEd 05 / BPI208 / 23

Activation of heartbeat monitoring- Prerequisites To activate the heartbeat monitoring for Java components, configure the socalled GRMG customizing file. For further information please refer to SAP Note: 634771, which includes the PI specific GRMG customizing template.

SAP AG 2005, SAP TechEd 05 / BPI208 / 24

GRMG Configuration file upload - Prerequisites To upload the GRMG configuration file, execute TC: GRMG

SAP AG 2005, SAP TechEd 05 / BPI208 / 25

Customizing GRMG Scenarios To monitor the availability of an instrumented application with GRMG, you must first customize and start the corresponding GRMG scenarios by using TC: GRMG

SAP AG 2005, SAP TechEd 05 / BPI208 / 26

Adjusting Frequency for individual ScenariosBy default, GRMG availability monitoring is performed every ten minutes for all monitored scenarios, you can change this by using TC: RZ21

SAP AG 2005, SAP TechEd 05 / BPI208 / 27

XI CCMS Heartbeats

SAP AG 2005, SAP TechEd 05 / BPI208 / 28

Demo

Demo

SAP AG 2005, SAP TechEd 05 / BPI208 / 29

Process Integration and CCMS Process Integration and Alert Framework Additional Techniques

PI and Alert Framework - Configuration Display Alert Framework Alerts in CCMS

Alert Framework (ALM) and PI Using the Alert Framework PI can generate Alerts for specific Sender / Receiver / Interface combinations (Alert Rules). Different contact groups can be alerted based on Alert Categories. Alert Rules are assigned to Alert Categories. The Alert Framework is a standard NetWeaver functionality. Alerts can be delivered using several channels, like Email, SMS, Pager (SAPConnect). As a prerequisite End-to-End Monitoring (Process Monitoring Infrastructure PMI) must be configuredUntil NW 04 SP 13 including, from SP 14 on the Alert generation does not depend on PMI anymore

SAP AG 2005, SAP TechEd 05 / BPI208 / 32

Activate Required ICF ServicesTake care that the ITS Plugin, the ALM related ICF Services, and required ICF Services are activated. Start Report RSXMB_ACTIVATE_ICF_SER VICES in TC SE38. Refer to SAP Note: 736312.

SAP AG 2005, SAP TechEd 05 / BPI208 / 33

End-to-End Monitoring ConfigurationIn the Runtime Workbench select Configuration. For generating alerts set the monitoring level to at least medium and save the entries. In the End-to-End Monitoring section press button Further Settings, set the job frequency, and activate the monitoring. Verify that a background job with a cryptic name is created in TC SM37. The job executes the Abap Report SPI_PS_ASSEMBLE_DSP.

SAP AG 2005, SAP TechEd 05 / BPI208 / 34

Report SXMSALERT_PROCESS_DATA_GETThe Report SXMSALERT_ PROCESS_DATA_GET reads the Alerts from the assembled PMI data and reports them using the Alert Framework. Schedule the Report as a periodic background job in TC SM36. Align the job period with the End-to-End Monitoring job period.

SAP AG 2005, SAP TechEd 05 / BPI208 / 35

Alert Categories IAlert Categories are container for some kind of alerts. Additional information like alert texts and subsequent activities as well as recipient lists are maintained per Alert Category. In the Runtime Workbench in section Alert Configuration press the button Create Alert Category. On the following screen maintain an Alert Category.

SAP AG 2005, SAP TechEd 05 / BPI208 / 36

Alert Categories II Container Elements for various Message Header information are available for PI Alerts. These Container Elements are filled at runtime with Message specific information and are used within the Alerts short and long text, e.g.Container Element SXMS_MSG_GUID returns the Message ID Container Element SXMS_FROM_INTERFACE returns the Sender Interface

Subsequent Activities for PI Alerts by default contain links for the resp. message to theMessage Monitoring End-to-End Monitoring

Recipients could be identifiedas Fixed Users via User Roles via Self-Subscription based on User Roles

SAP AG 2005, SAP TechEd 05 / BPI208 / 37

Alert RulesAlert Rules define the error situation which raises a specific alert. One Alert Category can contain on

Search related