02 Overview EPMonitoring v2 - archive.sap.com

1

? SAP AG 2002, Title of Presentation, Speaker Name 1

Course Structure

IntroductionEP 6.0 Portal

Overview EP 6.0 Monitoring

Overview CCMS/ Solution Manager

Installing Monitoring Infrastructure

CCMS Customizing

How to support EP 6.0

Questions & Answers

2


At the conclusion of this unit, you will be able to:

Overview: Unit Objectives

? Understand the difference between supportability and manageability

? Explain the monitoring concept of EP 6.0

? Know the monitoring infrastructure of EP 6.0

? Describe the monitoring landscape

? List the support & monitoring features and tools

? Define hardware and software requirements for EP 6.0 solution monitoring

3


Overview: Business Scenario

?A customer needs to understand the monitoring infrastructure of EP 6.0. You need to explain EP6 regarding? the difference between supportability & manageability? the monitoring concept? the monitoring landscape? the monitoring tools

? hardware and software requirements

?Which information and arguments do you share with the customers ?

4


Overview: Monitoring EP 6.0

Overview

EP 6.0 Portal

Monitoring Landscape EP 6.0

Supportability vs. Manageability

Monitoring Features and Tools

Monitoring Concept EP 6.0

Hardware and Software Requirements

5



For 1st and 2nd level support: Tools to support problem management (Error analysis)

Tools to handle regular monitoring tasks e.g. to ensure system stability

Tools to support regular maintenance tasks e.g. upgrading

Central Configuration Stores

Availability of EP components and prerequisites

Tools for Performance Analysis

Logging & Tracing capabilities

Remote connectivity

Requirements

Continuous System Maintenance e.g. Configuration Management, Change Management, Problem Management, Backup & Restore, Monitoring, Reporting statistics

Support for customer systems in case of product or configuration errors (remotely & onsite)

Tasks

System AdministratorsSAP SupportTarget group

ManageabilitySupportability

Goal of supportability => establish a support infrastructure forSAP‘s Java applications at customer site

6


Supportability: Features & Requirements

?Enable support organization to receive all relevant system data quickly? Centralize Configuration Stores? Component/ content object versions

?Enable the support to easily do a detailed Performance Analysis? JARM Instrumentation? Single Activity Tracing

?Enable the support to check availability of the portal and integratedsystems? Technical and Scenario Heartbeats through GRMG

?Provide the support with a central place for logging & tracing? Alerting through CCMS and LogViewer to access logs from a central point

?Establish Remote Connectivity to Portal Server

?Improve supportability by providing a central monitoring tool? Integration into CCMS? Instrumenting CCMS Agents?Warnings and Alerts over CCMS

7


Which components need to be monitored?

?Which parts of the portal landscape need to be monitored?

?Which parts of the portal can be monitored?

8


Minimal production landscape EP 6.0 with maximal options

host1host1

J2EEJ2EE

core

host2host2

host3host3

LDAP

DocumentRepository

DB

PCDPCDWCMWCM

BasisServicesBasisServices

PCDPCD

UMUM

PRTPRT

CM

Web ServerWeb Server

TREXTREXInQMyPlugIn

Fir

ewal

l

Legend:

x requires y

DB schema

host4host4

UnificationUnification

SAP unifiers

IISIIS

Business Objects

DB/2

DB unifiers

OracleOracleMS SQLMS SQLDB/2DB/2

MS SQL Oracle

SAP R/3SAP R/3BWBW

host7host7

SAP BWbackendSAP BWbackend

host8host8

SAP R/3backendSAP R/3backend

EPPlugIn

TREXengineTREXengine PythonPython

TREXIIS (Windows)Apache (Solaris)

TREXIIS (Windows)Apache (Solaris)

TREXPlugIn

Fir

ewal

l

Monitoring WebServer Logs

Monitoring Trex

Monitoring any host

Monitoring J2EE (cluster)

Monitoring EP & its core components

Monitoring LDAP Server

Monitoring DB

Monitoring backend connectionsMonitoring CM

Monitoring DB

