8/13/2019 SAP J2EE Monitoring and Management for Administrators[1] http://slidepdf.com/reader/full/sap-j2ee-monitoring-and-management-for-administrators1 1/56 Astrid Tschense PM System Management, SAP AG SAP Java Monitoring and Management for Administrators Welcome to SAP J2EE Server Monitoring and Management for Administrators. This slide show presents you the tools SAP offers to monitor a system landscape with one or more J2EE Engines and JAVA applications running on the engines.
56
Embed
SAP J2EE Monitoring and Management for Administrators[1]
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
8/13/2019 SAP J2EE Monitoring and Management for Administrators[1]
! SAP AG 2003, TechED Basel 2003, SM102_EMEA, Astrid Tschense
Monitoring
Architecture
GRMG
Infrastructure
Availability in %,
Heartbeat
Uploaded GRMG
configuration file
J2EE EngineHTTP
Server
ABAP
Application
SAP J2EE
EngineGRMG
Application
SAP Web AS
GRMG
Application
J2EE
Server
<?xml version="1.0" …
<!DOCTYPE Customizing<!ELEMENT customizing …
<!ELEMENT control(grmg…
<!ELEMENT …
SAP Web AS
Availability Monitoring: Using GRMG
GRMG Structure
GRMG consists of two parts, both of which are required for a functioning GRMG
environment:
The GRMG infrastructure is part of the monitoring architecture of the Computing Central
Monitoring System (CCMS). Its task is to send a request (the GRMG request) to the
GRMG application, to receive its response (the GRMG response) and to display this
response in an Alert Monitor (RZ20).
The GRMG application reports two values: a general availability and the heartbeat.
Therefore the GRMG application runs a specific test especially programmed for thecomponent(s) in question. In case of the J2EE Engine the tested components are the
HTTP Provider Service, P4 Service, EJB Container and Web Services.
The GRMG infrastructure is monitored itself, too. This allows you to differentiate, if an
error occurs, between errors in the monitored component and errors in the GRMG
scenario itself.
8/13/2019 SAP J2EE Monitoring and Management for Administrators[1]
! SAP AG 2003, TechED Basel 2003, SM102_EMEA, Astrid Tschense
Appl icat ion
Client
J2EE
Engine
Database
Server
Problem Detection: Distributed Statistics Records
Processing time (1)
Database time (1)
Processing time (2)
Processing time (3)
Database time (2)
Response
time
User starts transaction
Server receives request
Server returns response
Client displays result
N e t w o r k
N e t w o r k
N e t w o r k
N e t w o r k
Wait time (waiting for a data base connection)
Wait time (JMS Queue)
‚black box‘
This detailed view is
offered with the
Performance Trace
In this graphic you see which times are recorded: The total response time begins whenthe server receives a request and ends when the server returns a response. The
whole right hand part of the graphic is a black box in the DSR view but can be seen
on the trace level we will talk about lateron.
8/13/2019 SAP J2EE Monitoring and Management for Administrators[1]
! SAP AG 2003, TechED Basel 2003, SM102_EMEA, Astrid Tschense
Problem Detection: Distributed Statistics Records
Content-
Server Collector Collector
DatabaseDatabase
Central System
ST03G
J2EE
6.30
Server Instance
Content-
Server StatisticsStatistics
FilesFiles
DSR
Service
Hourly data pull
for statisticsaggregation
Aggreg.
statistics
STATTRACE
Direct call for
last minutes‘ loadDSR
Collector
Non-aggreg.
Single recorddisplay
CCMSR
Agent
the J2EE Engine, the DSR Service is responsible for managing the DSRs. You can switch the
DSRs on and off in the Visual Administrator, the default is “on”.
e statistics records are transferred to the file system of the host. The CCMS agent reads thestatistics files. There are three display variants:
First is to display Collector Aggregates After the Hourly Collector Run
e DSR collector aggregates the data during the transfer in its hourly background run
(background job SAP_COLLECTOR_FOR_NONE
_R3_STAT). The statistics records are then stored in the database and displayed in the Global
Workload Monitor (transaction ST03G).
Second possibility is to display the Collector Aggregates Between Hourly Collector Runs
So that you do not have to wait until the hourly collector run to display aggregated statistics filesthe Global Workload Monitor (transaction ST03G) provides the Last Minutes’ Load function,
which allows you to aggregate and display statistical data during runtime without storing it in the
database.
ou can also display Raw Data as Single Records
With single record display, the raw statistical data is displayed in the transaction STATTRACE.
8/13/2019 SAP J2EE Monitoring and Management for Administrators[1]
! SAP AG 2003, TechED Basel 2003, SM102_EMEA, Astrid Tschense
Analyze Alerts: The Alert Browser
Alert browser
Doubleclicking a node shows
all corresponding alerts
The Alert Monitor has two views:
- Current status shows the present situation of the system.
- Open alerts shows the situation of the system in the past. This view is useful for analyzingany problems that occurred before the last system monitoring run.
The Current status view provides an overview of the current values of the systems that were
reported to the monitoring architecture. It displays the relevant values for all attributes, for
example, the performance value or the last report that was received.
The color of the monitoring object indicates its status, and is independent of any open alerts
that may exist for that MTE.
f you switch to the Open alerts view, i.e. the „History"-view, the system displays for each
monitoring object the most important, that is the most critical and the most severe, open alertregardless of the total number of alerts for that object.
You can set alerts to Complete once they have been resolved. The completed alert is then
removed from the list. After a certain time which can be adjusted, the open alerts are auto-
completed and removed from the open alerts display.
8/13/2019 SAP J2EE Monitoring and Management for Administrators[1]
! SAP AG 2003, TechED Basel 2003, SM102_EMEA, Astrid Tschense
Log Viewer Types
3 Types of Log Viewers:
Integrated Log Viewer, included in the Visual Administrator
! Online tool where all the logs written from the Engine and the
running applications are automatically registered
! Customizing the properties, switch Log Monitoring on...
Standalone Log Viewer for central Log Viewing
! Consists of Log Viewer Server and Log Viewer Client. Logs from a
System Landscape can be viewed centrally in one Standalone Log
Viewer Client, if one Log Viewer Server runs on every host.
Command line Log Viewer
Usage: lv.bat delivered with Standalone Log Viewer
! Only for viewing local logs on console
! Can be switched on while deployment
! Converts binary data into human readable data
og Viewer 6.30
he Log Viewer is a display tool for several kinds of log files written by the J2EE Engine or its
applications. There are three different versions available:
he Integrated Log Viewer within the Visual Administrator, the Standalone Log Viewer, and a
command line log Viewer.
he advantage of the Integrated Log Viewer is that all the logs written form the Engine and the
running applications are automatically registered, because the Log Viewer server listens to
logging.jar and makes every log file available as it is created.
he Log Viewer can parse the logging.jar list format into columns. That allows merging severalslogs together. The records have timestamps that impose an order.
n the properties tab of the Integrated Log Viewer the Log Monitoring with the central SAP
System can be switched on.
8/13/2019 SAP J2EE Monitoring and Management for Administrators[1]
! SAP AG 2003, TechED Basel 2003, SM102_EMEA, Astrid Tschense
Log Monitoring Architecture
Log Monitoring
To monitor the logs registered in the online Log Viewer you can
choose between manual and
automatic Log Monitoring Activate the function „Create CCMSR agent templates for log file monitoring“ (1)
and check whether the right log file directory is entered (default: prfclog\logmon)
Central System
RZ20
Reads
sapccmsr.ini-
file
Reads
templates
Scans log files
for patterns
SAPCCMSR
Agent
! Creates monitor tree
alerts for found patterns
Reads
logmon.ini-
files
Log Monitoring can be started in two ways, automatically or manually. You shouldchoose this depending on how many logs you want to monitor. To start the automatic
process you have to set the flag for „Create CCMSR Agent templates for log
monitoring“:
! The Log Viewer creates the template files, inserting the log file path name, the search
pattern, and the color value.
! The log file template index is updated and stored.
! Then the Log Viewer writes into the CCMS Agent .ini-file to search for the index.
! When the CCMS Agent finds an index of log .ini-files it reads the templates and
creates the nodes in the CCMS log monitor tree.
! The CCMS Agent begins monitoring the logs named in the ini-files for text patterns
specified in the templates.
! When the agent finds one of the specified text patterns, it notifies CCMS on the R/3
system via an RFC.
8/13/2019 SAP J2EE Monitoring and Management for Administrators[1]
! SAP AG 2003, TechED Basel 2003, SM102_EMEA, Astrid Tschense
Single Activity Trace/Cross-Component Trace
Single Activity Trace
Using JARM implementation, you can analyze a single (user's) request to
find performance problems in an application or to understand the logical
processing steps inside an application.
Cross-Component Trace
Each request gets a passport that is transmitted between all involved
components. If each component writes ist own Single Activity Trace, the
whole processing can be viewed in an assembled Single Activity Trace.
Log Viewer
J2EE
6.30
Server I
LogsLogs
J2EE
6.30
Server II
LogsLogs
Request
assembly= Passport
Single Activity Trace
If the JARM monitors that I’ve already introduced to you are programmed by the
developer and activated by the administrator, the whole program can be traced easily
for a single user’s request.
If the Single Activity Trace is switched on, the JARM data for this special request is
transferred to the logging API. The SAT is then displayed in the Log Viewer. With the
SAT you can analyze a single request inside an application. Each request is passed
on with a passport that shows the identity of the request. Each component a request
runs through writes a Single Activity Trace. Via this passport the SATs of thecomponents can be assembled to one cross-component Single Activity Trace.
SAT log files are displayed in a format different from general logs:
For example, the steps are displayed in hierarchical manner. You see in the structure
how deep a component is nested.
8/13/2019 SAP J2EE Monitoring and Management for Administrators[1]
! SAP AG 2003, TechED Basel 2003, SM102_EMEA, Astrid Tschense
Configuration of logging and tracing - GUI
Log Configurator Serviceallows ‚on the fly‘-configuration of logs and traces
Parameters:Controllers: specify the severity to generate more or fewer log/trace messages
Formatters: change the format of the message
Destinations: change the output destination
Log Configuration
The J2EE Engine provides an easy and complex mechanism for configuring thebehavior and output of logging without having to write a Java source code. The Log
Configurator Service provides means for runtime management of the logging and
tracing configuration For example, when you want to generate more or fewer log
messages, you can change the diagnosis level they are in, like switching from error
to info, debug and so on.
Sometimes, you may also want to change the output destination or even the format of
the message. These all can be specified separately and dynamically integrated with
the program. No recompilation of the source code is necessary.
Really important is that this can also be done for Java applications. So application logs
can be configured according to your special needs.
8/13/2019 SAP J2EE Monitoring and Management for Administrators[1]
! SAP AG 2003, TechED Basel 2003, SM102_EMEA, Astrid Tschense
SQL Trace via Log Configurator
The SQL Trace (Database Trace) can be activated in two ways:
1. You can switch the trace on in the Log Configurator of the Visual Administrator
•You can open the webpage http://localhost:<portnumber>/SQLTrace
...and view the traces in the Log Viewer :
SQL Trace
The SQL trace is an on demand log of all SQL statements that are issued against the
database through Native JDBC methods. The SQL trace can be switched on/off
dynamically in the administrator tool of the J2EE engine" Activating/Deactivating
SQLTrace. The log format is database independent. Besides the SQL statement text,
each log record contains information about the point in time when the statement was
executed, its duration, its input parameters and results (where applicable) as well as
certain context information (dbpool, user, etc.).
The SQL trace is especially useful for performance analysis. Mostly, performanceissues are caused by inefficient database accesses. In this case, SQL trace can be
used to show the issued SQL statements and their duration, thus helping to identify
inefficient SQL statements.
8/13/2019 SAP J2EE Monitoring and Management for Administrators[1]
! SAP AG 2003, TechED Basel 2003, SM102_EMEA, Astrid Tschense
SQL Trace via Webpage „SQL Trace“
2. You can open the webpage http://localhost:<portnumber>/SQLTrace
Jump into
details
ithin SAP J2EE Engine 6.30 there are two possibilities for toggling the SQLTrace:
rst is within the Visual Administrator as you have seen on the previous slide. In the Log
Configurator Service you can toggle the SQLTrace for the current cluster node.
new set of files is generated each time the trace is switched on. Thus recent traces are availabl
for further reference. The different sets are identified by a trace ID, which consists of a time
stamp. The global trace ID additionally contains the SAP J2EE Engine cluster node ID.
he second possibility is a Web application which acts as trace viewer:
he SQLTrace Web application is pre-deployed on the SAP J2EE Engine during installation. Usin
the Web application, SQLTrace can be enabled for a selected or all cluster nodes.QL trace files are not deleted automatically. Please use the web application to clean up traces
that are no longer needed. You do this under SQL Trace File Administration.
8/13/2019 SAP J2EE Monitoring and Management for Administrators[1]