Professional Documents
Culture Documents
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
2016 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP
SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are
provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in
Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 1 of 59
Table of content
1 Monitoring
1.1 Java System Reports
1.1.1 Monitoring Using Charts and Reports
1.1.1.1 Using the Predefined Charts and Reports
1.1.1.2 Composing Charts
1.1.1.3 Composing Reports
1.1.2 Managing Monitors with the Monitor Browser
1.1.2.1 Activating and Deactivating Monitors
1.1.2.1.1 Monitors Active by Default
1.1.2.2 Changing the Color Thresholds
1.1.2.3 Configuring a Monitor
1.1.2.4 Using the History Comparison Mode
1.1.3 Changing Settings and Exporting History
1.1.4 Troubleshooting
1.1.5 Reference Monitored Data
1.1.5.1 Applications
1.1.5.2 Kernel
1.1.5.2.1 Application Threads Pool
1.1.5.2.2 ClassLoader Manager
1.1.5.2.3 Cluster Manager
1.1.5.2.4 Configuration Manager
1.1.5.2.5 Licensing Manager
1.1.5.2.6 Locking Manager
1.1.5.2.7 Session Manager
1.1.5.2.8 System Threads Pool
1.1.5.3 Performance
1.1.5.4 Services
1.1.5.4.1 ConnectorService
1.1.5.4.2 Deploy
1.1.5.4.3 HTTP Provider
1.1.5.4.4 IIOP Provider
1.1.5.4.5 JMS
1.1.5.4.6 JMX Adapter
1.1.5.4.7 JNDI Registry
1.1.5.4.8 Keystore
1.1.5.4.9 Log Configurator
1.1.5.4.10 Memory Info
1.1.5.4.11 P4 Provider
1.1.5.4.12 Security
1.1.5.4.13 Security UME
1.1.5.4.14 TREX
1.1.5.4.15 Timeout
1.1.5.4.16 Transaction
1.1.5.4.17 Web Container
1.1.5.4.18 Web Services
1.1.5.4.19 WebDynpro
1.1.5.4.20 XI Security
1.1.5.4.21 XML Form Module
1.1.5.5 System
1.2 Monitoring and Displaying Log Files
1.2.1 Logging Features
1.2.2 Log Configuration
1.2.2.1 Log Configuration with the SAP NetWeaver Administrator
1.2.2.1.1 Configuring Log Controllers
1.2.2.2 Log Configuration with the Config Tool
1.2.2.2.1 Adding, Editing and Removing Log Formatters
1.2.2.2.2 Adding, Editing and Removing Log Destinations
1.2.2.2.3 Adding, Editing and Removing Log Controllers
1.2.2.2.4 Log Manager
1.2.2.3 Configuring Log Files Archiving
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 2 of 59
1.2.2.4 LOG
1.2.3 Log Viewing
1.2.3.1 Log Viewer
1.2.3.1.1 How to Work with the Log Viewer
1.2.3.1.2 Log Types and Formats
1.2.3.1.3 Predefined Views
1.2.3.1.3.1 Viewing Predefined General Views
1.2.3.1.3.1.1 Viewing Standalone Log Viewer
1.2.3.1.3.2 Viewing Predefined Development Views
1.2.3.1.3.3 Viewing Specific HTTP Views
1.2.3.1.3.4 Viewing Specific Logging Views
1.2.3.1.3.5 Viewing Specific Security Views
1.2.3.1.3.6 Viewing Specific Server Views
1.2.3.1.4 Filtering Logs and Traces
1.2.3.1.5 Creating, Exporting and Importing Custom Views
1.2.3.1.6 Searching for Logs and Traces
1.2.3.1.7 Customizing Columns for Logs and Traces
1.2.3.1.8 Downloading Log and Trace Records
1.2.3.2 Viewing Logs with the SAP Management Console
1.2.3.3 Command Line Log Viewer
1.3 Open SQL Monitors
1.3.1 Managing the SQL Trace
1.3.2 Evaluating SQL Traces
1.3.3 Connection Monitor
1.3.4 Catalog Buffer Monitor
1.3.5 Table Buffer Monitor
1.3.6 Sync Log Monitor
1.3.7 Table Statistics Monitor
1.3.8 Open SQL Statistics
1.3.9 Native DB Monitors
1.4 Monitoring Sequences
1.4.1 What Is a Sequence?
1.4.2 Choosing Selection Criteria
1.4.3 Checking the Sequence Overview
1.4.4 Analysis of Sequence Details
1.4.5 Rejecting and Restarting Sequences
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 3 of 59
1 Monitoring
Monitoring the AS Java system helps the administrator to identify resource bottlenecks or problems early on and to take any action that is required.
With the SAP NetWeaver Administrator, you can monitor the application server itself and the components and applications running on top of it. You can also
extend the functionality of your custom applications by adding monitoring capabilities to them, and thus to take advantage of the monitoring tools and
infrastructure for monitoring your own applications.
You can also access log files from one location which reduces the time required for error identification and correction.
Local Monitoring
Java System Reports
To monitor your local system, you use the SAP NetWeaver Administrator tool Java System Reports.
This is a problem detection and analysis tool that you use for the following:
The most important information is summarized in a set of predefined charts and reports. You can also view data from each single monitor in the monitoring
tree of the Monitor Browser and compose your own reports and charts.
More information: Java System Reports.
Central Monitoring
If you want to monitor SAP NetWeaver Process Integration 7.1 (PI) centrally, you must use the central SAP NetWeaver Administrator for PI.
More information about the configuration and use of the SAP NetWeaver Administrator for PI, see
Central Monitoring
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 4 of 59
To monitor AS Java you use the Monitor Browser, charts, and reports. The Monitor Browser comprises a tree of single monitors, where you can view current
data reported by each activated monitor, either in a table or in a chart. You can view the traffic light of each monitor, which changes in case the values
reported by the monitor exceed the predefined limits. From the Monitor Browser, you can choose the monitors of your interest and combine them into one
chart. The chart of one or more monitors gives you both an overview of a monitors data and a comparison between several monitors. If you want an even
broader system overview, you combine several charts into one report.
Below are the most important actions you can perform with Java System Reports:
Use the set of predefined charts and reports to monitor certain aspects of the system performance, such as memory consumption, combined security
information, system health data, and so on.
More information: Using the Predefined Charts and Reports
Using the tree of monitors in the Monitor Browser, you can view detailed information about the system and applications performance and receive alerts in
case the reported data has unexpected values.
More information: Managing Monitors with the Monitor Browser
You can pick one or more monitors from the Monitor Browser tree to create your own charts.
You can also combine several charts into your own custom report.
More information: Monitoring Using Charts and Reports
If you experience problems using the Java System Reports (for example, problems displaying charts and reports, or lack of reported data), see
Troubleshooting.
Java
Procedure
Using Predefined Charts and Reports
In Java System Reports, there is a set of predefined charts. These charts contain the most useful information, such as memory consumption information or
data about the logged-in users.
There is also a set of predefined reports, such as Security or Error Statistics .
More information, see Using the Predefined Charts and Reports
Composing a Chart
To customize Java System Reports according to your monitoring needs, you can compose your own charts and save them. The charts can contain any
performance and JARM monitor from the monitoring tree.
You can also use the predefined chart as templates, edit them, and save them under another name.
You can than use those charts as part of your own reports.
More information: Composing Charts
Composing a Report
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 5 of 59
In the same way, you can compose your own reports. They can contain the predefined charts as well as charts that you have composed yourself.
When you compose a report, you can save it for subsequent use and make it appear as an entry report every time you start JSR.
More information: Composing a Report
The predefined reports also contain the traffic light and the description of important monitors. This way you see only the current state of a
monitor without its detailed history.
Prerequisites
You have started the Java System Reports.
Procedure
1. From the Instance dropdown box, choose an instance.
You can choose to monitor a particular instance or all instances in a system.
2. From the Cluster Node dropdown box, choose a node.
You can monitor a single server process or all server processes of the selected instance.
If you have chosen to monitor all instances, at this step, only the All option is available.
3. To set the period for which the performance data is generated, in the Time Period dropdown box, perform one of the following:
Choose a preset period of the last 1, 8, or 24 hours.
Choose Custom , specify time and date, and choose Apply to confirms your custom reporting period.
You can use the Set Current Date and Time option for setting the current time as the end of the reporting period. You must specify the beginning of
the reporting period.
4. If you want to configure the display of data, the saving of history, or the auto refresh function, you can change additional settings.
More information: Changing Settings and Exporting History.
5. To view a report, choose the Reports tab, and then from the Report dropdown box, choose a report.
When viewing reports, choose the heading of each chart or table, depending on the view, to open a large-size chart or a table in a new tab.
To go back to the report, choose the Reports tab.
6. To view a chart, choose the Charts tab, and then from the Chart dropdown box, choose a chart.
For hints on how to read charts, choose Hint on charts .
7. To toggle between the chart view or table view, in the right-hand side corner, select the following:
Chart View
Presents the monitored data in the form of a chart.
Table View .
Presents in tabular format the name of each monitor and its values for the specified period.
When the data from two or more monitors is in different ranges, for example, the data set of one monitor is in the range of 0 to 1, while the other is in
the range of 10 000 to 100 000, you can use the Scale Monitor Values checkbox.
This function scales the values to fall in the range of 1 to 100, when this is possible, and indicates the scaling factor in the legend below the chart or
table.
See also:
Composing Charts
Composing Reports
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 6 of 59
You cannot delete a predefined chart or edit a predefined chart and save it under its original name. To create a chart based on a predefined
one, you have to edit and save the modified preset chart under a new name.
When you create, edit or delete a chart, the changes you make become available:
Only for the currently selected system
For all users who work with Java System Reports
Prerequisites
You have started the Java System Reports.
Procedure
Creating and Editing Charts
1. In the Instance dropdown box, choose an instance.
2. In the Cluster Node dropdown box, choose the server process to which you want to add monitors or choose All .
If in the Instance dropdown box you have selected All , in the Cluster Node dropdown box only the All option is available.
3. If you want to configure the display of data, the saving of history, or the auto refresh function, you can change additional settings.
More information: Changing Settings and Exporting History.
4. Choose the Charts tab, and then from the toolbar, choose Open Customization .
Below the tabstrip, new buttons appear.
5. To create a chart from scratch, choose New .
To create a chart based on a preset or a custom one, in the Chart dropdown box, choose a preset or a custom chart, and then choose Edit Mode .
6. To edit a chart, in the Chart dropdown box, choose a custom chart, and then choose Edit Mode .
7. In the Name and Description fields, enter a name and short description for the chart.
8. In the Selected Nodes screen area, add therequired performance or JARM monitors to your chart:
Task
Adding Performance Monitors
Procedure
Enter Manually
4. Choose Add .
The Attributes screen area appears.
5. For every JARM monitor you add, you need to specify which of its
attributes you want to monitor. In the Attributes list, select one or more
attributes.
6. If you want to remove a monitor, in the Selected Nodes screen area, select the monitor and choose Remove . To remove all monitors, choose Remove
All .
7. Depending on the type of chart, choose between the following:
If you created a chart from scratch, or edited a custom chart, choose Save .
If you created a chart based on an existing predefined or custom one, choose Save with New Name .
Deleting Charts
1. Choose the Charts tab, and from the toolbar, choose Open Customization .
2. In the Chart dropdown box, choose a custom chart.
You cannot delete predefined charts.
3. Choose Delete .
See also:
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 7 of 59
Composing Reports
Managing Monitors with the Monitor Browser
You cannot delete a predefined report, or edit a predefined report and save it under its original name. To create a report based on a predefined
one, you have to edit and save the modified preset report under a new name.
When you create, edit or delete a report, the changes you make become available:
Only for the currently selected system
For all users who work with Java System Reports
Prerequisites
You have started the Java System Reports.
Procedure
1. In the Instance dropdown box, choose an instance.
2. In the Cluster Node dropdown box, choose the server process to which you want to add monitors or choose All .
If in the Instance dropdown box you have selected All , in the Cluster Node dropdown box only the All option is available.
3. If you want to configure the display of data, the saving of history, or the auto refresh function, you can change additional settings.
More information: Changing Settings and Exporting History.
4. Choose the Reports tab, and from the toolbar, choose Open Customization .
Below the tabstrip, new pushbuttons appear.
Task
Creating and Editing Reports
Procedure
2. In the Name and Description fields, enter a name and short description
for the report.
3. In the Charts pane, choose Add Charts . The list of available charts
appears.
4. From the list of charts, choose one or more charts, and then choose
Add .
To select multiple charts, on your keyboard, press and hold the CTRL key and
with the primary mouse button choose the charts you want to add.
5. If you want to remove a chart from the report, choose the chart, and then
Remove . To remove all charts, choose Remove All .
6. Perform one of the following:
If you created a report from scratch or edited a custom report, choose
Save .
If you created a report from an existing predefined or custom one, enter a
different name and choose Save with New Name .
Deleting Reports
1. Choose the Reports tab, and from the toolbar, choose Open
Customization .
Below the tabstrip, new pushbuttons appear.
2. From the Report dropdown box, choose the report you want to delete.
Predefined reports cannot be deleted.
3. Choose Delete .
Setting a Default Report
You can set a report to display each time you start Java System Reports.
The report you set becomes the default one only for the currently selected system,
as well as for all users who work with Java System Reports.
See also:
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 8 of 59
Composing Charts
Monitoring Tree
The monitoring tree comprises nodes and monitors. A node can be of two types: summary and object. Summary and object nodes do not provide information
but are used to group monitors. A monitor is a leaf in the monitoring tree.
The monitoring tree comprises the following summary nodes:
Applications
Reports information about the Java applications that are running on the selected system and that have implemented monitoring functionality.
Kernel
Reports information about the AS Java managers registered for monitoring.
Performance
Reports AS Java performance measurements.
Services
Reports information about the state of AS Java services registered for monitoring.
System
Displays general information about the system, such as hosts, ports, cluster element names, IP addresses, VM information, and so on.
Color Thresholds
The status of a monitor is graphically displayed as an icon. The list below outlines the color statuses and their meaning:
The system displays
with the quick info text OK if data is at the normal level and no attention is needed.
Prerequisites
You have started the Java System Reports.
Procedure
Starting the Monitor Browser
1. In the Instance dropdown box, choose an instance.
2. In the Cluster Node dropdown box, choose the server process to which you want to add monitors or choose All .
If in the Instance dropdown box you have selected All , in the Cluster Node dropdown box only the All option is available.
3. Choose the Reports tab.
4. In the Reports dropdown box, choose Monitor Browser .
5. To view the monitoring tree, choose the type of view in the Show dropdown boxes.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 9 of 59
Configuring a Monitor
You can also fine tune additional monitor settings, such as the monitors description, data collection period and so on.
More information: Configuring a Monitor
Prerequisites
You have opened the Monitor Browser.
More information: Managing Monitors with the Monitor Browser
Procedure
Activating and Deactivating a Single Monitor
1.
2.
3.
4.
5.
From the monitoring tree, select the monitor which you want to activate or deactivate.
In the Details screen area, choose the Configuration tab.
Choose Edit Configuration Group .
To activate or deactivate a monitor, select or deselect the Enabled checkbox.
Choose Save.
Yes
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 10 of 59
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Services/JMX Adapter/NotificationQueue/Size
Services/JMX Adapter/NotificationQueue/ThreadUsage
Services/JMX Adapter/ObjectNameCash/CashFillRate
Services/Keystroke/System Entries
Yes
Services/Keystroke/User Entries
Yes
Services/Log Configurator/General/TotalLogFileSize
Yes
Yes
Yes
Yes
Yes
Yes
Services/Web Container/AverageProcessingTime
Yes
For more information about the types of monitored data, see Monitored Data.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 11 of 59
Prerequisites
You have opened the Monitor Browser.
More information: Managing Monitors with the Monitor Browser
Procedure
1.
2.
3.
4.
5.
From the monitoring tree, select the monitor whose color changing thresholds you want to change.
In the Details screen area, choose the Configuration tab.
Choose Edit Configuration Group .
In the respective fields, enter the values for which you want the color of the icon to change.
Choose Save.
Prerequisites
You have opened the Monitor Browser.
More information: Managing Monitors with the Monitor Browser
Procedure
1. Select a monitor from the Monitor Tree .
The monitors details appear in the Details screen area.
2. In the Details screen area, choose Configuration tab
3. Choose Edit Configuration Group .
In the Description input field, you can edit the description of a monitor.
In the Data Collection group of input fields fields, you can edit the following fields:
Field
Data Collection Reaction to Resource Failure
Meaning
In case of resource failure, you can configure the monitor to react in the following
ways:
Unregister
The monitor is not visible in the monitoring tree.
Ignore
The monitor is visible in the tree but is not working.
The field is not editable and is used for information purposes only.
Period
Unit
Enable
4. Choose Save .
5. To restore the monitors settings to default, choose Restore Group to Default .
Prerequisites
You have opened the Monitor Browser.
More information: Managing Monitors with the Monitor Browser
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 12 of 59
Procedure
1. To view the history of an active monitor, choose History Comparison Mode .
The column Selected appears in the Monitor Tree screen area. The column displays checkboxes for each active monitor.
2. Select the checkbox of one or more monitors.
A chart displaying the values of the monitor appears in Details screen area.
If you have selected more than one monitor, the system plots the values of all monitors on the chart.
3. To view the values in a table, in the Details screen area, choose Show Table .
Prerequisites
You have started the Java System Reports.
Procedure
Saving History
1. Choose Settings .
2. From the History Properties list, specify a mode for storing history data.
Choose between the following:
Memory
History data is stored in the memory for 24 hours.
In this mode, JARM history is not stored. You can still add performance and JARM monitors to charts, but history for JARM data is not available.
No History
In this mode, charts and reports display only the current values of monitors.
Persistent
Data for both performance and JARM monitors is stored in the database. You can specify how long the data is to be stored.
Exporting History
1. Choose Export History .
2. From the screen that opens, choose Download History Data .
A download dialog box opens.
3. Specify the destination for the archive file.
4. When the download is complete, choose Close .
1.1.4 Troubleshooting
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 13 of 59
In this case, the chart displays only the current values of the monitors it comprises. For more information about monitor history settings, see Changing
Settings and Exporting History .
You have only recently chosen to keep a history of monitor values.
The monitor is deactivated. To activate it, see Activating and Deactivating Monitors.
1.1.5.1 Applications
The Applications node of the monitoring tree displays monitor data for the Java Enterprise Edition 5 applications that have implemented the monitoring
functionality. By default, you can see here the Table Buffers monitor.
This component shows the monitored data for Open SQL table buffers.
Monitored Unit
Description
BufferSize
FreeSize
HitRate
Number of displacements
The total number of displacements in the buffer since buffer instance startup.
Description
Indicates whether the caf.core application is started or stopped. It contains
predefined, commonly-used services and data types for your composite
application.
Runtime Application
Indicates whether the runtime application is started or stopped. You need to start
this application to be able to run all other CAF applications.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 14 of 59
1.1.5.2 Kernel
This section provides detailed information about the AS Java managers that are registered for monitoring. Currently, the following managers are registered:
Monitored Unit
Description
The number of threads from the thread pool which are executing a Runnable task
pool
Capacity of the waiting tasks queue, where tasks waiting for execution are stored.
The ratio of current thread pool size to maximum pool size. The outcome is
presented as a percentage.
The ratio of active threads count to maximum pool size. The outcome is presented
as a percentage.
Usage Rate
The ratio between the allocated task slots and total number of task slots. When a
task has to be executed in a separate thread, the caller thread allocates a free task
slot in the thread manager. If there is no free task slot then the caller thread blocks
until one is free.
The number of Runnable tasks waiting for available thread from the thread pool to
be executed
The number of threads waiting to deposit a Runnable task in the request queue if it
is full
The ratio of the current size of the waiting tasks queue to the maximum configured
size.
Monitored Unit
Description
ClassLoaders Count
Monitored Unit
Description
The total number of bytes received from the specified service through the message
server communication layer.
The total number of bytes sent from the specified service through the message
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 15 of 59
the message server communication layer. This is the time between the call of the
send method and the actual writing of the message in the socket.
The current size of the message object pool in the lazy communication layer.
MessageContext Communication/General (MessageContext)/Current MS Pool Size The current size of the message object pool in the message server communication
layer.
MessageContext Communication/General (MessageContext)/Lazy Pool Size Rate
Ratio of the current size to the maximum size of the message object pool in the lazy
communication layer.
Maximum size of the message object pool in the message server communication
layer.
The maximum size of the message object pool in the lazy communication layer.
The maximum size of the message object pool in the message server
communication layer.
SessionContext Communication/Data Per Processors/Current Session Queue Size The current size of the message queue in the session communication layer.
SessionContext Communication/Data Per Processors/Session Queue Size Rate
The ratio of the current size to the maximum size of the message queue in the
session communication layer.
The total number of bytes received from the specified service through the session
Received
communication layer.
The total number of bytes sent from the specified service to the cluster through the
session communication layer.
Average time in microseconds (us) that a message spends in the message queue
Process Time
of the session communication layer. This is the time between the call of the send
method and the actual writing of the message in the socket.
The maximum size of the message queue in the session communication layer.
Monitored Unit
Description
Commit Duration
Description
Description
LockingTable
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 16 of 59
description
Describes the operation for which the time measurements are effective. For
example, create unique owner (total), create single lock (total).
average (us)
Average time for the execution of operation for description x.
min (us)
Minimal time for the execution of operation for description x.
max (us)
Maximal time for the execution of operation for description x.
count
Number of operations executed for description x.
Description
LoggedInUsersTable
Provides general information about the users and sessions. The information
includes:
User ID
Security Sessions
Web Sessions
Opened EJB Sessions Count
Monitored Unit
Description
The number of threads from the thread pool which are executing a Runnable task
Capacity of the waiting tasks queue, where tasks waiting for execution are stored.
The ratio of current thread pool size to maximum pool size. The outcome is
presented in percentage.
The ratio of active threads count to maximum pool size. The outcome is presented
in percentage.
Usage Rate
The ratio between active threads count to maximum pool size in percents.
The number of Runnable tasks waiting for available threads from the thread pool to
be executed.
The number of threads waiting to deposit a Runnable task in the request if it is full.
The ratio of the current size of the waiting tasks queue to the maximum configured
size.
1.1.5.3 Performance
The Performance node of the monitoring tree displays performance monitor data for applications and services in accordance with the developers needs. By
default, you can see here the following groups of monitors:
Activity Snapshot
Monitored Unit
Description
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 17 of 59
Active Applications
Active Sessions
Active Threads
Shows active threads from the thread pool, which are used at the moment.
Active Users
Shows the active users: users that are currently requesting resources from the AS
Java.
Requests performance
Monitored Unit
Description
Component calls
Number of requests
1.1.5.4 Services
This section provides detailed information about the AS Java services that are registered for monitoring. Currently, the following services are registered:
ConnectorService
Deploy
HTTP Provider
IIOP Provider
JMS
JMX Adapter
JNDI Registry
Keystore
Log Configurator
Memory Info
P4 Provider
Security
Security UME
TREX
Timeout
Transaction
Web Container
Web Services
WebDynpro
XI Security
XML Form Module
1.1.5.4.1 ConnectorService
The Connector Container Service manages the overall connectivity to back-end resource systems.
Monitored Unit
Description
FreeManagedConnectionCount
ManagedConnectionUsageRate
The ratio between the used connections and connection pool maximum size for a
specific connector.
MaxConnectionNumber
OpenedConnectionCount
TimeoutedConnectionCount
UsedManagedConnectionCount
WaitingConnectionCount
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 18 of 59
1.1.5.4.2 Deploy
This service manages the deployment of applications and the distribution of their modules to the corresponding containers across the cluster. For more
information, see Deploy Service in the Administration Manual.
Monitored Unit
Description
Application name
Archive Size the application archive size
Deployment Duration the deployment duration time for the application
Number of redeploys the number of redeploys for the application
Time of last redeployment
Status applications current status: STARTED, STOPPED, etc.
Startup mode of the application.
Description
General/AllRequestsCount
General/ResponsesFromCacheCount
The number of all responses which have coma from the cache
The number of all responses that have returned this response code
The number of all requests using this method since the startup
Description
ExportedRemoteObjectsCount
IIOPThreadUsageRate
1.1.5.4.5 JMS
Monitored Unit
Description
Checks if the jms_provider service is available. Sends and receives one message.
Shows the time to send and consume a single message through the JMS Provider
message
(message latency).
Number of Virtual Providers that are not started currently in the cluster.
Shows the messages per queue. Only the first 50 messages are displayed.
Number of connections.
Number of consumers.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 19 of 59
Number of producers.
Virtual_Provider_Name /TopicMessages/Topics
Shows the messages per topic. Only the first 50 messages are displayed.
In place of Virtual_Provider_Name you have the name of the Virtual Provider you have created or the default one. For each Virtual Provider you have the
same set of monitors.
Description
MbeanServer/ClusterWideNotificationListeners
The number of JMX notification listeners registered with the MBean server delegate
to receive MBean server notifications from cluster nodes.
MbeanServer/LocalMBeanRepositorySize
The number of MBeans registered with the MBean server in the local cluster node.
NotificationQueue/Size
NotificationQueue/ThreadUsage
ObjectNameCache/CacheFillRate
The number of currently cached object names to the maximum size of the cache.
ObjectNameCache/HitRate
Monitored Unit
Description
The total number of objects that are bound in the naming tree, including the
serializable and non-serializable objects. Gives an idea about the application
runtime.
1.1.5.4.8 Keystore
Certificate and key pair entries expiration tracker.
Monitored Unit
Description
System Entries
Monitors the entries from the system created and maintained views.
To find the exact entries navigate to 'ITSAM / Configuration Management / Security
Management / Key Storage' and apply filter for 'System Views' with the appropriate
status.
User Entries
Monitors the entries from the user created and maintained views.
To find the exact entries navigate to 'ITSAM / Configuration Management / Security
Management / Key Storage' and apply filter for 'System Views' with the appropriate
status.
Description
General/TotalLogArchivesSize
General/TotalLogFilesSize
The total size of all log and trace files excluding archives.
Page 20 of 59
This service is responsible for keeping track of the memory that is used internally by the JVM of the owner cluster element.
Monitored Unit
Description
Allocated Memory
Provides the current, maximum, and minimum values of the allocated memory.
Available Memory
Provides the current, maximum, and minimum values of the available memory.
Usage Rate
The ratio between the used memory and the total memory of the process.
Used Memory
Provides the current, maximum, and minimum values of the memory used.
1.1.5.4.11 P4 Provider
The P4 is the implementation of the RMI communication protocol used on the AS Java. For more information, see P4 Provider Service in the Administration
Manual.
Monitored Unit
Description
ExportedRemoteObjectsCount
FailedRequestsCount
P4ThreadUsageRate
RequestsCount
1.1.5.4.12 Security
The Security Provider Service enables you to manage the security policy, the users, the authentication and authorization mechanisms on the system, and to
restrict access to the resources or the applications deployed on the AS Java. For more information, see Security Provider Service in the Administration
Manual.
Monitored Unit
Description
AggregatedData/ActiveSessionsCount
The number of all active security sessions. Such sessions can be created for every
protocol, which has access to the server http, p4, iiop, telnet, rfc.
AggregatedData/InvalidSessionsCount
AggregatedData/LoggedOffSessionsCount
The number of all security sessions since server startup for witch the user has
successfully logged off
AggregatedData/TimedOutSessionsCount
The number of all security sessions that have timed out since the server startup
AggregatedData/TotalSessionsCount
AggregatedData/UnsuccessfullLogonAttemptsCount
The number of all unsuccessful logon attempts since the server startup
The number of all sessions since the server startup for which the user has
successfully logged off
Number of all sessions that have timed out since the server startup
The number of all unsuccessful logon attempts since the server startup
Description
The number of communication errors occurred since last start-up in relation to ldap
requests.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 21 of 59
Persistence/LDAPMainRequestCount
Security UME Persistence/Security UME LDAP
The percentage of ldap request served by the main server in case of a UME High
Persistence/LDAPMainServerUsage
Availability configuration.
The number how often the defined limits of the LDAP pool are reached.
Persistence/LDAPPoolExhaustionCount
Security UME Persistence/Security UME LDAP Persistence/LDAPRequestCount
1.1.5.4.14 TREX
Monitored Unit
Description
TREXConfiguration Monitor
1.1.5.4.15 Timeout
This service is only used internally by the AS Java.
Monitored Unit
Description
EstimatedFrequencyPerMinute
1.1.5.4.16 Transaction
The SAP AS Java enables distributed transactions, which can spread over many different resources and even pass the boundaries of an application. For more
information, see Transaction Service in the Administration Manual.
Monitored Unit
Description
CommittedTransactionsCount
OpenTransactionsCount
RolledBackTransactionsCount
SuspendedTransactionsCount
TimedOutTransactionsCount
TransactionsSuccessRate
Description
AllRequestsCount
AverageProcessingTime
Average value of the request processing time for given time interval.
CurrentHttpSessions
CurrentSecuritySessions
The number of currently valid security sessions created for http clients.
HttpSessionsInvalidatedApplication
SecuritySessionsInvalidatedByApplication
TimedOutHttpSessions
TimedOutSecuritySessions
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 22 of 59
1.1.5.4.19 WebDynpro
Monitored Unit
Description
General Information/Configuration
1.1.5.4.20 XI Security
Monitored Unit
Description
Archiving/Archiving state
Archiving sessions.
Archiving/Configuration
Permission/Permission processing
Permission overview.
Description
Properties
1.1.5.5 System
This section contains a group of monitors that are responsible for observing the system parameters:
Monitored Unit
Description
Provides information about the basic settings of the current cluster node.
Instance Info
Provides information about the SAP Central Services (SCS), that is, about the
Enqueue and Message Servers.
System Properties
The system properties monitored by the Monitoring Service are the properties
provided by System.getProperties(). For more information, see
java.lang.System in the JDK API documentation.
VM Info
Provides information about the basic Java Virtual Machine (JVM) parameters.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 23 of 59
Concepts
Log and trace files contain information about the system execution.
Log records are mainly used by administrators to monitor the system operation and to perform error analysis. Logs are typically written to categories.
Trace records are usually used by developers or support (engineers) to record and analyze the occurrence of certain events in programs during runtime.
Traces are typically written to locations.
More information: Logging Features.
Configuration
The table below contains configuration settings you can perform if the default setting are not suitable:
Configuration Task
Description
You use the Log Configuration tool in the SAP NetWeaver Administrator.
The default severity values are:
You can configure the storage location for trace files, using the Log Manager .
More information: Log Manager.
Log and trace archiving is switched off by default. You can switch it on and
configure the archive storage location and specify which files to be archived.
More information: Configuring Log Files Archiving.
Tasks
The table below contains tasks you can perform, when required:
Task
Description
In any predefined or custom view, you can filter and display log and trace records
on the AS Java that meet a specified filter criterion.
More information: Filtering Logs and Traces.
If an AS Java is not running on the system to be monitored, you can filter and
display log and trace records, using the predefined Standalone Log Viewer view.
More information: Viewing Standalone Log Viewer.
Search logs
To monitor the SAP NetWeaver system landscape for critical issues, in any
predefined view or custom view, you can filter and display only log and trace
records with severity ERROR or FATAL.
Automatic when the logs reach the size of five files at 10 MB each, the
new logs start overwriting the old ones, that is, the old logs are deleted
automatically.
If you activate archiving, the system backs up the set of five files into a ZIP file
and then starts overwriting the first log file.
You can manually delete part of the log or trace files that you do not
need, for example, you may not need the default traces.
In several countries, the backup of security logs is enforced by law. Therefore,
you must perform regular backups and keep all of your security log files.
You can delete the temporary log and trace files that are generated by the
system when you view the archives using the Log Viewer. When you
open archives of logs and traces, the log and trace files of each archive
are extracted to the temporary directory ./log/archive/temp.
Afterwards, the log and trace files are not deleted from the temporary directory.
The next time you want to view the same archives, they will be displayed faster.
We recommend that you delete these log and trace files periodically to save disk
space.
Monitor log and trace file size
There are two types of monitors for logs and traces for files size and for achieve
size.
More information: Log Configurator.
You can also change the settings of the monitors traffic light, for example, the value
when the monitors traffic light changes from yellow to green. To perform this, use
the Monitor Browser in the SAP NetWeaver Administrator.
More information: Monitor Browser .
Tools
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 24 of 59
The Log Viewer tool in the SAP NetWeaver Administrator allows you to view all list and text formatted logs and traces that are generated from the whole SAP
NetWeaver system landscape.
You can also use the following tools to monitor and display logs:
SAP Management Console
Command Line Log Viewer
Additional Information
From <Drive>:\usr\sap\<SID>\<Instance name>\j2ee\cluster\<Server name>\log, display the following files:
\system\database.log
\system\security.log
\system\server.log
\system\logging.log
\system\userinterface.log
\system\configchanges.log
\application.log
For more information about the logging categories and tracing locations of the CE components, see SAP Note 1048624.
Tracing
Tracing is a process of writing detailed information about an operation to an output file. The trace facility provides:
a detailed sequence of statements that describe the events of an operation as they are executed.
diagnosing of an abnormal condition.
Traces are used by support engineers and developers. Therefore tracing is not normally turned on. Traces can be switched on if a problem has occurred and a
detailed analysis of a distinct part of a program is necessary.
Log Manager
Log Manager is a module that manages the process of logging system events. The Log Manager is part of the Java Enterprise Runtime and is the first
manager to be started at system startup.
By using the Log Manager properties, you can reconfigure the default system log archiving and tracing behaviour.
Formatter.
Levels of Severity
An important part of any log and trace message is its severity. This denotes the level of importance or relevance of a certain message. Logs and traces can
be limited to certain severity levels, that is, only data of a defined severity is collected. The increasing order of the severity levels is:
DEBUG For debugging purpose, with extensive and low level information
PATH For tracing the execution flow
INFO Informational text, mostly for echoing what has already been performed
WARNING The application can recover from an anomaly and fulfill the required task, but needs attention from a developer/operator.
ERROR The application can recover from an error, but it cannot fulfill the required task due to the error
FATAL The application cannot recover from an error, and the severe situation causes fatal termination.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 25 of 59
Features
Log Controllers
Log controllers are objects that manage the writing of log and trace messages. Two types of log controllers are available:
Location describes messages that originate from delimited source code areas. It is used to store and emit trace messages. Since trace messages are
meant for developers and support engineers, they are organized along code packages. In the SAP NetWeaver Administrator, locations are named as
tracing locations.
Category describes messages specific to distinguished problem areas. It is used to store and emit log messages. Typical problem areas are:
databases, networking, security auditing, and others. In the SAP NetWeaver Administrator, categories are named as logging categories.
The configuration steps for both logging categories and tracing locations are the same. Therefore, the steps in the configuration procedures
treat them as a whole.
Severity levels
The severity denotes the level of importance or relevance of a certain message.
The increasing order of the severity levels is:
ALL The lowest severity. Controller with such a severity logs all the messages regardless of their severity.
DEBUG For debugging purpose, with extensive and low level information.
PATH For tracing the execution flow, for example, used in the context of entering and leaving a method, looping and branching operations.
INFO Informational text, mostly for echoing what has already been performed.
WARNING Announces that the application can recover from an anomaly and fulfill the required task, but needs attention from a developer/operator.
ERROR Announces that the application can recover from an error, but it cannot fulfill the required task due to the error.
FATAL Announces that the application cannot recover from an error, and the severe situation causes fatal termination.
NONE The highest severity. Log controllers with such a severity suppress all the messages logged into them, except for the messages with the same
severity.
Activities
Configuring Log Controllers
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 26 of 59
Prerequisites
Before changing the severity of a log controller or instance in a system, bare in mind that:
If you change the severity of a log controller, the severity of all instances in the system will be changed for this controller. That is, the severity change will
be at system level.
If you change the severity of the selected log controller for only one instance, and this new severity is different on the various instances in the cluster,
there will be no system level severity anymore. There will be only specific instance severities.
Procedure
1. Find the Log Controller for Configuring
1.
2.
3.
4.
If you want this changed reference for the children to be valid only for the current filter, choose Copy to Filtered Sub-Tree .
3. Choose Save Configuration .
4. In the Destinations pane on the System Configuration tab, you can find all the destinations that are assigned to the selected log controller at system
level, that is, for the whole cluster.
5. If you want to reset the severity of the selected log controller to its default value, choose Reset Category or Reset Location .
Configuring Log Controllers per Instance
1.
2.
3.
4.
The default severity for categories is INFO, and for locations- ERROR.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 27 of 59
These activities have to be done with extreme care and only by users who are familiar with the SAP Logging API in detail. More information:
SAP Logging API.
You can switch on/off writing traces to one file, as well as exclude certain locations from being written to one trace file. This is done using the Log
Manager s properties ForceSingleTraceFile and SingleTraceFile_UnrestrictedLocations correspondingly.
More information: Log Manager.
Formatter.
You can configure and manage formatters for existing destinations only.
Prerequisites
Start the Config Tool by double clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory.
Procedure
Adding a New Formatter
1. Choose cluster template Log Configuration Formatters. .
2. Select any formatter name from the list and then choose New .
A dialog box appears.
a. In the Enter name field, specify the name of the new formatter.
b. Choose OK .
The new formatter appears in the Formatters pane.
Editing a Formatter
1. From the Formatters pane, select the formatter you want to edit.
2. From the Type dropdown box, specify the formatter type.
You can choose from the default ones:
a. ListFormatter formats a log record, which is then ready to be transferred to and processed further by another application, for example, Log
Viewer.
b. TraceFormatter a format that is readily understood by users. Only to this format you can specify a pattern. If you do not specify such, a default
one is created.
c. XMLFormatter formats log records as XML elements.
3. Choose the Pattern field to configure this formatter with a custom formatting pattern.
For the TraceFormatter you can configure the formatter using a custom formatting pattern. The pattern enables you to specify the message
data fields, with place holders of the form %[[-]<width>[-]]<type>, interspersed with arbitrary text that you want to include in the
formatted messages.
4. Choose
Apply .
Removing a Formatter
1. From the Formatters pane, select the formatter you want to remove.
2. Choose Remove .
3. Choose
Apply .
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 28 of 59
Log (Destination) .
Prerequisites
Start the Config Tool by double clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory.
Procedure
Adding a New Destination
1. Choose cluster template Log Configuration Destinations .
2. Choose any destination name in the list and then choose New .
A dialog box appears.
Editing a Destination
1. From the Destinations pane, select the destination you want to edit.
2. In the Enter Name field specify the name of the new destination.
The new destination appears in the Destinations pane.
3. Choose the Type dropdown list and specify the desired destination type.
You can select a default one: FileLog or ConsoleLog.
More information:
Log (Destination)
4. In the Pattern field, specify the path to the file where messages will be written.
The default path containing the destination's name is specified.
5. In the Limit field, specify the maximum number of bytes each file piece of the rotating file-set can contain.
6. Choose the Severity dropdown box to specify a severity level.
More information:
Appendix A: Severity Levels.
7. In case your destination is of type File (FileLog), you can decide to specify whether there will only be one file, or a rotating number of files. In the last
case, use Count field to specify the number of files in a rotation stack, and the Limit field, to define in bytes the size of one file from the rotation stack.
8. In the Formatter pane, select a new formatter. That is the format in which the log destination will print the messages.
More information:
9. Choose
Formatter .
Apply .
Removing a Destination
1. From the Destinations pane, select the destination you want to remove.
2. Choose Remove .
3. Choose
Apply .
The configuration steps for both categories and locations are the same. Therefore the steps below are described for log controllers as a whole.
Adding, editing, and removing log controllers has to be done with extreme caution and only by users experienced in the SAP Logging API.
More information:
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 29 of 59
Prerequisites
Start the Config Tool by double clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory.
Procedure
Adding a New Controller
1. Choose cluster template Log Configuration
2. Select the Categories tab if you want to create a new category, or the Locations tab if you want a new location. The new element is added as a new
sub-node of the ROOT CATEGORY / ROOT LOCATION tree structure. If you want to add a new category / location in a particular position inside an
already available tree structure, browse to that position, select the node under which the new category/location will be added, and then continue with the
next step.
3. Choose New .
A dialog box appears.
a. In the Enter name field, enter the name of the new controller.
Categories are named according to the hierarchical structure known from file systems. The different hierarchical levels in a category name must be
separated by /, for example /System/Database (always starts with /).
Locations are labeled according to the hierarchical structure known from Java packages. The . character is used to demarcate the different layers
in locations names. For example com.sap.yourPackage.Class.
If you have selected a particular node, the Name field will display the path to the selected node. Therefore, you only have to define the subname of your category/location at the end.
b. Choose OK .
The new controller is added to the tree.
Editing a Controller
1. Select the controller you want to edit.
2. In the Severity dropdown box, specify the level of severity.
More information:
Appendix A: Severity Levels.
3. If you are changing the severity of the root node of the whole tree or of a particular sub-tree, the change will take effect to all nodes below this root node.
4. You can specify a destination where the log/trace messages to be written. To add one or more destinations, choose Add and then OK .
5. If you want to remove a destination, choose Remove (on the right-hand side).
6. Choose
Apply.
Choose the Reset to template option if you want to return to the configuration available at the time of the AS Java installation. This is valid for
the current controller only and has some restrictions, that is, sometimes not all the configuration will be restored. Generally, only the severity
levels are reset.
Trace messages for standard output for STDOUT and STDERR are written in the defaultTrace.trc file to the locations System.out and System.err ,
respectively. To be able to see these trace messages, you have to set the severity level of System.out to INFO , and the severity level of System.err to
ERROR.
Removing a Controller
1. Select the controller you want to remove.
2. Choose Remove (at the bottom of the configuration window).
3. Choose
Apply .
Activities
1. Start the Config Tool by double clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory.
2. Choose template Managers LogManager.
Property
Description
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Default Value
Page 30 of 59
ArchiveOldLogFiles
ArchivesDirectory
./log/archive
/usr/sap/<SID>/<instance name>/j2ee/cluster/server
directory.
ArchivedFileNames
ConsoleLogs_UseSapAPI
YES
SQLTraceInitiallyEnabled
SingleTraceFile_UnrestrictedLocations
YES
com.sap.engine.services.httpserver.server.
Smd
Defines log controllers, that write only in their own log ShortDumpHeader;ShortDumpBody;SQLTraceLogg
locations, not in the defaultTrace.trc due to security or er
other reasons. The property value consists of the log
controllers full names, separated by semicolon(;)
In several countries, the backup of security logs is enforced by law. Therefore, you must perform regular backups and keep all of your security
log files.
Prerequisites
Start the Config Tool by double clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory.
Procedure
1. Choose cluster-data template managers LogManager.
2. From the list of properties, select ArchiveOldLogFiles.
By default, log archiving is disabled and the value is set to OFF.
3. To activate the log files archiving, in the Custom value field, set the value as ON.
4. Choose Set to apply the new value.
5. To change the current log archive directory, choose the ArchivesDirectory property.
The default directory where archives of logs are stored is: <Drive>:\usr\sap\<SID>\JC<Instance number>\j2ee\cluster\<Dispatcher
or server>\log\archive.
6. In the Custom value field, enter the name of the new directory.
7. Choose Set to apply the new directory.
8. If you want only certain log files to be archived, choose the ArchivedFileNamesproperty.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 31 of 59
The default value for this property is empty. This means that all log files will be archived.
9. In the Custom value field, enter the names of the files to be archived. The log file names have to be separated by semicolon(;).
10. Choose Set to apply the log file names.
11. Choose
Apply changes to save the changes.
12. For the changes to take effect, restart the cluster.
Result
Log archiving is activated. After the ZIP file is done, the new logs keep on overwriting the old log files.
More information about viewing log archive records: Predefined General Views.
1.2.2.4 LOG
Use
This section contains the log commands used for AS Java log system administration. They are added to the Shell environment by executing ADD LOG on
the command line.
LOG_ARCHIVE
Syntax
LOG_ARCHIVE
Description
LOG_CREATE
Syntax
Arguments
-? | -H Displays the help message.
-C | -D | -F Specifies the type of the object to be created: log controller (C), log destination (D),
or log formatter (F).
OID The ID of the object to be created. The OID identifier must represent a unique name
for the Log Configurator Service.
Description
Use the LOG_LIST command to obtain information about the existing objects. To
change the settings of a newly created object you can use the LOG_EDIT
command.
LOG_DUMPS
Syntax
Arguments
-? | -H Displays the help message.
OID The ID of the log controller to be debugged. The OID identifier must represent a
valid name for the Log Configurator Service.
ON | OFF Turns the additional console output ON or OFF.
Description
You can use the LOG_LIST command to obtain information about the existing
controllers.
Note that if this log controller already has an associated log destination of type
ConsoleLog some messages may be displayed twice.
Keep in mind the hierarchy of the log controllers. If neither ON nor OFF is
specified, then the current status is shown. If no OID is given a "global"
configuration is assumed.
LOG_EDIT
Syntax
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 32 of 59
Arguments
-? | -H Displays the help message.
-C | -D | -F Specifies the type of the object to be edited: log controller (C), log destination (D), or
log formatter (F).
OID The ID of the object to be edited. The OID identifier must represent a valid name for
the Log Configurator Service.
Description
You can use the LOG_LIST command to retrieve the current logging settings or
the LOG_CREATE command to add a new object to the existing configuration.
Note that only "named" objects can be edited (name is case sensitive), and that
this operation will affect all the users of the corresponding object.
LOG_LIST
Syntax
Arguments
-? | -H Displays the help message.
-C | -D | -F Specifies the type of the object to be listed: log controller (C), log destination (D), or
log formatter (F).
-T Specifies that a thorough info should be provided.
The -T switch can be used as a single argument or after a type specifier (that is: C, -D, or -F). In this case the command behaves as if there is no -T (the only
difference is that a detailed information will be provided for the appropriate
objects, instead of simple listing of their names).
The object identifier, that is, the name of an object as printed by this command,
displays a thorough information about the settings of a particular object. It must
be used with a preceding type specifier but without the -T switch. The -T switch
can be used only when no object ID is given.
OID The ID of the object to be inspected. The OID identifier must represent a valid name
for the Log Configurator Service.
Description
Shows information about the currently configured objects in the Log Configurator
Service.
Only "named" objects can be displayed (name is case sensitive). If the command
is used without arguments, it provides a complete listing of all registered object
names sorted by their corresponding types. If it is executed with a type specifier
but with no object identifier, then this command lists the name of every object of
the respective type that is configured with the Log Configurator Service
LOG_REMOVE
Syntax
Arguments
-? | -H Displays the help message.
-C | -D | -F Specifies the type of the object to be removed: log controller (C), log destination (D),
or log formatter (F).
OID The ID of the object to be removed. The OID identifier must represent a valid name
for the Log Configurator Service.
Description
You can use the LOG_LIST command to retrieve the necessary information.
Note that only "named" objects can be removed (name is case sensitive), and
that this operation will affect all the users of the corresponding object.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 33 of 59
More Information
More information about how to use the shell commands: Administration Using Telnet.
Log Viewer.
Integration
In the SAP NetWeaver Administrator you can configure the Log Viewer from the Log Configuration tool.
More information: Log Configuration with the SAP NetWeaver Administrator.
Features
The Log Viewer tool allows you to:
View list and text formatted logs and traces on selected systems in a set of predefined views.
More information: Predefined Views.
View application and system logs. The messages in log files provide hints to the cause of problematic application behavior.
Know the certain system problem via the trace messages.
View logs and traces from an AS Java that is not running, by connecting to a Standalone Log Viewer server
The Standalone Log Viewer Server is relevant only for viewing log records from the older systems 7.0.
For systems 7.1, you can use the newly created offline connecting tool: the SAP Host Control Agent.
More Information
How to Work with the Log Viewer
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 34 of 59
To see all the predefined views, choose Show Perspective and then, from the Log Perspectives dialog box, select the relevant view type.
After choosing a view, either a table or a list of the relevant logs and traces appears.
To see general information about the usage of each predefined view choose
The maximum number of list-formatted log records you can enter is 50.
The maximum number of text-formatted log records you can enter is 500 .
To navigate the table pages, use the right-hand radio buttons.
Go to Newest records .
Collapse tray .
Log Formats
ListLog
ASCIILog
SysLog
List
ASCII; Trace
ABAP Sys Log
ASCII Format
A log file in ASCII format is any text file with no particular format.
Trace Format
This format is the same as the ASCII format. However, a log file in trace format is a text file with a particular format. The format is defined by a pattern. The
pattern for a trace formatted message is the following:
%24d %-40l [%t] %s: %m
where:
%d is a timestamp in a readable format
%l is the location on behalf of which the message has been created
%t is the thread that has emitted the message
%s is the severity of the message
%m is the message text.
The numbers in the pattern denote the number of characters for an item. The corresponding output is the following:
Dec 01, 2007 10:10:00 PM com.sap.FooClass.fooMethod [main]
Fatal: A sample fatal message
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 35 of 59
Features
A predefined view is defined by a combination of the following:
Example of Filters
The priority for applying filters is the following: when you apply a filter, all filters that are set below it are also applied, and the filters that are set above it, if
any, are not applied.
If you set all filters in a view and apply the filter by data source, it will be applied and all other filters below it will be applied.
If you set all filters in a view and apply only the filter by content, then only the filter by content will be applied.
The conditions for applying the filter criteria are the following: when you set two or more filter criteria of the same type, the condition is logical OR. When you
set filter criteria of a different type, the condition is logical AND.
Activities
To access the predefined views, from the Show dropdown list box select the relevant typical or specific predefined view type.
You can use the predefined views as a template for creating custom views.
More information: Creating, Exporting and Importing Custom Views
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 36 of 59
Prerequisites
Open the Log Viewer tool by choosing SAP NetWeaver Administrator Problem management Logs and Traces Log Viewer .
Procedure
Predefined General Views
Predefined View
Description
Shows a table of merged log records from all list formatted log files, except for
defaultTrace.trc , on all selected systems.
No filters by data source and content are set.
Shows a table of merged log records from all list formatted log files, written in the
last 24 hours on all selected systems.
No filter by data source is set. The following filter by content is set: Date & TimeRelative equals last 24 hours.
Alert (Java)
Shows a table of merged log records from all list formatted log files, except for
defaultTrace.trc with severity ERROR and FATAL, on all selected systems.
No filter by data source is set. The following filter by content is set: Severity is
greater than or equal to error.
Shows a list of log records written on all selected systems. Text formatted log
records are not merged in a table.
No filters by data source and content are set.
Expert
Allows you to view the user defined set of log records, on all selected systems.
These logs correspond to traces of the Startup Framework. They give information
about behaving of the AS Java at startup.
No filters are set.
More information: Viewing Predefined Development Views.
Shows a table of log records written in the ABAP Sys Log set of files.
No filters are set.
Allows you to view archives of log records, both list and text formatted on all
selected systems.
The default directory where archives of logs are stored is:
usr\sap\<SID>\JC<Instance number>\j2ee\cluster\
<server>\log\archive .
In the archive folder there is a sub-folder temp where the log and trace files of
each archive are extracted. After you leave the Log Archives (Java) view, the log
and trace files are not deleted from the temp directory.
More information: Configuring Log Files Archiving.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 37 of 59
More Information
Searching for Log and Trace Records
Remote Method Invocation (RMI) this is a protocol supported by the Standalone Log Viewer server. You can use RMI if you want to view log
records on systems 7.0.
SAPHostControl this is an agent protocol you can use for viewing logs and traces on systems 7.1.
Prerequisites
Open the Log Viewer tool by choosing SAP NetWeaver Administrator Problem management Logs and Traces Log Viewer .
For viewing log and trace records on systems 7.0, use the Standalone Log Viewer server. This server can be run only via the RMI. The server is running
on the system you want to monitor.
For viewing log records on systems 7.1, you need to install the SAP Host Control Agent to be able to use the SAPHostControl method.
More information:
Procedure
1. Open the Log Viewer tool by choosing SAP NetWeaver Administrator Problem management Logs and Traces Log Viewer .
2. From the Show dropdown list box, select General View and then, from the adjacent dropdown box, choose Standalone Log Viewer .
3. Choose Show Advanced Filter .
Description
Host
Enter the host name of the system you want to monitor. By default, the name of the
host is localhost . If you want to monitor a different system, enter the host name of
that system.
On Port
Enter the port number of the system you want to monitor. By default, the port
numbers for the two system types are as follows:
From the dropdown box choose one of the two methods, respectively, for offline
connecting to a server to view log records:
RMI
SAPHostControl
More Information
Searching for Log and Trace Records
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 38 of 59
Prerequisites
Open the Log Viewer tool by choosing SAP NetWeaver Administrator Problem management Logs and Traces Log Viewer .
Procedure
Predefined Development Views
Predefined View
Description
work/dev*
Shows a list of text formatted log records from all trace files located in folder work .
No filters by data source and content are set.
These are Startup Framework trace files. They give information about behaving of
the AS Java at startup.
work/std_server*.out
Shows a list of text formatted log records about the STDOUT stream processes in
the server. These trace files are located in folder work .
No filters by data source or content are set.
Shows a table of log records written in the ABAP Sys Log set of files.
No filters are set.
Look above.
More Information
Searching for Log and Trace Records
Prerequisites
Open the Log Viewer tool by choosing SAP NetWeaver Administrator
Procedure
Predefined HTTP Views
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 39 of 59
Predefined View
HTTP Access
Description
Shows a table of text formatted log records written in the http_access.log file.
These logs are related to the process of accessing a permission to a relevant HTTP
system page.
No filters by data source or content are set.
HTTP Response
Shows a table of text formatted log records written in the responses.trc file. These
traces are related to the process of accepting an answer from the HTTP page that is
called.
No filters by data source or content are set.
Servlets JSP
More Information
Searching for Log and Trace Records
Prerequisites
Open the Log Viewer tool by choosing SAP NetWeaver Administrator Problem management Logs and Traces Log Viewer.
Procedure
Predefined Logging Views
Predefined View
Description
Shows a table of merged log records that show information about the configuration
changes in the selected systems. These log records are written in
configChanges.log file. The severity of these logs is INFO.
No filters by data source or content are set.
Logging Log
Shows a table of merged log records written in logging.log file on all selected
systems. The severity of these logs is INFO.
No filters by data source or content are set.
More Information
Searching for Log and Trace Records
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 40 of 59
Prerequisites
Open the Log Viewer tool by choosing SAP NetWeaver Administrator Problem management Logs and Traces Log Viewer .
Procedure
Predefined Security Views
Predefined View
Description
You can use this view if security archived logs exists on the file system.
More information: Predefined General Views Log Archives (Java) .
Authentication Logs
Shows a table of logs that give information about logging activities of users on all
selected systems.
No filter by data source is set.
The default filter by content is set as follows: Category contains
/System/Security/ Authentication.
Authentication Traces
More Information
Searching for Log and Trace Records
Prerequisites
Open the Log Viewer tool by choosing SAP NetWeaver Administrator Problem management Logs and Traces Log Viewer .
Procedure
Predefined Server Views
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 41 of 59
Predefined View
Description
Applications (Java)
Shows a table of merged log records written in the application.log file on all
selected systems.
No filters by data source or content are set.
Bootstrap (Java)
Shows a list of text formatted log records from all log files whose name contains
bootstrap. Bootstrap is used for starting the engine.
No filters by data source or content are set.
Database (Java)
Shows a table of merged log records written in the database.log file on all
selected systems. These logs provide information about SQL maintenance of
database in the AS Java.
No filters by data source or content are set.
JVM
Shows a list of text formatted log records written in all log files whose name starts
with jvm_ and are located in folder work .
These log messages provide information about the processes in the Java Virtual
Machine (JVM).
No filters by data source or content are set.
Security (Java)
work/std_*
Shows a list of text formatted log records written in all log files whose name starts
with std_ and are located in
folder work.
These log records show messages about STDOUT processes in the AS Java.
No filters by data source or content are set.
More Information
Searching for Log and Trace Records
Procedure
Filtering Log Records by Data Source
By default, the Log Viewer shows logs and records from the whole cluster. Using this procedure, you can view log records from a particular Java instance or
server process.
1.
2.
3.
4.
5.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 42 of 59
You can make a filter inactive and keep it for future use by deselecting the Active indicator.
If you want to delete a filter, choose
Delete this row .
8. Choose Apply Data Sources .
You can make a filter inactive and keep it for future use by deselecting the Active indicator.
If you want to delete a filter, choose
Delete this row .
10. Choose Apply Logs .
More Information
Customizing Columns for Logs and Traces
Searching for Log and Trace Records
Procedure
Creating Custom Views
1. From the Show dropdown box, select General View .
2. From the adjacent dropdown box, select a view you want to use as a template for your custom view.
From the Show dropdown box, you can, as well, select Custom View and then, from the adjacent dropdown box, select <Create New View
>.
3. Choose Show Advanced Filter .
4. Set the filter criteria. Optional filter criteria are:
Filter by data source
Filter by content
Filter by log or trace name and type
More information: Filtering Logs and Traces.
5. Customize the columns to be displayed in your custom view.
More information: Customizing Columns for Logs and Traces.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 43 of 59
6. Choose Save View As , enter a name for the custom view, and then choose OK .
Procedure
1. Choose Show Search .
2. From the Search By dropdown box, select a content by which you want to search.
More information: Customizing Columns for Logs and Traces.
3. In the adjacent dropdown box select a search criterion, and then in the next field enter the search string.
When selecting the search criterion, you can select, for example, contains (wildcards) or does not contain (wildcards) and use an asterisk (*)
to represent zero or more characters in your search string.
For text formatted logs and traces, you can search only by message and by data source location.
4. To go to the next record that meets the search criteria, choose
5. To go to the previous record that meets the search criteria, choose
In the search, log records are shown in descending order by date and time. That is, the newest records are displayed at the top.
Procedure
1. Open the view, whose content you want to customize.
2. Choose Show Column Customization .
You have the following options:
If You Want To
Then
Select the column name and then select the indicator next to it.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 44 of 59
Apply the changes to all views within the current logon session
More Information
The following table gives information about all the columns available for customization, and their descriptions:
Column Name
Description
Application
The name of the application on whose behalf the log record is generated.
Arguments
Argument Objects
Additional arguments that are appended to the log record if the message type is
Java.
Category
Name of the category of the problematic area, for example, database, network,
security, to which the log record belongs.
Correlator ID
Data Source
Date
Dsr Component
Distributed Statistics Record (DSR) component on whose behalf the log record is
generated.
Dsr Transaction
Dsr User
Host
Instance
Location
Name of the source code area, for example, component, package, class, method to
which the trace message belongs.
Message
Message text.
Message Code
Node
Session
The name of the session on whose behalf the log record is generated.
Severity
Severity level of the log record: DEBUG, PATH, INFO, WARNING, ERROR, and
FATAL.
System
Thread
Time
Transaction
The name of the transaction on whose behalf the log record is generated.
User
For list formatted log and trace records, the file includes only the columns that you selected during column customization.
For text formatted log and trace records, the file includes only the complete message text.
The maximum size of the extraction file is 5 MB. If this size is exceeded, you can download the records that have been extracted so far. Then you can
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 45 of 59
continue with the extraction of the next portion of log and trace records.
Procedure
1. Extracting and Downloading the Content
1. Open the relevant view you want to extract and download.
2. Choose Download Content .
A dialog box appears.
3. To start extracting the log and trace records, choose Download .
4. To stop extracting the log and trace records, choose Stop .
You can still download the log and trace records that have been extracted so far.
5. To download log and trace records that have been extracted, choose here .
If the size of the extracted information exceeds 5 MB, the content will be downloaded in series.
6. Save the file to the file system.
Result
The log and trace records are displayed in a human-readable format in Microsoft Excel.
Context
The trace and log messages contain important information about system operation. It is helpful to check and analyze them if you experience errors or
unexpected behavior.
Using the SAP Management Console (SAP MC) log viewing functions you can:
View all system log and trace files
View developer trace files
Create stack traces for the processes
Types of Log and Trace Files:
Instance developer trace and log files contain information about the startup process. You can check these files in case of errors or unexpected behavior
during the startup process. The data from the last three restarts is retained by default.
The developer trace files of the Java instance are located in directory <Drive> :\usr\sap\ <SAPSID> \
<instance_name> \work(Windows) /usr/sap/ <SAPSID> / <instance_name> /work(UNIX), where <SAPSID> is the system ID
(for example, CE1 ) and <instance_name> is the instance name of the Java instance (for example, J03 ).
The developer trace files of the central services instance are located in directory <Drive> :\usr\sap\ <SAPSID> \
<instance_name> \work(Windows) /usr/sap/ <SAPSID> / <instance_name> /work(UNIX) , where <SAPSID> is the SAP system
ID (for example, CE1 ) and <instance_name> is the instance name of the central services instance (for example, SCS02 ).
AS Java logs
The log and trace files generated by the AS Java processes and the applications running on top of AS Java are stored in directory
<Drive> :\usr\sap\ <SAPSID> \ <instance_name> \j2ee\cluster\server <n> \log(Windows) /usr/sap/ <SAPSID> /
<instance_name> /j2ee/cluster/server <n> /log(UNIX).
Procedure
Proceed as follows to view the developer trace file of a process:
Select the relevant process and choose ShowDeveloper Trace from the context menu.
If the information in the developer trace is insufficient or too detailed, choose Increment/Decrement Trace Level to adjust the launcher trace level
to the required level.
Proceed as follows to dump the Java stack trace:
To dump Java stack trace of the server processes, select the relevant server process, and choose Dump Stack from the context menu.
To view the dump stack trace, choose Show Developer Trace (see above).
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 46 of 59
The resulting Java server stack trace is stored in the dev_server <n> file in directory <Drive> :\usr\sap\ <SAPSID> \
<instance_name> \work(Windows) /usr/sap/ <SAPSID> / <instance_name> /work(UNIX).
Proceed as follows to view logs from the SAP MC:
1. To view all the log and trace files of an instance, select the Log Files node from the tree structure of the relevant instance.
2. In the navigation pane, select the file you want to view and choose Show Log File from the context menu.
3. A dialog box appears, in which you can browse the log messages and view their detailed description.
Note
Alternatively, you can view all developer trace and log files of an instance by selecting the relevant instance, and choosing List Developer
Traces from the context menu.
To view the log file of the service, select an instance and choose Show Trace File from the context menu.
To view log records filtered by severity, time, and entries, select an instance and choose Analyze Log Files .
Related Information
SAP Management Console
Features
You can use the Command Line Log Viewer to display:
A single log or trace file
All log and trace files from a log directory
A particular number of log records from a log or trace file.
Activities
To start the Command Line Log Viewer, in the file system, go to the /usr/sap/<System ID>/<Instance number>/j2ee/configtooldirectory
and run the lv script file.
To display a single log or trace file, execute the following command: lv <Full path to the file including the file name>.
To display all log and trace files from a log directory, execute the following command: lv <Path to the directory>.
You can use this command only if all logs and traces in the directory are list formatted.
To display only the latest log records as they are written to a particular log or trace file, execute the following command: lv <Full path to the file including
the file name> -t.
To display all options that are available in the Command Line Log Viewer, execute the following command: lv h.
Prerequisites
You are in the Problem Management
Features
The Open SQL Monitors function comprises the following monitors:
SQL Trace Administration
SQL Trace Evaluation
Connection Monitor
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 47 of 59
Activities
In the Open SQL Monitors function, you can sort and filter data:
To sort tables by individual columns in ascending or descending order, click the column header.
To filter tables, choose
. A blank line appears in the table. Enter the appropriate filter string in the line and choose Enter .
You can obtain additional information for table data from the column tooltips.
There are no write filters. If the SQL Trace is active for a cluster node, all requests are traced.
Prerequisites
You are in Problem Management Database Open SQL Monitors SQL Trace Administration .
Procedure
Activating and Deactivating the SQL Trace
1. Select a cluster node from the list in the Current SQL Trace Status per Cluster Node area.
Cluster node details are displayed with SQL trace statuses, either On with a green LED icon, or Off with a grey LED icon.
2. To activate the SQL trace for the cluster node, choose the Switch Trace On button. The SQL Trace is activated for the selected cluster node. To
evaluate the trace, choose SQL Trace Evaluation .
More information: Evaluating SQL Traces
3. To set additional options for the trace, you use the Trace Options screen area:
To add stack trace information to every written trace record, select the Add Stack Trace checkbox.
To add stack trace information to trace records that take longer than a certain time period in microseconds only, enter the appropriate value in the
Threshold in Micro Seconds field.
To add stack trace information to trace records that contain matching method name calls only, enter the appropriate value in the Method Name
Contains field.
Method name matching is case-sensitive! You cannot use wildcards in method name matching.
4. To deactivate the SQL trace for the cluster node, choose the Switch Trace Off button.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 48 of 59
Prerequisites
You are in Problem Management
Database Open SQL Monitors SQL Trace Evaluation.
You have activated the SQL trace for the selected cluster node.
More information: Managing the SQL Trace
Procedure
1. In the Available SQL Traces for Evaluation screen area, select a trace and choose Display Selected Trace . Records are initially sorted in the order they
are written in. Trace records are written after the returned native JDBC method.
You can filter trace records by date and time, or by advanced selection criteria. To filter trace records by one or more of the advanced
selection criteria, choose the Advanced Filter button.
By default, the number of trace records in the list is limited to 10,000 records. To change the limit, choose the Advanced Filter button and
enter the appropriate number in the Max. Number of Records field. If there are trace records that are not displayed due to this limit, the SQL
Trace List function shows a Trace contains more data than currently displayed warning.
2. To view details for a particular record, select a record from the SQL Trace List . The Record Details screen area opens.
If the trace record is a compound record, that is, a record composed of several individual simple records, a dropdown list box appears in the
Record Details screen area. To retrieve the details for a specific simple record, choose the relevant record from the dropdown list box.
Attribute
Meaning
Time
The exact start time of the JDBC method call in millisecond precision
Duration in Microseconds
Method Name
DB Error Code
Statement
Result
Database Id
Number of Calls
J2EE Application
J2EE User
J2EE Transaction
J2EE Session
ResultSet Id
Table names
Thread
DB Session Id
Stack Trace
DSR Transaction Id
SQLTrace uses the general SAP Logging and Tracing mechanism. The SAP
Logging API trace record number thus appears in the trace.
Page 49 of 59
The Connection Monitor provides information about the connections obtained using Open and Native SQL DataSource objects.
Prerequisites
You are in Problem Management Database Open SQL Monitors Connection Monitor.
Activities
The Accessed Data Sources screen gives you an overview of all data sources that are currently accessed on each cluster node of the Java server. For each
cluster node, the following parameters are displayed:
Data Source Details
Parameter Name
Description
Data Source
The name of the data source and the SQL type it supports.
Database
The name, vendor, server (database host), and default user of the database
associated with the data source.
Connections
The number of database connections that are currently open on this data source.
Connection Requests
The number of connection requests for that data source, according to their state,
that is, Successful, Waiting, Timeout, Error.
Connection Properties
The properties for each connection, such as wait time, cleanup interval, timeout,
and so on.
You can choose a data source for which you want to monitor the established connections. The displayed list of data sources contains those that have already
been used to provide a connection.
To view the available information for a particular connection, choose the relevant data source. The Open Connections screen area displays the details for
each connection.
To view information about statements for a particular connection, choose the connection. The Open Statements screen area displays details of the SQL
statement string, the type of the statement, and so on.
Prerequisites
You are in Problem Management
Activities
On the Accessed Catalog Buffers screen, you can choose a catalog buffer instance that you want to monitor. A catalog buffer is displayed along with the
following details:
Catalog Buffer Details
Parameter Name
Description
Buffer ID
A unique identifier for a catalog buffer instance within a cluster node. It is created by
the concatenation of the database host, the database name and the database
schema.
References
Max
Current
Free
Displacements
When you choose a catalog buffer from the list, the Buffered Catalog Tables screen area displays a list with tables for that buffer ID.
To view the catalog table columns, select a table from the list. The Catalog Table Columns screen area displays data for each column in the selected table.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 50 of 59
Prerequisites
You are in Problem Management
Activities
To view detailed data about the buffer, select a buffer ID. The Table Buffer Details screen area displays detailed data about the selected buffer in three tabs,
Administration , Displacement , and Buffered Objects .
To view administration details, choose the Administration tab. The Administration tab displays the following parameters:
General Administration
Parameter Name
Description
Startup Date
Reset Date
Reinstall Date
Resets
Reinstalls
Is Ready
Storage Information
Parameter Name
Description
Free Bytes
Reload Delay
Number of Objects
Number of Tables
Access Statistics
Parameter Name
Description
Requests
Hits
Efficiency
To view displacement details, choose the Displacement tab. The Displacement tab displays the following parameters:
General Statistics
Parameter Name
Description
Is Displacement On
Number of Displacements
Interval Statistics
Parameter Name
Description
Displaced Objects
Displaced Tables
Size of the load priority queue, which is used for determining which objects are to
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 51 of 59
be displaced.
Displaced Data
Displaced Bytes
Summary Statistics
Parameter Name
Description
Displaced Objects
Displaced Tables
Displaced Data
Displaced Bytes
To view buffered objects in the selected table buffer, choose the Buffered Objects tab.
Prerequisites
You are in Problem Management Database Open SQL Monitors
Activities
On the Available Sync Log Entries screen, you can view the following details about all synchronization requests pertaining to a single database transaction:
Parameter Name
Description
Time Stamp
Creation timestamp of the BC_SYNCLOG table rows; the timestamps are generated
by the underlying database server.
Cluster Node
Buffer Handler Id
Unique identifier for the buffer handlers, which consists of the category (table or
catalog buffer), host, instance, and DataSource name.
Request
Prerequisites
You are in Problem Management Database Open SQL Monitors Table Statistics Monitor .
Activities
To view statistics, select a cluster node from the Current Table Statistics Status area. The Available Table Statistics Items area opens. The area displays
each table in the cluster with statement statistics.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 52 of 59
Prerequisites
You are in Problem Management
Activities
To view method execution details for a particular DataSource, select the DataSource. The SQL Statistics Details area opens. To view database access
statistics about queries, choose the Queries tab. For each SQL statement, statistical details about Prepare, executeQuery and next calls are
displayed. To view details about the executed DML statements regarding Prepare, executeUpdate and executeBatch calls, choose the DMLs tab.
You need appropriate authorization to use the Native DB Monitors. Without the appropriate authorization, the monitors do not work correctly.
Prerequisites
You are in Problem Management
Features
The Native DB Monitors function consists of the following monitors:
Database Activity
Shows a database-dependent view of the current database activity. The displayed columns are different depending on the RDBMS.
Refreshing the list may take longer on databases with a high number of parallel sessions.
Current Exclusive Lock Wait Situations
Shows processes currently holding or waiting for locks.
The Current Exclusive Lock Wait Situations on Database table is generally the same for all supported databases. However, the column
content can have different meanings depending on the RDBMS.
You cannot sort or filter the Current Exclusive Lock Wait Situations on Database table.
Activities
To view database activity for a DataSource on a underlying database, select a DataSource in the Native SQL and Open SQL Datasources screen area and
choose Show DB Activity . The Current Database Activity area opens.
To view lock situations, select a DataSource in the Native SQL and Open SQL Datasources screen area and choose Show Current Exclusive Lock Wait
Situations . The Current Exclusive Lock Wait Situations on Database area opens. Normally, exclusive lock situations do not last long and thus it is normal
(and desired) for the table to be empty.
You can use the Database Activity, Current Exclusive Lock Wait Situations, and the Connection Monitor together to investigate reasons for
lock wait situations. We recommend that you open the three monitors in parallel in separate browser windows to facilitate such analyses.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 53 of 59
Purpose
Web Services Reliable Messaging (WSRM) ensures that message exchange between a service provider and a service consumer is completed without fault.
Here messages are combined into sequences. The reliability of sequence transmission is adopted by the Web service runtime. Using the analysis tools of the
sequence monitor, you can find and remove any errors that occur during transmission.
You use the Sequence Monitor in the following cases:
1. To monitor the sequence status
2. To end/restart sequences with errors
Implementation Notes
You can call the Sequence Monitor in the local SAP NetWeaver Administrator ( SOA Management Monitoring Sequence Monitoring ) or in the
NetWeaver Administrator for PI (refer to
Features
The sequence monitor comprises three areas.
Selection Criteria
Sequence Overview
Sequence Detail
Selection Criteria
This area contains the following sections:
Common Criteria
Additional Criteria
Inputs in the fields under Additional Criteria invalidate the inputs under General Criteria . The Location field is an exception.
For more information, refer to the section Choosing Selection Criteria.
Sequence Overview
In the sequence overview, you see a list of the selected sequences. When you choose a sequence, more details are displayed. It is possible to end or restart
individual sequences.
For more information, refer to the section Checking the Sequence Overview.
Sequence Details
In the Sequence Header tab, you will find general information on the messages contained in the sequences.
In the Messages tab, you will see details on the status of the messages contained in the sequence.
For more information, refer to the section Analysis of Sequence Details.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 54 of 59
Sequences contain a unique identifier. Messages in a sequence are numbered consecutively. The WS-RM sequence header in the SOAP message identifies
the sequence that a message belongs to.
WS Reliable Messaging implementation at the sender and receiver locations ensures that messages are confirmed. For this purpose, the specification defines
the format of an acknowledgement that the receiver sends to the sender as confirmation. The sender waits for the confirmation and, if necessary, keeps
sending the message until the confirmation is received.
To avoid unnecessary network communication, the receiver does not have to confirm the receipt of every single message individually, but can confirm whole
(not necessarily related) messages in one acknowledgement - for example, confirm that messages 1, 3, and 5 have been correctly received.
Since messages 2 and 4 were not confirmed, they are sent again. The sequence is only finished when it has been confirmed that these messages have been
successfully received.
Errors during the transfer of a sequence can refer to the sequence or to the message. When a sequence is created, a remote message call is executed. This
uses the same configuration settings as the first message that was sent using the sequence. If the message call terminates with an error (for example, Login
not possible or Configuration missing on provider side ), the cause of the error is displayed. As soon as the cause of the error is resolved (for example, after
correct configuration), the sequence can be restarted using the Sequence Monitor. If there is an error relating to a message, the cause of the error can be
displayed in the Sequence Monitor. The message key, the message status, and the user name that were used to process the message are displayed.
Procedure
1. Specify the required selection criteria.
The following criteria are available:
General Criteria
Criterion
User
Location
Function:
Name of the person who started the logical sequence on the consumer side of Web
Services or the name of the logon user on the side of the provider.
All sequences ( Consumer Provider) or only sequences of the provider or
consumer
Sequence Status
Active
Sequence is open (in processing)
Terminated
Sequence is closed and the messages have been delivered or have failed
Faulty
Sequence is faulty
All
Start Date
Combine the time specifications with the above fields for example, the sequence
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 55 of 59
End Date
status.
Start Time
End Time
Bear in mind that a faulty or open sequence will be retained for a lengthy
period of time. The start time must be set accordingly.
If no end time has been specified, the current time will be taken automatically.
Here the system accesses the configuration for the time zone in the JEE
Engine.
It is only possible to search for individual sequence and message keys if, for example, faulty sequences have been found using general search criteria.
Bear in mind that entries in the fields under Enhanced Criteria invalidate the entries under General Criteria . The Location field is an exception.
Enhanced Search Criteria
Logical Sequence ID
Technical Sequence ID
Message ID
It is only possible to search for individual sequence and message keys if, for example, faulty sequences have been found using general search
criteria and the corresponding keys are available.
Bear in mind that entries in the fields under Enhanced Criteria invalidate the entries under General Criteria . The Location field is an
exception.
2. Choose Start Selection.
Procedure
1. Check the status of the sequences listed.
In the upper right-hand corner of the sequence overview, choose the first pushbutton to change the number of lines displayed in the overview.
As standard, 10 lines are displayed. In many cases, it can be appropriate to increase the number of lines to 20, for example.
In the sequence overview, you see the following columns:
Column
Function:
Status
Terminated
Active
Faulty
Location
Consumer or Provider
Logical Sequence ID
Technical Sequence ID
Page 56 of 59
Use
By analyzing the details of a sequence, you can find out the cause of any faulty message transmission.
Procedure
Analysis of a Successfully Transmitted Sequence
1. In the sequence overview, select a sequence with the status Terminated (
2. Check the sequence details under the Properties tab.
).
The field entitled Last Message Indicator Number tells you that the sequence comprises four messages.
The field entitled Successful Messages also contains the number 4. You can therefore safely assume that the sequence has been transmitted
successfully.
3. Call up the Messages tab page.
After a lapse of 24 hours, all the message contents are deleted. The header information, however, is retained for a short while.
Analysis of a Faultily Transmitted Sequence
1. In the sequence overview, select a sequence with the status Faulty (
).
Make sure that you enter Consumer Provider as a selection criterion in the Location field to display all faulty sequences.
2. Check the sequence details under the Properties tab.
The sequence contains four messages. Only one message has been transmitted successfully.
3. Call up the Messages tab page.
If you check the quick info for message 2, you will see that this message has the status Non delivered . Message 3 is missing in the messages list.
4. Enter the name of the logical sequence as a selection criterion in order to find out why message 3 does not appear in the list on the provider side.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 57 of 59
The message analysis on the consumer side tells you that message 3 has the status To_Be_Delivered (
provider and therefore did not appear in the list of messages.
With the help of the message ID, you can analyze messages in the Message Monitor as well. You can navigate directly to the Message
Monitor.
Rejecting a Sequence
1. Select a sequence with the status Faulty or Active.
2. Choose Reject Selected Sequence .
If you reject a sequence, the status of all messages is set to Failed . If a message has the status Delivered this status remains the same.
Before the sequence is terminated, the status of the messages could look like this:
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 58 of 59
Message 2 and 4 have the status Delivering. Message 1 has the status Delivered.
After termination, the status of messages 2 and 4 changes to Failed .
The status of the sequence is changed from Active to Terminated.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 59 of 59