?Monitoring WebServer Logs

?Monitoring EP and its core components: Portal data reported into CCMS is for example

?Configuration parameters of SAPJ2EE, PCD, UME, PRT and KM

?Version Parameters of SAPJ2EE, PCD, UME, PRT and KM

?Service Status of SAPJ2EE, PRT, UME, PCD and KM services

?JARM data about portal threads,

?Availability of processes (java-process/SAPJ2EE Dispatcher/ SAPJ2EE Server) and components like cluster nodes, backend connections

?Logfile monitoring for any registered log

?Monitoring DB*:

?Availability of processes

?Logfile monitoring

?Monitoring LDAP server*:

?Availability of processes

?Logfile monitoring

* Process monitoring is handled by SAPOSCOL, which supports common UNIX and Windows platforms.

9


Technical Infrastructure Architecture

Inner Firewall

Outer Firewall

Browser, PDA, etc.

Web Server

Web Server

Web Server

Portal Server

(incl. CM)

Portal Server

(incl. CM)

Portal Server

(incl. CM)

Notification

http/https

Web Server

UnificationServer

Retrieval &Classification

(as part of KM platform)

ClusteredCorporate User

Management

ClusteredDatabase

Load Balancer

Web Server

http/https http/httpshttp/https http/https

Persistence

Engines

Retrieval & Classification

Index

http/https

10


Portal Framework

Connector FrameworkConnectors

Information SourcesDocuments AppsSAP R/3 EIS Databases Web

User Management Engine

Unification

Application Unifiers

Database Unifier

KnowledgeManagement

Collabor-ation

TREX

CM

Portal Runtime

Portal Components Portal Services

Logical Components

Browser, Devices

User Persistence Store

PortalDatabase

Backend Systems

SAP Enterprise Portal 6.0

Portal ContentDirectory

PageBuilder

UserManagement

Admin Tools

Connections to Backend

Monitored EP components

? Portal Runtime, Portal Server: Portal Runtime is an extension of SAP J2EE, and hosts Portal Applications which can contain Portal Components and Portal Services. The Portal Server is a logical environment that runs on the Portal Runtime. PRT needs a storage mechanism to keep its operations alive at runtime. The Portal Content Directory provides it a reliable runtime storage facility, implemented on a database, called the Portal System Database.

? Portal Components: Java code that executes according to user requests and generates output (depending on the content type in the request) for the client. Example is the Application Repository that stores data about components and services. Page Builder that assembles pages, layout and fills them with content as per a request.

? Portal Services: Portal services enable interoperability in the PRT among several other services or Portal components. For instance, Content Service obtains various properties from the PCD for the operations of the PRT. Then there is the iView Service that obtains the set of properties for an iView per the request.

? Portal Content Directory:Also stores Portal Application data (deployable PAR files, and application meta-data, configuration data. It is a static component, it has no operations of its own. PRT uses the PCD for its storage needs during runtime.

? User Management Engine:Connects to a central storage for user related data. This storage is referred to as the User Persistence Store. The UPS can be a database, a directory server, such as LDAP, SAP R/3 users or a text file.

? Information sources, the origins of data and information that form the content presented.

11


Technical Components

Web Server

Unification

User Persistence Store

Portal

Content Management

Portal Framework

Web Server

Unifier 1

Web Server

Unifier 2

Realtime Collaboration

Retrieval & Classification

PortalDatabase

Persistence

Applications, Information, Services

Unification Server

Index Server

Web Server

Portal Runtime

Connector Framework

Java App Server (SAP J2EE engine)

Backend Systems


Browser, Devices

12


Portal Applications

Basic Building Blocks

?The Portal Runtime (PRT) resides on the SAP J2EE Engine.? PRT hosts portal components (UI-relevant, e.g. iViews) and portal

services (general functionality providers).

SAP J2EE Engine

WebApps/Servlet Container

Portal Runtime (PRT)

Portal Services

Resource Adapters EJBs

Basic Portal Building Blocks

Basic SAP J2EE Building Blocks

Portal Components

? Running on SAP J2EE Engine, the Portal Runtime (PRT) hosts Portal applications which can contain Portal components and Portal services.

? A Portal component is custom JAVA code that is executed according to user requests and generates HTML output for display on the client. Components are requested directly or indirectly by clients during runtime. Output generated by a component is based on a set of properties in the Portal Server. The set of properties is provided by an iView.

? Portal services expose functionality to portal components and other services.

13


Portal Content Directory

PCD: Logical Layers

Semantic Portal Objects? Portal Services using the

PCD as storage mechanism

? Describe information of portal content in form of metadata

?Generic Layer? Object model hides

business/portal semantics? Provides persistence API

for semantic portal objects? Hierarchy of “folders” with

attributes

?Persistence layer? Hides the physical

persistence? Supports several variants

for the persistence (different DB vendors, etc.)

Persistence Layer

Generic LayerPersonalization

ServiceSearch & Filter

Service

Delta LinksService

Version Service

RelationsService

NotificationService

Portal Database

Semantic Portal Objects

TransportService

ObjectCacheService

MessagingService

ACL Service

LockService

Portal Services

? A semantic portal object (=semantic application) wrapped around the PCD is a Portal Service that

?Hosts a specific semantic object

?Uses the PCD as its persistence

?Offers a client API

? The Semantic Layer is comprised of services (Portal services) that define metadata describing portal content objects, however the information of the origins of the content is located in the database implemented for the PCD. The semantic layer creates data for the generic layer.

? The Generic Layer consists of services (Portal Services). The services in the generic layer enable the portal to implement the content. The location of various portal objects such as, other services, components and other portal applications, form part of the implementation details. Origins of source code to be implemented are located in the database for the PCD.

? The Persistence Layer is also a service. It interfaces with the Generic layer and the database for the portal. This service obtains details of objects from the database, parses the information and then encapsulates it. The encapsulated information is obtained by the generic layer for further processing in the Portal Runtime.

? The PCD storage mechanism enables, content developers to concentrate on creating and adding business processes to the portal, without worrying about how it is implemented by the portal.

14



Overview

EP 6.0 Portal






15


Monitoring & Logging: Definition

?Monitoring? Display of the status, availability, performance, configuration, etc. of

the system and individual components.

?Logging? Regular output of messages to confirm that a certain action was

performed or triggered.

?Tracing? Output of errors and warning messages to help find and analyze

problems. Tracing is activated by the developer or by a member of the support desk team.

16


SAP Java Components(e.g. SAP Enterprise Portal)

Central MonitoringSystem

Monitoring: Agents for SAP Java Components

Log

Application

SAPCCMSR

Shared Memory

ApplicationSAPOsCol

SAP Solution Manager

SAP Solution Manager

SAPCCMSR = Agent for SAP Java ComponentsSAPOSCol = Operating System Collector

SAPCCMSR = Agent for SAP Java ComponentsSAPOSCol = Operating System Collector

Alerts are a central element of the monitoring. These quickly and reliably report problems - such as a value exceeding or falling below a particular threshold value, or an IT component being inactive for a defined period of time. To improve clarity, alerts are assigned certain colors - yellow for a warning and red for a problem - and a numerical value for the criticality of the problem.

Remote monitored components are included using CCMS agents. These have the following properties:

? Connection to the central monitoring system using RFC, to provide greater downtime security and universal usability

? Use of a push mechanism to proactively report alerts and data to the central system

? Integration of the SAPOSCOL operating system collector to transfer data for the operating system level (from CPU utilization and fill levels of file systems to details of individual monitored processes)

? Connection of systems with SAP Basis 3.X and components on which no SAP Web Application Server is installed

?Monitoring of any log files

17


Monitoring of non-ABAP components

?Monitoring of non-ABAP applications shall be realized by the following components: ? A central monitoring system (CEN): Required is an installation of WebAS 6.20.

As a basis component the CCMS is available by this installation. (For integration into the Solution Manager 3.1. an additional PlugIn has to be installed on the WebAs Server.)

? SAPOSCOL: The Operating System Resource Collector (SAPOSCOL) collects data about operating system resources, including ? Usage of virtual and physical memory? CPU utilization? Utilization of physical disks and file systems? Resource usage of running processes? Process monitoring

? SAPOSCOL makes the data available to various applications and all SAP instances on a host using a segment of the shared memory.? Dev_proc: This file is a configuration file for the SAPOSCOL.

? SAPCCMSR: The agent creates the RFC connection between the host and the central monitoring system (CCMS/ Solution Manager).

? Standalone LogViewer: The LogViewer enables you to centrally view log files written by the portal application.

? Jmonapi.jar: The SAPJ2EEEngine 6.20 is using the jmonapi.jar (JMON) to write monitoring data into the shared memory segment of the SAPCCMSR.

18


LogFile Monitoring

? Java-based applications write messages to log files. In complex applications, such as EP6, important messages can be distributed across significantly more than 100 log files. To ensure stable operation, these log files should be regularly checked for error messages.

? SAP provides a mechanism for automatically analyzing log files. The CCMS agent SAPCCMSR checks the log files every minute for preset search patterns. If the agent finds a pattern, it reports an alert to the central monitoring system. The administrator can be informed from there on the basis of the alert.

? As an administrator, you can see all of the checked log files in the Alert Monitor (transaction RZ20) of the central monitoring system. If an error occurs, you can expand the corresponding sub tree in the Log file Monitoring monitor, and obtain the name and path of the log file in which an error was logged from the Complete Name node. You can then view the entire log file in the central log viewer, and make appropriate repairs based on your analysis of the log.

19


EP System Logfile Monitoring - Example

Log Files

SAP J2EE

Portal

CM

Portal Server*

Log Files

Preprocessor

TREX Server*

Index Server

Queue Server

Name Server

Web Server

Portal Database*

User Persistence

Store*

Log Files

Log Files


SAP Solution Manager 3.1

SAP Web AS 6.20

*CCMSR Agent + SAPOSCOL installed on each server

20



Overview

EP 6.0 Portal






21


Central Monitoring

SystemCCMS,

SolMan 3.1

Shared Mem.SAPOSCOL

CCMS Agent

LOGFiles

OS resources

TREX Preprocessor

TREX Index Server

TREX Queue Server

TREX Name Server

WebServer

Shared Mem.SAPOSCOL

CCMS Agent

LOGFiles

OS resources

TREX ServerTREX Server

TREX Preprocessor

TREX Index Server

Shared Mem.SAPOSCOL

CCMS Agent

LOGFiles

CM

Portal

OS resources

SAP J2EE 6.20

div. Skripte

Shared Mem.SAPOSCOL

CCMS Agent

LOGFiles

CM

Portal

OS resources

SAP J2EE 6.20

div. Skripte

LOGFiles

OS resources

Shared Mem.SAPOSCOL

CCMS Agent

DB ServerDB Server

Oracle Server

div. Skripte

OS resources

Shared Mem.SAPOSCOL

CCMS Agent

LDAP ServerLDAP Server

Novell eDirectory

div. Skripte

Portal ServerPortal Server Portal ServerPortal Server TREX ServerTREX Server

EP System Landscape Monitoring - Example

22



Overview

EP 6.0 Portal






23


Portal Monitoring Features and Tools

?Portal Platform provides? JARM (Java Application Responsetime Measurement)? SAT (Single Activity Tracing)? GRMG application

?Monitoring features? LogFile Monitoring? Availability Monitoring

? GRMG Heartbeat

? Central Configuration Store? Parameter Reporting into CCMS

?SAPJ2EE 6.20 provides ? Jmonapi.jar? Logging API? LogViewer available in SAP J2EE 6.20

?WebAS 6.20 provides? CCMS ? Solution Manager

24


Portal UI: JARM – Request Summary

JARM as infrastructure for portal monitoring

? Here you find the most important performance data displayed via different categories: e.g.

?Accumulated Amount of Outbound Data: Amount of all out going data in byte.

?Time for all Requests: Overall amount of time used to proceed all requests in the backend system.

?Average Time of a Request: The average amount of time used to proceed a request in the backend system.

?Time Stamp of First Request: Start time of the monitoring.

? Please check the documentation for a detailed expalantion of the collected monitoring data.

25


Portal UI: JARM Request Overview

? Detailed view on a request can be received by clicking on the component name. Under Executed Components, all components in this request (main component including ins subcomponents) are displayed with the following information

?Component Name: Name of the main components or subcomponents

?Gross Time of Component: Total time of the component (including time for all subcomponents)

?Net Time of Component: Net time of a component (computed from its gross time less the gross time of the subcomponents).

?Amount of Outbound Data (Bytes): Amount of outbound data for the component

?Starting Time / Starting Date: Time when the component was started

?Nesting Level: Nesting level 0 corresponds to the main component. Nesting level 1 means that this component was called from the main component, etc.

26


Portal UI: JARM – Component Overview

? Here you find an overview of the portal components running in the cluster node that have the largest load on the resources. The components are displayed without taking the corresponding requests into consideration.

? Example: Calling the component overview tells you if a component only created a time load once, or if the component is generally slow and reduces system performance. A component can, for example, be slow the first time it is called. If it is called repeatedly, the net time will generally be shorter because data is kept in the cache.If you sort the slow components by their average net time and the average net time is approximately the same as in the first call, the component will generally reduce performance. In custom components you should check the coding in such cases.

27


Portal UI: JARM – Thread Overview

? An overview of the threads currently used by the portal applications in the cluster node is displayed here. The active threads and running components that are currently involved are displayed.

? The Thread Overview is a „snapshot“ of the data collected for the Request Overview and Component Overview. The current state of the thread is shown. It is not possible to display a history of the thread for the entire runtime of the request.

28


Portal UI: Logged On Users

? The Portal Runtime creates a session in the cluster node for each active user. This session is displayed in the overview of logged on users.

?Active User means: The user has a valid logon ticket/ a valid user management session exists for the user

? Configuration of this component can be done in the the service com.sap.portal.runtime.application.monitor (see above).

29


Portal UI: Activity Tracing

If SAT is enabled the file sat.trc.x is written in directory \\<server>\j2ee_xx\cluster\server\log

? You can sequentially record the activities of individual requests and their components for a defined period of time, and then analyze their performance and errors in the LogViewer of the SAP J2EE Engine.

? In a cluster environment, activity tracing is activated automatically for all cluster nodes.

? All trace data is written to file sat.trc.0 in directory <Installation_folder_SAP_J2EEngine>\cluster\server\log. New trace data is constantly added to this file.

? For details about the configuration, see the Administration Guide for the SAP J2EE Engine. You can find this guide at http://help.sap.com ? SAP NetWeaver ? SAP Web Application Server ? SAP Library ? mySAPTechnology Components ? SAP Web Application Server ? J2EE Engine

30


What is „GRMG“?

?GRMG is the abbreviation for “Generic Request and Message Generator”.

?GRMG allows external operational testing and monitoring of? a chain of technical components for availability (heartbeats)? a chain of business application processes/components? a mixture of both

? GRMG monitoring is able to distinguish between (overall) scenario errors and component test errors

? GRMG is HTTP based

?Checks in EP 6.0 SP1:? Availability of Cluster Nodes:? Availability of defined URL connection? Availability of Backend-Systems

Design of GRMG:

?GRMG consists of two parts:

?GRMG Framework:

? is embedded in CCMS

? is maintained by SAP CCMS administrator/developer

? sends a client request containing the test parameters against the GRMG Application

? receives test response from GRMG Application

?GRMG Application:

? is a callable application (built-in in JSP, Servlet, iView, etc.) on the server which contains the implementation of the scenario test

? has well-defined interfaces to receive GRMG requests and to send GRMG responses

?GRMG request and response are supplied in well-formed XML documents

31


Typical Web Server Situation

TX rz20 TX grmg

Web Server

GRMG Framework

GRMG application

Servlet

EJB

1

Servlet Engine

J2EE Server

SAP System (R/3)

SAP System (R/3)

CCMS Monitoring

3

2

45

8

6

7

9

10

11

1. Web Server transfers GRMG request as HTTP POST request to a servlet or iView on a servlet engine or PRT.

2. This request will be received and processed by a GRMG application (JSP, Servlet, iView) on the J2EE Server, Web Server or PRT.

3. The GRMG application tests a certain set of technical components or business processes (? GRMG Scenario): e.g. availability of EJBs, web pages, DB, SAP Systems (R/3), PRTs in cluster environment etc.

4. The results of the different checks are collected by the GRMG application and assembled in a GRMG response.

5. The GRMG response is transferred back to the GRMG framework – typically the contents of the GRMG response may be uploaded into the HttpServletResponse of the servlet or iView.

6. The GRMG framework in the CCMS interprets the response and displays the results in the monitoring tree of CCMS.

GRMG Framework (in the CCMS) (1) periodically sends GRMG request (2) to the (central)Web Server (3) which transfers to the Servlet Engine (4) the GRMG request by an HTTP POST (5). In the example the GRMG Application checks the availability of a SAP System (6) the availability of an EJB (7) and the availability of a Servlet (8). The GRMG Application sends back the GRMG response to the GRMG Framework (9,10). The result is then displayed in a CCMS monitoring tree (11).

32



Overview

EP 6.0 Portal






33


Software Requirements

Service Market PlaceJSTF Package

WebAS based monitoringsystem ? Basis Support Package ? 29

Included in JSTF package on SMPStandalone LogViewer 6.30

Included in JSTF package on SMPSAPOsCOL ?Version 20.79

Included in JSTF package on SMPSAPCCMSR ?Patch Collection 8/2003+

Regular Shipment of SAP EP 6.0SAPJ2EE Engine 6.20 PL 16+

Regular Shipment of SAP EP 6.0Enterprise Portal 6.0 SP1+

34


Where to find the supportability package...

?To ease the installation of the monitoring infrastructure you need to download an aditional package from SAP Service Market Place.

?Get the EP_Monitoring Package from SAP Service Marketplace - you canfind the current version in the following directory:

?SAP Enterprise Portal

-> SAP Enterprise Portal 6.0

-> Binary Patches

-> EP_Monitoring 6.0HP-UXSOLARIS...

?

35


Required Support Infrastructure

SAP Router

WANWANSAP

SupportSAP

Support

Via OSS

SAP Solution Manager 3.1 incl. Windows Terminal Server

SAP Web AS 6.20

Windows 2000 Advanced Server

Enterprise Portal 6.0*

DEV


INT


PROD

Windows-basedremote access

*On each server :-SAPOSCOL-SAP CCMSR Agent

36


Required Hardware for Support Infrastructure

?SAP Solution Manager and Windows Terminal Server on one server? Requires Windows 2000 Advanced Server

?SAP Solution Manager and Windows Terminal Server on two servers? SAP Solution Manager 3.1 based on SAP Web AS 6.20 running on

any platform supported by Web AS 6.20? Windows Terminal Server

? Requires Windows 2000 Advanced Server

37


Related Information

? “Enterprise Portal 6.0 System Landscape Monitoring – Best Practice for Solution Management” available on SAP Service Marketplace > Alias ep > Product Information > Enterprise Portal 6.0 > Documentation & More > HowTo Guides

? “EP 6.0 SP2 Solution Management” available on SAP Service Marketplace > Alias ep > Product Information > Enterprise Portal 6.0 > Documentation & More > Fundamentals

? Administration Manual EP 6.0 under help.sap.com

38


Overview: Unit Summary

You are now able to:

? Understand the difference between supportability and manageability

? Understand the support concept of EP 6.0

? Explain the monitoring concept of EP 6.0

? Know the monitoring infrastructure of EP 6.0

? Describe the monitoring landscape

? List the support & monitoring features and tools

? Define hardware and software requirements for EP 6.0 solution monitoring