Enterprise Portal 6.0 SP1

Enterprise Portal 6.
0 SP1
System Landscape Monitoring
Best Practice for Solution Management

Version Date: March 2004
The latest version of this Best Practice can always be
obtained through the SAP Solution Manager
Best Practice: Enterprise Portal 6.0 SP1 System Landscape Monitoring 2
Contents
Applicability, Goals, and Requirements................................................................................................... 2
Best Practice Procedure and Verification ................................................................................................ 3
How to Use this Best Practice ........................................................................................................... 3
Introduction.................................................................................................................................. 5
SAP Enterprise Portal Overview ................................................................................................. 5
General Preparation .................................................................................................................. 10
Installing and Configuring the Monitoring Infrastructure on the Portal Landscape Hosts ......... 12
SAPCCMSR and SAPOsCol..................................................................................................... 12
Process of the automated installation: ...................................................................................... 12
Installing JMON ......................................................................................................................... 24
Monitoring the J2EE Engine...................................................................................................... 25
Setting Up Log File Alerting and Monitoring.............................................................................. 28
Availability Monitoring................................................................................................................ 39
Availability monitoring of the J2EE Engine...................................................................................... 39
GRMG Check of the Portal based on HTTPS........................................................................... 49
Availability Check by Process monitoring ................................................................................. 74
Setting Up Central Configuration .............................................................................................. 76
Single Activity Trace.................................................................................................................. 79
Manually adding new monitor sets to CCMS ............................................................................ 83
Defining Automatic Alert Notification in the Central Monitoring System ................................... 91
Further Information .............................................................................................................................. 102
Appendix.................................................................................................................................. 102
Applicability, Goals, and Requirements

Goal of Using this Service
The Enterprise Portal Solution Landscape consists of several components that need to be monitored both
from a technical as well as from a business process perspective. The aim of this Best Practice is to briefly
show how to set up System Monitoring in an EP 6.0 SP1 System Landscape for its different technical
components.
This is not an in-depth description of the whole SAP monitoring architecture. However, appropriate
examples will be given. Where necessary, references to related documents will be cited.
Alternative Practices
This Best Practice focuses on technical issues.
The Best Practice Central System Monitoring for mySAP.com provides information about system
monitoring and the use of the Solution Manager. If you want to integrate your SRM solution into the system
monitoring refer to the Best Practice mySAP SRM 2.0 System Landscape Monitoring. If you want to
integrate CRM refer to Best Practice CRM Release 4.0 SP03 Monitoring Installation Guide.
2004 SAP AG
Staff and Skills Requirements

To implement this Best Practice, you require a system administration team with technical knowledge about
the system components used in an EP solution landscape. To be able to successfully perform the steps of
this Best Practice, the team/user requires root/administrator permissions for the Operating System (OS), the
Central Monitoring System and in the Portal.
System Requirements
We recommend that you use a separate R/3 based system for the Solution Manager. This system should
also be used as the main system for the CCMS, that is, all components send their data to this R/3 based
monitoring system.
Duration and Timing

Timing
The best time to apply this Best Practice is after installation of the EP Solution Landscape.
Best Practice Procedure and Verification

How to Use this Best Practice
Follow the order of sections of this Best Practice when implementing the EP Solution Monitoring. This
document consist of 5 main parts:
Introduction of the Best Practice and the EP 6.0 monitoring concept
Set up in detail: automated set up
Set up in detail: further information manual set up as background information and due to individual
customizing your monitoring and troubleshooting
CCMS customizing
Appendix with information sources, notes, example files
If you only use a printout, please be aware that there are hyperlinks in the document referring to related
chapters in this document.
Requirements
For information about the permitted release and patch status on which this Best Practice is based, see EP
6.0 SP1 PAM. This document is available under:
http://service.sap.com/ep Product Information Enterprise Portal 6.0 Platform Availability Matrix.
Enterprise Portal 6.0 SP1
SAP J2EE Engine 6.20
TREX 6.0 SP1 (on Unix TREX 6.0 SP1 patch 1)
Additional the following component versions are required:
SAPCCMSR: Patch collection 2003/6
SAPOsCol: Version 20.79
Standalone Log Viewer 6.30 (currently delivered with attachment of SAP note# 644783, soon there
will be an own component on SAP Service Marketplace
Web AS based monitoring system: Basis Support Package: 29
2004 SAP AG
Important: Using this document
This document refers to binarys, scripts and templates, delivered in an *.SAR (SAP archive).
You have to download the SAR-File from SAP Service Marketplace, alias patches SAP
Enterprise Portal SAP Enterprise Portal 6.0 Binary Patches EP_MONITORING.
During installation, create directory moni_temp on each host of your EP6 environment. Copy the appropriate
archive for your operating system and the associated version of SAPCAR compression program to this
directory and decompress the archive (under UNIX, you must first set the execute flag for the program with
command chmod a+x sapcar):
sapcar xvf <package>
Throughout this Best Practice, you will repeatedly require files from the unpacked directory. In each case,
this document will refer to directory moni_temp that you have just created, such as:
Switch to directory moni_temp and call file ....
Copy file ... from directory moni_temp to directory ...
The files in the archive were entered when this Best Practice was created in October 2003. If you are using
this document later, you have to check that the files in the archive are up-to-date. Newer versions available
on SAP Service Marketplace should be downloaded.
Example Landscape
2004 SAP AG
Example Monitoring Set
Introduction
A fully installed solution monitoring enables you to to react appropriately and quickly to each kind of
problem. This can help prevent unnecessary downtimes or loss of data.This Best Practice describes the
efficient implementation of a monitoring infrastructure for EP 6.0. These guidelines require that the following
information is provided centrally for as many components as possible:
Central Log File Monitoring
Component Availability
Single Activity Trace
Central Configuration Information.
This Best Practice describes the configuration of these requirements for EP6.0 SP1.
As a prerequisite for using this Best Practice, the system in which the information listed above is to be
centrally displayed should fulfill the following conditions:
The central monitoring system / Solution Manager has SAP Basis 6.20 and Basis Support Package
29 (this system is abbreviated to CEN in subsequent sections).
The Transport Management System is configured in CEN.
The result of working through this Best Practice is that you will see the various components of an EP6
environment in the alert monitor of the monitoring architecture (transaction RZ20). These components are
now centrally monitored, and you can see all relevant system management information and performance
values and alerts for the EP6 environment in the alert monitor.
SAP Enterprise Portal Overview

SAP Enterprise Portal addresses one of the most pressing problems facing enterprise IT organizations
today how to provide an integrated, single point of access to heterogeneous IT systems. Todays modern
IT landscapes typically contain many diverse technologies acquired from different vendors or developed in-
house and involve a highly distributed infrastructure based on both open and proprietary protocols and
standards. As part of SAP NetWeaver the SAP Enterprise Portal unifies enterprise applications, information,
and services from both SAP and non-SAP sources into a coherent interface. With its role-based content and
2004 SAP AG
collaboration tools, SAP Enterprise Portal integrates people, and with its knowledge management of
unstructured data, and its unification of structured data, it integrates information.
For its users, the portal provides a window onto information both in their organization and outside it, along
with the tools to manage this knowledge, to analyze and interrelate it, and to share and collaborate on the
basis of it.
The core technology components which bring this breadth and depth of information to the portal desktop
make up its content, and the basic unit of this content is the iView. An iView is a mini-application which
fetches information from any of a variety of sources, such as databases, enterprise applications, file
systems, and the Web, returning up-to-the-minute information each time it is launched.
SAP Enterprise Portal Architecture

SAP Enterprise Portal is platform-independent, and therefore able to operate on both UNIX and Microsoft
Windows operating systems. It installs and runs on a component of the SAP Web Application Server, the
SAP J2EE Engine, which is a proprietary Java application server based on the Java 2 Enterprise Edition
(J2EE) standard. SAP Enterprise Portal consists of the Portal Platform, Knowledge Management, and
Collaboration. The Portal Platform contains:
Portal Framework:
provides components and services for the creation and running of portal content, such as iViews, pages,
worksets and roles. It also supplies a persistence layer, the Portal Content Directory, which runs against an
Oracle or Microsoft SQL database, and user management.
Unification:
enables the integration of multiple information sources of structured data.
Connector Framework:
supplies the pipelines of communication between the portal and backend applications.
Knowledge Management (KM):
KM is implement in order to enable unstructured content management, and sophisticated search and
retrieval functionality over unstructured content in disparate information repositories. It comprises CM, TREX
and Collaboration.
Content Management (CM):
with CM, you can author, store, manage, and display documents.
Retrieval and Classification (TREX):
with TREX, you can carry out intelligent searches and text mining of extensive document sets and structure
these sets sensibly using document classification.
Collaboration:
in SAP Enterprise Portal it is a set of tools designed to facilitate cooperation and communication that is both
synchronous and asynchronous. It lets portal users create virtual rooms in which they can organize
themselves into groups, for example, teams or projects. It also allows portal users to communicate through
interactive online meetings, with instant messaging and application sharing capabilities. Further, it can
integrate the e-mail and scheduling services of groupware.
Figure 1: The following illustration displays the components of SAP Enterprise Portal:
2004 SAP AG
Short Description of the Monitoring and Supportability

Requirements
Log File Monitoring
Java based applications write messages to log files. In complex applications, such as EP6, important
messages can be distributed across significantly more than 100 log files. To ensure stable operation, these
log files should be regularly checked for error messages.
SAP provides a mechanism for automatically analyzing log files. The CCMS agent SAPCCMSR checks the
log files every minute for preset search patterns. If the agent finds a pattern, it reports an alert to the central
monitoring system. The administrator can be informed from there on the basis of the alert.
As an administrator, you can see all of the checked log files in the Alert Monitor (transaction RZ20) of the
central monitoring system. If an error occurs, you can expand the corresponding sub tree in the log file
monitoring monitor, and obtain the name and path of the log file in which an error was logged from the
complete name node. You can then view the entire log file in the Standalone Log Viewer, and make
appropriate repairs based on your analysis of the log. If the relevant log file is not displayed in the
Standalone Log Viewer, register the file.
2004 SAP AG
EP60
Figure 2:
Advantages of central log file monitoring and alerts:

Automatic regular checking of the many log files.
The administrator can be automatically notified if problems occur.
The Standalone Log Viewer provides you with central access to all log files for your EP6 landscape
(even if the SAP J2EE Engine is no longer running).
The Standalone Log Viewer can also display ASCII-based logs for other applications, such as the
database.
Availability Monitoring
Availability cannot be unambiguously defined with regard to IT components. For example, availability can
mean the existence of a process at operating system level. Other definitions of availability could, for
example, include the provision of a service within a certain time, or the average time for executing a user
action between 08:00 - 18:00.
SAP provides a number of different mechanisms for availability monitoring. The mechanisms have the
following in common:
The availability information is usually technical.
Once it has been set up, the availability check is performed periodically and without user interaction.
The result of the check is reported in the central CCMS and therefore also in the Solution Manager. This
means that an availability monitor can be set up centrally that displays the status of the individual
components. It is also possible to implement automation and notifications using auto reactions.
At application level, availability is checked with the Generic Request and Message Generator (GRMG).
2004 SAP AG
Figure 3:
With GRMG, the central system periodically calls a GRMG application using a URL. The GRMG application
performs component-specific checks and returns the result of the checks to the central system.
SAP delivers a GRMG application for EP6, TREX and for the SAP J2EE Engine.
The availability check can be implemented differently for C-based components. For example, the availability
of the IPC is checked using a shared library (data supplier), which is periodically started by the SAPCCMSR
agent.
If a GRMG check is not possible or not useful for a component, it is possible to at least prove the existence
of the corresponding process at operating system level. A check of this type establishes the necessary (but
insufficient) prerequisite for component availability. The check is performed by the SAP program SAPOsCol
and the SAPCCMSR agent.
Central Configuration
An EP6 system landscape consists of a large number of individual components. If errors occur, it is
important for you to be able to see configuration and version information quickly and centrally, since this is
often important for solving problems.
Components can send their configuration and version information to a central monitoring system using the
SAPCCMSR agent. This information is updated once a minute, and is visible in the CCMS and in the
Solution Manager.

You can sequentially record the activities of individual requests and their components for a defined period of
time, and then analyze their performance and errors in the Log Viewer. Technically, activity tracing is based
on the Java Application Responsetime Measurement (JARM).
In the portal the activity trace is related to a user and has a default time interval for 30 minutes. You can
change this time interval.
The activity tracing for the TREX needs to be enabled separately. The internal TREX procedure steps are
recorded separately. This is of interest if actions like search, classify or create index are to be analyzed.
2004 SAP AG
Remote Connectivity
With a fully installed automated solution monitoring and remote connectivity you enable SAP support to also
react appropriately and quickly to every kind of problem. Remote Connectivity set up is only introduced here
and not described.
Figure 4:
General Preparation
Unless otherwise explicitly stated, the following actions at operating system level should always be
performed using the user under which the J2EE Engine runs (<J2EEadm>):
Importing and post processing transport request
Installing agent/SAPOsCol
JMON
Importing a Transport Request into the Central

Monitoring System / Solution Manager
This section describes the process for an empty system. Please check before hand if the containers for the
transport already exist in your central monitoring system.
Three particular transport requests adjust the central monitoring system/Solution Manager for the special
features of monitoring an EP landscape. To do this, the transport environment of CEN must already be
configured.
The transport requests contain:
The CSMREG user profile
2004 SAP AG
CATT process for creating CSMREG

Setup for CCMS specific background jobs
Extension of the functions of transaction GRMG
EP JSTF collection monitor set
Import the transport requests into your central monitoring system / Solution Manager CEN as follows:
Switch to directory moni_temp.
Copy the files R900051.nbs, R900071.nbs, R079283.bce to <DIR_TRANS>\data.
Copy the files K900051.nbs , K900071.nbs, and K079283.bce to <DIR_TRANS>\cofiles.
If you do not know the path of the directory <DIR_TRANS>, call transaction AL11 by entering
/nal11 in the command field. The path of the directory is displayed there.
Log on to CEN in client 000 as an administrator.
Start transaction STMS, by entering /nstms in the command field. Choose F5. Double click <CEN>.
For each of the three requests, choose Extras Other Requests Add, and enter the requests
numbers NBSK900051, NBSK900071, and BCEK079130 in that order, and confirm your entries
and the subsequent popup.
Place the cursor on each of the transport request numbers and choose <Control>+F11 in each
case. Enter 000 as the target client and confirm your entry and the subsequent popup.
The transport request initially has the status (Import Queue). Update the display by choosing
Refresh, until this status changes.
Post Processing in Client 000 in CEN

First start transaction SCC4 by entering /nscc4 in the command field.
Double click client 000 and check in the restrictions when starting CATT and eCATT group box
whether the entry eCATT and CATT allowed is selected. If this is not the case, choose Display
Change, and select this entry. Save your changes.
If the predefined currency is invalid, enter a valid currency and save your entry.
Create the CSMREG Role
Start transaction PFCG by entering /npfcg in the command field.
Enter CSMREG as the role and choose Change.
Switch to the authorizations tab page and choose Change Authorization Data.
Choose Generate, and confirm the profile name with ENTER.
Save your entries.
Create the CSMREG User
Start transaction SCAT by entering /nscat in the command field.
Enter ZCSMREG_USER_ANLEGEN as the test case and choose Execute or F8. Leave all values
unchanged, and choose Execute.
You now run through transaction SU01 automatically, by entering /nsu01 in the command field. All
settings are predefined. You can change the values, or simply choose ENTER repeatedly:
Enter an initial password on tab page Logon Data. Repeat the initial password in field Repeat
Password.
Choose ENTER repeatedly, until the test plan has been completely run through and the test plan
log appears. If you do not enter an initial password, the initial password Init is used.
Create CCMS specific background jobs
2004 SAP AG
Start transaction SCAT by entering /nscat in the command field.

Enter ZCCMSJOBS as the test case and choose Execute. Leave all values unchanged, and choose
Execute.
Choose ENTER repeatedly, until transaction SCAT appears again.
If you made changes in transaction SCC4, reverse your changes, and save.
Create your JSTF monitor set
Start transaction RZ20 by entering /nrz20 in the command field.
Choose Extras Activate Maintenance Function.
Place the cursor on EP JSTF Collection and choose Copy.
Name your monitor set (<my monitor set>) and choose ENTER.
Further Recommendations
All the components included in the transport can be created manually. The how-to is described in a later
chapter of this Best Practice. Except the extension of the functions of transaction GRMG, which currently for
6.20 only delivered with the transport, future delivery by SP is planned. With Web AS 6.30 they are a
standard feature.
Installing and Configuring the Monitoring

Infrastructure on the Portal Landscape Hosts
SAPCCMSR and SAPOsCol
The SAP programs SAPCCMSR and SAPOsCol should be installed on all hosts in your
monitored system landscape (EP Portal, TREX, and DB).
The operating system collector SAPOSCOL is a stand-alone program that runs in the operating system
background. It runs independently of SAP instances exactly once per monitored host. SAPOSCOL collects
data about operating system resources, including:
Usage of virtual and physical memory

CPU utilization
Utilization of physical disks and file systems
Resource usage of running processes
Process monitoring
SAPOsCol makes the data available to various applications and all SAP instances on a host using a
segment of the shared memory. A CCMS agent or a dialog work process reads the data from the shared
memory. You can display the data in various monitoring architecture monitors or in the operating system
monitor (transactions OS07 and ST06). If the operating system data is read and sent by CCMS agents, you
can display operating system data for any hosts in a central system.
SAPCCMSR creates the connection between the host and the central monitoring system / Solution
Manager.
Process of the automated installation:
2004 SAP AG
If the automated installation fails, you can use the Further Information sapccmsr manual
installation.
Microsoft Windows only:
Switch to directory moni_temp and enter install.cmd at the operating system command prompt.
If there is not yet a share \\<host>\saploc, specify a drive letter for the installation.
SAPOsCol is automatically installed as a service with a manual start and the file dev_proc (process
monitoring) is created.
Start the Windows Service Manager, double click service SAPOsCol and set the service type to
Automatic.
Switch to directory \\<host>\saploc\prfclog\sapccmsr.
At operating system level, replace all fields in the csmconf_sc with $<PAR>$ (ensure that you
also replace the $ characters when doing so). You can see exactly which changes you have to
make in the table in section UNIX only below.
Start the installation of the agent by entering (one command, please enter in one row):
sapccmsr -R -f \\<HOST>\saploc\prfclog\sapccmsr\csmconf_sc
pf=\\<HOST>\saploc\prfclog\sapccmsr\j2ee.pf
Check the file sapccmsr.install.log for errors.
UNIX only
Switch to directory moni_temp.

SAPOsCol must be installed by a user with root permissions.
Enter:
su root
./install_root.sh
(be sure that the script is executable - chmod a+x install_root.sh)

As user, enter the user under which the SAP J2EE Engine runs (default value is c11adm):
J2EE-User [c11adm]
<J2EEadm>
Confirm the group of the user specified above.
To return to the user <J2EEadm> after the script is completed enter:
exit
To configure the directories at operating system level, enter
./install_user.sh.
(make sure that the script is executable)

You can ignore error messages of the type Could not move...
Confirm a message Continue with ENTER.
Switch to directory /usr/sap/tmp/sapccmsr.
Note the output of the script install_user.sh.
You can also use the output of the script from install_user.sh.log to simplify additional
configuration steps.
At operating system level, replace all fields with $<PAR>$ in file csmconf_sc (ensure that you also
replace the $ characters when doing so).
Make the following changes:
2004 SAP AG
Parameter Name Description
Data for the central monitoring system
$SID$ System ID of the central monitoring system
$CEN_HOST$ Host name of an application server in CEN
$INSTANCE_NUMBER System number of CEN

_OF_CEN$
CEN_ADMIN_USER section
A user with administrator authorization (such as DDIC) is required once here
$CLIENT$ Client in CEN, in which the user exists
$USER$ User with administrator authorization
$PASSWD$ Associated password.

It is not stored.
CEN_CSMREG_USER section
You enter the communication user that you created under Importing a Transport
Request into the Central Monitoring System / Solution Manager [page 10] here.
$CLIENT$ Client in CEN, in which the user exists
$USER_CSMREG$ Name of the user
$PASSWD$ Associated password.

It is stored in an encrypted format in the secure store.
The file csmconf_sc is identical for all monitored hosts. After editing the file once, you can
therefore use it for all additional hosts.
Start the agent installation by entering the following (one command):
/usr/sap/ccms/bin/sapccmsr R -f /usr/sap/tmp/sapccmsr/csmconf_sc.
Check file sapccmsr.install.log in the current directory for errors.
You can ignore an error message of the type Could not find <file>.old.
Start the agent manually by entering the following (one command):
/usr/sap/ccms/bin/sapccmsr DCCMS
pf=/usr/sap/tmp/sapccmsr/j2ee.pf
SAPCCMSR and SAPOsCol are to be started when the server is started. Therefore create an
entry in the appropriate operating system file (such as INITTAB); this is usually in directory /etc,
and can only be entered using the root user:
/usr/sap/ccms/bin/saposcol -l
/usr/sap/ccms/bin/sapccmsr DCCMS pf=/usr/sap/tmp/sapccmsr/j2ee.pf
2004 SAP AG
Further Information SAPCCMSR

If for any reason it is not possible for you to apply the Best Practice as described above you will find here
additional information for installing the necessary components manually.
Process for alternative manual installation of the

SAPCCMSR agent
Download the SAPCCMSR.EXE for the operating system of your choice into the agents working
directory (see SAP note 209834) from the service marketplace alias systemmanagement System
Monitoring and Alert Management Download Area.
Overview of the directories used by the saposcol and the sapccmsr:
Operating System Directory Function
UNIX /usr/sap/tmp/sapccmsr working directory of sapccmsr
/usr/sap/tmp/logmon home of templates
/usr/sap/ccms/bin home of executables
Windows /usr/sap/ needs to be shared with share
name saploc
\usr\sap\prfclog home of saposcol
\usr\sap\prfclog\sapccmsr working directory and home of
executables of sapccmsr
\usr\sap\tmp working directory
Unix:
Create the following directories as root:
mkdir /usr/sap/ccms
mkdir /usr/sap/ccms/32bit
mkdir /usr/sap/ccms/bin
mkdir /usr/sap/tmp (if not already exist)
mkdir /usr/sap/tmp/sapccmsr
mkdir /usr/sap/tmp/logmon
chown R j2eeadm:sapsys /usr/sap/ccms
chown R j2eeadm:sapsys /usr/sap/tmp
Download the files into a directory for example /usr/sap/ccms/32bit.

Unpack the downloaded file from directory /usr/sap/ccms/32bit with the SAPCAR tool.
Check if the downloads SAPCAR have executable rights. If not you can do something like
cd /usr/sap/ccms/32bit
mv SAPCAR_3-10001671.EXE SAPCAR
chmod 775 SAPCAR
Unpack the file for example ./SAPCAR.EXE xvf CCMAGENT<download#>.SAR
2004 SAP AG
Check the unpacked files via command ls ltr

The following files will appear:
sapccmsr
ccmsping
sapcm3x
sapccm4x
Remove all unpacked files except sapccmsr:

rm ccmsping
rm sapcm3x
rm sapccm4x
Copy file sapccmsr into directory /usr/sap/bin/ccms.

cp sapccmsr /usr/sap/ccms/bin/sapccmsr
The subdirectory sapccmsr will be created during the installation process of the agent.
If the file csmconf does not exist and no f parameter is set during registration (see below) the
file csmconf will be created automatically during registration.
Dialog SAPCCMSR Registration
Register the agent using the following command:
(During registration, the agent automatically creates an RFC connection to the central monitoring
system)
/usr/sap/ccms/bin/sapccmsr R to register
/usr/sap/ccms/bin/sapccmsr U to unregister
Windows
If you want to start the sapccmsr as an NT service you need to register the SAPCCMSR with
the profile file. For example \usr\sap\ccms\sapccmsr\sapssmcr R
pf=/usr/sap/prfclog/sapccmsr/j2ee.pf
Unix
You can give the parameters later during startup of SAPCCMSR.
Additionally you can use the parameter f=<file name>. This is the name of the configuration file for
the dialog-free installation. The default file name is /usr/sap/tmp/sapccmsr/csmconf . The SAPCCMSR
agent will create this file during registration automatically.
The file csmconf_sc is identical for all monitored hosts. After editing the file once, you can
therefore use it for all additional hosts.
Start the agent installation by entering the following (one command):
/usr/sap/ccms/bin/sapccmsr R -f /usr/sap/tmp/sapccmsr/csmconf_sc.
Check file sapccmsr.install.log in the current directory for any errors.

Registration of the agent creates a log file in the working directory, which is
/usr/sap/tmp/sapccmsr/sapccmsr.log.
Check the file for any errors and warnings.
2004 SAP AG
Be aware, that you need a user for every central monitoring system. You must also enter a valid
SAP user in the central monitoring system that is used once to create an RFC connection to the
agent. This user requires the authorization to execute transactions RZ20/21 (S_RZL_ADM with
authorization field ACTVT and value 01) and to enter an RFC destination using transaction
SM59 (S_ADMI_FCD with authorization field S_ADMI_FCD and value NADM.
For more information see CCMS Agents: Features, Installation, Usage.
Information necessary for SAPCCMSR registrations can be seen below in the example csmconf file.
Option: dialog free SAPCCMSR Registration

Create a configuration file csmconf.
You can also use the automatically created csmconf from inside the registration working directory with a
dialog as seen above.
This file is required for a dialog-free installation.
Save the file in the CCMS agent working directory.
Using a configuration file allows an unsupervised installation to run and the file remains unchanged when
installing the CCMS agent on several servers. The content of the csmconf should appear as shown below.
Make sure all parameters are set to match your configuration and system information.
For a detailed explanation refer to the CCMS Agent Description document. See also service marketplace
alias systemmanagement System Monitoring and Alert Management Media Library Documentation
CCMS Agents: Features, Installation. Usage.
Example: Content of the csmconf file
CEN_CONFIG
CEN_SYSID=<SID of monitoring R/3 system>
.
CEN_ADMIN_USER
CEN_ADMIN_CLIENT=<client>
CEN_ADMIN_USERID=<valid user>
CEN_ADMIN_LANG=<language>
CEN_ADMIN_LOADBALANCING=n
CEN_ADMIN_ASHOST=<hostname of application server>
CEN_ADMIN_SYSNR=<instance no. of monitoring R/3 system>
CEN_ADMIN_TRACE=0
CEN_ADMIN_MSHOST=<hostname of message server>
CEN_ADMIN_PASSWORD=<Password of the user>
.
CEN_GATEWAY
CEN_GATEWAY_HOST=<hostname of gateway server>
CEN_GATEWAY_SYSNR=<instance no. of the gateway of the monitoring R/3 system>
CEN_GATEWAY_TRACE=0
.
CEN_CSMREG_USER
CEN_CSMREG_CLIENT=<client>
CEN_CSMREG_USERID=<valid user>
CEN_CSMREG_LANG=<language>
CEN_CSMREG_LOADBALANCING=n
CEN_CSMREG_ASHOST=<hostname of application server>
CEN_CSMREG_SYSNR=<instance no. of monitoring R/3 system>
2004 SAP AG
CEN_CSMREG_TRACE=0
CEN_CSMREG_MSHOST=<hostname of message server>
CEN_CSMREG_PASSWORD=<Password of the user>
.
Both ADMIN_USERID and CSMREG_USERID must be valid R/3 users in the Central Monitoring System
with RFC privileges.
Option: Starting the SAPCCMSR agent

The agent does not start automatically on a UNIX platform.
You must start it manually and also ensure that the CCMS agent is started after a system restart.
cd /usr/sap/ccms/bin
chmod R 775 sapccmsr
The commands for the agent are:
Starting
UNIX
/usr/sap/ccms/bin/sapccmsr DCCMS pf=<profile_name>
<profile_name> is /usr/sap/tmp/sapccmsr/j2ee.pf
Explanations can be found below in Troubleshooting Shared Memory Segment of how to use
this profile.
Example
/usr/sap/ccms/bin/sapccmsr DCCMS pf=./usr/sap/tmp/sapccmsr/j2ee.pf
Stopping
/usr/sap/ccms/bin/sapccmsr stop
Status
/usr/sap/ccms/bin/sapccmsr status
MS Windows
On windows you start and stop the SAPCCMSR as a Windows service.
UNIX and MS Windows
On stopping the SAPCCMSR writes the shared memory content in the files
/usr/sap/tmp/A*
Troubleshooting SAPCCMSR
Checking the successful operation of the agent can be done by inspecting the log:
Check the log-file sapccmsr<pid>.log
Check whether your user id has the administrative rights to start a service on Windows
environment.
Troubleshooting Shared Memory Segment properties

SAPCCMSR creates a shared memory segment during startup, which needs to be accessible to the J2EE
Engine user <J2EEadm> or specifically the user who started the J2EE Engine. Otherwise the jmon can not
connect to the shared memory segment due to missing permissions.
2004 SAP AG
To avoid this connection problem you need to grant rwx permission to the SAP agent working
directory.
Then start the agent as user j2eeadm.
This issue will be resolved with version 6.x of the jmon.
Make sure that the users belong to one user group as there are possible concurrent creators of the
shared memory segment 0x4dc4 rsp. .99. The first creator becomes owner each creator which is
started later only connects to the segment and it is no longer possible to change the properties of the
segment. Therefore you need to make sure that the shared memory segment is created with the
necessary properties.
Necessary properties are:
- Hostname < 13 characters
(13 characters are a limitation of the CCMS - if your hostname is longer than 13 characters you
need to set a shorter one here)
- Segsize > 64 MB
- --rw-rw---- write permission to the group

Check the properties with command ipcs ma.
The shared memory segment with KEY= 0x4dc4 must have MODE = --rw-rw---- (important: write
authorization to group) and a SEGSZ = 64141728
If the properties of the shared memory segment differ from this, you have to stop the J2EE Engine and
every other agent which is attached to the segment NATTCH= <X>.
Be sure that everything is stopped and NATTCH=0
Delete the shared memory segment with /usr/sap/ccms/sapccmsr initshm
Create a new segment with the necessary properties by starting the SAPCCMSR with a profile that
contains the necessary startup profiles.
Unix
Create a file, for example j2ee.pf within the directory where your SAPCCMSR resides.
cd /usr/sap/tmp/sapccmsr/
touch ./J2ee.pf
edit this file
vi ./j2ee.pf
Add the following lines

SAPLOCALHOST=<short hostname> (Example: SAPLOCALHOST=portalhost1)
alert/MONI_SEGM_SIZE=64000000
ipc/shm_permission_1008=760
Definitions
2004 SAP AG
SAPLOCALHOST
The name of the contexts the data is written to (Hostname < 13 characters)
alert/MONI_SEGM_SIZE
size of the segment
ipc/shm_permission_1008
authorizations of the segment
Please find further information in SAP note 300464.
Save the entry and exit the file :wq
Usage during installation:
./sapccmsr R pf=/usr/sap/tmp/sapccmsr/j2ee.pf
Usage during normal startup
./sapccmsr DCCMS pf=/usr/sap/tmp/sapccmsr/j2ee.pf
Further information SAPOsCol

Installing SAPOsCol
The installation procedure of the SAPOsCol is as follows:
Look up the current version in the SAP Service Marketplace.
Find a new version of SAPOsCol for your platform in the SAP Service Marketplace, alias swcenter
SAP Support Packages & Patches SAP Web AS SAP Web AS <version> BinaryPatches
SAP Kernel <version><architecture> <Platform> Database Independent
Copy the new SAPOsCol version to /usr/sap/ccms/bin.

Assign the correct authorizations to SAPOsCol with:
chgrp sapsys saposcol
chmod 4755 saposcol
Make sure the binary is executable.

Since SAPOsCol runs with root authorization, users of group 'sapsys' (e.g. <j2eeadm>) should be
able to access it.
Start the SAPOsCol as root by entering

/usr/sap/ccms/bin/saposcol -l
Further information about installation of SAPOsCol can be found in SAP note 19227.
Process monitoring with SAPOsCol
SAPOsCol enables you to monitor selected processes on an operating system level, such as SVR1 and
DISP1. To monitor selected processes with SAPOsCol, you must specify information about the desired
processes or their owners in the configuration file dev_proc. This file must be in the SAPOsCol working
directory, /usr/sap/tmp/, where the file dev_coll resides.
More detailed information about process monitoring with SAPOsCol is available via the Service Marketplace
(http://service.sap.com/monitoring SAPOsCol operating system collector.) and in SAP notes 451166 /
566840.
Giving the java processes an identifier for SAPOsCol

It is helpful to assign distinct identifiers to the different java processes (as seen above #J2EE Server
*SVR1* *SRV2* etc.). Currently naming of the java processes is not possible, but there is a simple
workaround. It is possible to add a pseudo parameter e.g. D:SVR1 to the beginning of the class path call of
2004 SAP AG
the J2EE service nodes. The Java virtual machine does not recognize this parameter, but the syntax is
correct, so the virtual machine does not throw an exception, but ignores the parameter.
Unix with ps ef | grep java will show you this pseudo parameter.
The SAPOsCol will also report the performance data of the process into the CCMS with this pseudo name.
Tthere you can assign auto reaction methods to it (see below).
Due to different start up methods of the portal there are different files where this parameter has to be
maintained. The files for a standard start up with unixdeamon start are described here.
The parameter for the dispatcher is to be added to the
/usr/sap/<Portal>/j2ee/j2ee_01/configtool/service.ini
Service_0_MainClass=com.inqmy.boot.Start
ServiceCount=1
Service_0_RootDir=/usr/sap/EP0dir/j2ee/j2ee_01/cluster/dispatcher
Service_0_Timeout=10000
Service_0_JavaPath=/usr/j2se/
Service_0_Name=cluster/dispatcher
Service_0_ShutdownKey=125-36-125-107-75-1269225-287
Service_0_Port=5501
Service_0_Parameters=
Service_0_JavaParameters=-D:DSP -Dmemory.manager=64M -Xmx64M -Xms64M -classpa
th ".;.\system-lib\boot.jar;" -Djava.security.policy=.\java.policy -Dorg.omg.C
ORBA.ORBClass=com.inqmy.services.iiop.internal.ORB -Dorg.omg.CORBA.ORBSingleton
Class=com.inqmy.services.iiop.internal.ORB -Djavax.rmi.CORBA.PortableRemoteObje
ctClass=com.inqmy.system.PortableRemoteObjectProxy -Djavax.rmi.CORBA.UtilClass=
com.inqmy.system.UtilDelegateProxy
The parameter for the server started by the dispatcher is to be added
/usr/sap/<Portal>/j2ee/j2ee_01/cluster/server/cmdline.properties
#
#Wed Sep 10 22:53:34 CEST 2003
2004 SAP AG
Parameters=
MainClass=com.inqmy.boot.Start
JavaParameters=-server -D:SVR1 -Dmemory.manager\=1024M -Xmx1024M -classpath ".;.
\\system-lib\\boot.jar;.\\system-lib\\jaas.jar;" -Djava.security.policy\=.\\java
.policy -Dorg.omg.CORBA.ORBClass\=com.inqmy.system.ORBProxy -Dorg.omg.CORBA.ORBS
ingletonClass\=com.inqmy.services.iiop.internal.ORB -Djavax.rmi.CORBA.PortableRe
moteObjectClass\=com.inqmy.system.PortableRemoteObjectProxy -Djavax.rmi.CORBA.Ut
ilClass\=com.inqmy.system.UtilDelegateProxy -XX:NewSize\=256M -XX:PermSize\=128M
-XX:+DisableExplicitGC -Xms1024M
Configuration of SAPOsCol by editing dev_proc

The default path of the dev_proc is /usr/sap/tmp.
The file dev_proc has the following structure:
$PROC
#
# ProcessName User
#
#J2EE Server
*SRV1* j2eeadm
*SRV2* j2eeadm
2004 SAP AG
*DSP* j2eeadm
#TREX
*TREXDaemon.x* trexadm
*TREXFilter.x* * trexadm
*TREXIndexServer.x* * trexadm
*TREXPreprocessor.x* trexadm
*TREXQueueServer.x* trexadm
*TREXNameServer.x* trexadm
#Apache
*Httpd* trexadm
# Oracle
$
Please find a dev_proc in the appendix.
Filtering Processes and Rile Systems reported by

SAPOsCol due to Assignment of MTE Classes and
Attribute Groups
MTE classes and attribute groups are explained in the upcoming chapter Assigning Thresholds and
Autoreaction Methods to the Desired Node. However, this is the correct point to carry out preparations.
The server process of the portal cluster was named SRV0, SRV1, and SVR2. Thresholds and auto alerts
will be configured to this process and to the fill level of reported file systems. You have configured the
SAPOsCol with the file dev_proc (see above section SAPOsCol) to monitor the processes. Now due to the
assignment of auto reaction methods and thresholds to these processes it is recommended that MTE
classes and attribute groups be attached to the process names. This is carried out by the SAPCCMSR
agent with a configuration file oscolfile.ini and an entry in the sapccmsr.ini.
Structure oscolfile.ini
#MonitorProcess Process MTE_Class Attribute_Group
#J2EE-Prozesse
MonitorProcess *SVR0* ZSVR_P_CL ZSVR_P_GR
#Filesystems MTE_Class Attribute_Group
MonitorFilesystem /oracle/EP0/sapdata CL_FS_EP GR_FS_EP
An example oscofile.ini and sapccmsr.ini can be found in the appendix.
The section Assigning the Thresholds and Autoreaction Methods to the Desired Node describes how you
assign thresholds to the attribute group, for example ZSVR_P_GR and autoreaction methods to the MTE-
class, for example ZSVR_P_CL.
Starting and Stopping SAPOsCol

Always start SAPOsCol as a user with root rights:
/usr/sap/ccms/bin/saposcol l
Therefore you can only stop SAPOsCol with a user with root rights:
/usr/sap/ccms/bin/saposcol k
At stopping SAPOsCol writes its shared memory content to the file
2004 SAP AG
/usr/sap/tmp/dev.put
Troubleshooting
In case of problems start you can start with SAP Note # 48699.
Installing JMON
You need to perform the actions in this section for hosts on which a J2EE Engine is running.
If you have installed multiple J2EE Engines on one host, you must perform these steps for each J2EE
Engine. Monitoring data for the SAP J2EE Engine can be written to SAPCCMSRs shared memory using
JMON. JMON consists of a Java section and an operating system specific section. These two sections
must:
- Match each other
- Match the operating system (note that the bit version is not important here)
- Match the VM of the J2EE Engine with regard to the bit version
Checking the version of the jmonapi.jar

The easiest way to check the version of the jmonapi.jar is to open it with WinZip, browse to file Manifest.mf,
open this file and check the version. Currently the version is 1.7.2.
Configuring jmon
Switch to the directory moni_temp.
Copy the file jmonapi.jar to all of the locations in your SAP J2EE Engine 6.20 where the old version
currently exists.
UNIX
You can find these locations using for example the command
find /usr/sap name jmonapi.jar
Some Unix derivates / shell need the option print.

Copy the file libjmon.so to all of the locations where jmonapi.jar exists and also to the directory
<SAP J2EE engine home>\oslibs
MS Windows
Search in the <SAP J2EE engine home> for jmonapi.jar.
Copy the file jmon.dll to the system directory WINNT\system32.
UNIX/Windows
Standard directories for the jmonapi.jar are
<SAP J2EE engine home>\cluster\server<x>\additional-lib
<SAP J2EE engine home>\cluster\dispatcher<x>\additional-lib
<SAP J2EE engine home>\tools\lib
Troubleshooting
The jmonapi writes two trace files, which have to be checked in case of errors:
2004 SAP AG
../cluster/server/ccms_agent.trc
and
../cluster/server/ccms_jmon.trc
Monitoring the J2EE Engine

The SAP J2EE Engine monitoring system consists of a monitor server and monitor service. The monitor
service establishes a connection between the monitor server and the system. The monitor server works on
a separate virtual machine for releases from patch 10 onwards or on the same Java VM of the portal
process as a server node below patch 10. Due to conflicts with the class loader for the portal monitor it is
mandatory to run the monitor server in a separate VM.
The monitor server collects data from the J2EE Engine and reports the information and statistics about the
node and their components to the Visual Administrator, SAPs Computing Center Management System
(CCMS) agent, a file system (in .xls and .html format files) and its own monitor server GUI tool.
This document only handles reporting into CCMS. Should you want to use one of the other monitoring
techniques, refer to the administration guide of the J2EE Engine (Administration Manual Configuration
Tasks Using the Log System and Monitoring).
Configure and Start the Monitor Server

The following description shows you how to configure the monitor server in a separate Java VM. More
detailed information about the configuration is available via SAP note 498179.
The installation directory of the SAP J2EE Engine, for example
/usr/sap/EPORTAL/j2ee/j2ee_00/ is abbreviated by <J2EE INSTDIR>.
(MS Windows and Unix differences here are purely in the direction of the slashes).
Check monitorServer properties

Unix: <J2EE INSTDIR>/tools/monitorServer.properties
MS Windows: <J2EE INSTDIR>\tools\monitorServer.properties
The properties should look like this:
(please find explanations below the file text to help with editing)
# --------------Auto Execution----------------
# This will be automatically executed. If there are no autoexec #properties
# the 'connect' command should be typed manually on the Monitor Server #console.
shell.autoexec.0=help
shell.autoexec.1=connect
#-----------------Connection Parameters--------------------------------
# # Default values : localhost, Administrator , ""
#
java.naming.provider.url=10.15.201.117
java.naming.security.principal=PerformanceGuru
java.naming.security.credentials=LetsPerformBetter
#
#
#------------------Monitoring Reports Frequency------------------------
2004 SAP AG
# This sets the report interval in milliseconds. (Influences performance)

# With value of 5000 used has the feeling of real-time update of #information,
# but it is too short if the results will not be monitored real time but #post factum and will
# be monitored for hours. Good value for long monitoring could be 60000 #(1 min.) or even larger.
# Default value : 10000.
monitor.report.gap=30000
#-----------------Visual Administrator Reporter-----------------------

monitor.system.VA.mode=on
monitor.system.VA.port=5555
#-----------------File System Reporter---------------------------------

monitor.system.FS.mode=off
monitor.system.FS.fileFormat=html
monitor.system.FS.filesize=64
# Full path or just name of folder. If only the name of folder is selected this folder will
# be created in the same folder where monitor.bat is located.
monitor.system.FS.path=monitoring_html
#------------- CCMS Reporter ------------------------------------

monitor.system.CCMS.mode=on
monitor.system.CCMS.root=SAP_J2EE_Engine620
Explanations
java.naming.provider.url = your hostname:<p4 port>
If you run multiple installations of the SAP J2EE Engine on the same machine, you must set up
a monitor server for each installation. To avoid conflicts, add the following 2 lines to the
beginning of the configuration file properties. Replace <p4port> with the port you use to
connect via the administrator
(you can easily check the default p4 port in the file <J2EE_INSTDIR>/prepconf.log)
java.naming.security.principal = your administrator <name>
Do not confuse the <j2eeadm> with the administrator. The administrator is therefore created
with an empty password by default; you should also ensure that you remove the comment
symbols in the appropriate lines:
monitor.system.VA.port = <vaport>
Replace <vaport> with any free port (by default the port is 5555).
monitor.system.CCMS.root = <monitor_context>
2004 SAP AG
<monitor-context> is extremely important if you want to connect more than one installations
of the SAP J2EE Engine to the same CCMS. It must be system-wide unique. For this purpose,
change the default value (SAP J2EE Engine) to some unique identifier that includes, for
example, the host name.
Save and exit these text file properties.
Test the J2EE Engine Monitor Server

Test the monitor server before integrating it into a portal J2EE node.
Starting the monitor server:
MS Windows
<J2EE INSTDIR>\tools\monitor.bat
UNIX
<J2EE INSTDIR>\tools\monitor
The monitor server tries to connect to all nodes of the entire cluster, which are shown within stdout. If you
have activated CCMS monitoring via the appropriate parameters you can see a shell similar to the following:
Once the nodes are connected to the monitor server you can check the monitoring data from within the
visual administrator (monitor service) or if you call GUI from within the prompt of the monitor servers.
Now, you can see an additional java process on operating system level.
Check the monitor data in the visual administrator.
Once the monitor server and the SAP J2EE Engine are running, you should be able to see the monitor data
in the visual administrator.
Launch the Visual Administrator:
UNIX
<J2EE INSTDIR>/admin/go
MS Windows
<J2EE INSTDIR>/admin/go.bat.
Connect to your Standalone installation.

In the tree on the left hand side, select the monitor service of a server node.
The tab Runtime on the right-hand side shows all monitor servers after a double click on monitor servers.
2004 SAP AG
Browse the tree to inspect the monitoring data.
Figure 5:
The monitoring data for the SAP J2EE Engine is transferred to the SAPCCMSR agent using the monitoring
server, and can therefore be displayed in CEN. You can view the data in the alert monitor in the sub tree
SAP_CCMS_<Hostname> SAP J2EE Engine in the Monitor System / All Monitoring Segments / All
Monitoring Contexts of the monitor set SAP CCMS Technical Expert Monitors.
Mmore informationcan be found in the following chapters: Defining a CCMS Monitor for the J2EE Engine,
SAP J2EE Version monitoring, SAP J2EE Service Status Monitoring, SAP J2EE Workload Monitoring.
Troubleshooting
If you cannot see the sub tree, check whether the process SAPCCMSR is actually running (under UNIX, for
example, with the command ps ep | grep sapccmsr).
If the agent is not running:
Enter the command sapccmsr initshm
Restart the agent.
Errors in the J2EE monitor server are written to a log at
<J2EE_INSTDIR>/cluster/<server>/services/log/work.
Setting Up Log File Alerting and Monitoring

In the case of a Java application, the process of log file monitoring, in detail, is as follows: A Java application
writes a log file using the SAP Logging API. The SAP J2EE Engine therefore knows the file with its full path.
The SAP J2EE Engine creates an INI file for the SAPCCMSR agent for each log file to be monitored. This
INI file contains both the path and the name of the file, and details about monitoring the log file. The agent
automatically reads the INI files and monitors the corresponding log files from that point on. If an error
occurs, an alert is triggered in the central monitoring system.
The administrator can analyze the relevant log in more detail using the Standalone Log Viewer.
2004 SAP AG
The following configuration work is required for log file monitoring:

Configuring the J2EE monitoring server
Starting the J2EE Engine and the J2EE monitoring server
Generating the INI files for the automatic monitoring of the log files of the J2EE Engine
Registering the INI files in the SAPCCMSR agent
Generating the INI files for the automatic monitoring of the log files of J2EE applications
Adjusting the monitors in the central monitoring system
Installing and configuring the Standalone Log Viewer
Configuring the J2EE Monitoring Server

If you have not already done so, edit the file monitorServer.properties in accordance with section Configure
and Start the Monitor Server
Starting the J2EE Engine and the J2EE Monitoring Server

If the J2EE Engine is not yet running, start the J2EE Engine and the J2EE monitoring server as described in
Configure and Start the Monitor Server
Generating the INI Files for Automatic Monitoring of the J2EE Engine Log Files
The J2EE monitoring server generates the control files that are required to monitor the J2EE Engine logs.
After starting the monitoring server:
Create the log file templates by making the following entry in its console:
Microsoft Windows
generateLT <J2EE INSTDIR> <drive>:\usr\sap\prfclog\logmon
UNIX
generateLT <J2EE INSTDIR> /usr/sap/tmp/logmon
No confirmation message is displayed. The following folders are created in the directory \logmon:
ALERT
CRITICAL
DEBUG
...
Registering the INI Files in the SAPCCMSR Agent

There is now a file log-templates.summary in every subdirectory of the logon directory.
Copy the content of the summary files and insert it into file sapccmsr.ini under the comment line.
IF you have already register the SAPCCMSR agent, this file is stored by default in:
UNIX:
/usr/sap/tmp/sapccmsr/sapccmsr.ini
MS Windows:
<drive>:\usr\sap\prfclog\sapccmsr\sapccmsr.ini
### Format of entries for log file monitoring:
2004 SAP AG
LogFile C:\SAP_J2EE6.20\monitor_templates\ALERT\a-21-log.ini
An example sapccmsr.ini can be found in the appendix.
The INI files point to the actual paths of the J2EE Engine log files, such as
C:\SAP_J2EE6.20\alone\managers\log.
Under UNIX, you can automate this registration by entering the following single command
(note the sign double greater than [>>]):
grep LogFile /usr/sap/tmp/logmon/ALERT/log_templates.summary >>
grep LogFile /usr/sap/tmp/logmon/ERROR/log_templates.summary >>

grep LogFile /usr/sap/tmp/logmon/CRITICAL/log_templates.summary >>

grep LogFile /usr/sap/tmp/logmon/WARNING/log_templates.summary >>

...
Generating the INI Files for Automatic Monitoring of the Log Files of J2EE
Applications
Not to be confused with the J2EE Engine log files.

Start the visual administrator by entering:
UNIX
<J2EE INSTDIR>/admin/go
MS Windows
<J2EE INSTDIR>\admin\go.bat.
In the visual administrator, start the Log Viewer Service (Cluster Server Services Log
Viewer).
Make the following entries in the Properties:
Logviewer_FlagForGeneratingCCMSTemplate = 1
UNIX:
Logviewer_output_directory = /usr/sap/tmp/logmon
MS Windows:
2004 SAP AG
Logviewer_output_directory = <drive>:\usr\sap\prfclog\logmon
Figure 6: tab page Properties in the Log Viewer service of the visual administrator
Save your entries and restart the Log Viewer service.
The INI files are automatically created in directory logmon.
UNIX:
Stop and restart the agent manually:
/usr/sap/ccms/bin/sapccmsr stop
/usr/sap/ccms/bin/sapccmsr DCCMS
MS Windows:
Restart the agents service SAPCCMSR.99 under Start Settings Control Panel
Administrative Tools Services.
The SAPCCMSR automatically loads the *ini files in the described directory ../logmon for
reporting them into the CCMS.
2004 SAP AG
Integrate the Monitoring Server into a Cluster Node for Automated Start up
After you generate the *ini files you should configure the J2EE monitor server for automatic start up.
Copy the file <J2EE INSTDIR>/tools/monitorServer.properties to the directory <J2EE

INSTDIR>/cluster/server
Add the following two lines to the file

<J2EE_INSTDIR>/cluster/server/services/shell/work/autorun.scr
add monitor
startmonitorserverX
Restart the J2EE Engine of the portal.

Unix
<J2EE INSTDIR>/configtools/unixdaemon stop
<J2EE INSTDIR>/configtools/unixdaemon start
Windows
Restart the J2EE service of your portal.
Setting Up Log File Alerts for Non-Java Components

TREX
MS Windows
Copy the file TREX-Logfiles_Logmon.ini

from directory moni_temp to <drive>:\usr\sap\prfclog\logmon.
UNIX
Copy the file TREX-Logfiles_Logmon.ini

from directory moni_temp to /usr/sap/tmp/logmon.
Check the file paths contained in the file; these are specified in the DIRECTORY parameters.
Adjust them to your environment, depending on the location of the TREX installation directory.
DB Oracle
MS Windows
Copy the file Ora_Win-Logfile_Logmon.ini

UNIX
Copy the file Ora_Unix-Logfile_Logmon.ini

from directory moni_temp to /usr/sap/tmp/logmon.
Check the file path specified in the DIRECTORY parameter, and adjust it, depending on the location
of the Oracle installation directory in your environment.
Adjust the file name specified in the FILENAME parameter to your environment, by replacing <SID>
with the ID of the database system.
MSSQL
Copy the file MSSQL-Logfile_Logmon.ini
2004 SAP AG
Check the file path specified in the parameter DIRECTORY, and adjust it, depending on the location
of the MS SQL installation directory in your environment.
Checking Log File Monitoring in the Central Monitoring System

Start transaction RZ20 in the central monitoring system, by entering /nrz20 in the command field.
Open the Logfile Monitoring monitor in your monitor set by double clicking it.
You should see all log files that are monitored by SAPCCMSR. You can see the search patterns found by
the agent in the Open Alerts view, if you expand the corresponding sub trees for the individual log files.
You can also display the content of the monitored log files to obtain an overview.
To do this:
Place the cursor on the relevant Complete Name node and choose Start Analysis Method.
SAPCCMSR transfers the content of the log to the central system.
Installing and Configuring the Standalone Log Viewer

6.30
Host I Host II
J2EE J2EE
6.30 6.30
Log Viewer Log Viewer

Server Server
Log Viewer protocol (P4)

WTServer
(for example,
together with SAProuter
Solution Manager)
Log Viewer
Client SAP Support
Figure 7: System Landscape with Standalone Log Viewer

You must install the Standalone Log Viewer on the client side and on the server side. The Log Viewer
server must run on each monitored host, while the Log Viewer client should be installed on the central
monitoring system.
For documentation for the Log Viewer, see

http://help.sap.com/sapdocu/netweaver/webas/630/helpdata/EN/3f/10f39af50a95428130732ef1
47735a/frameset.htm
For the installation, you require the files in directory logviewer-standalone. This directory is in directory
moni_temp.
For the Log Viewer server, copy the folder logviewer-standalone to the <J2EE INSTDIR>/tools
folder.
For the Log Viewer client, copy the folder logviewer-standalone to any folder.
Adjusting the List of Log Files to Be Monitored

You must inform the Standalone Log Viewer which log file it is to monitor. You can do this by specifying the
complete path of the log files to be monitored at the start of the Log Viewer server.
2004 SAP AG
There is a template for this file with the name logdirectory.xml in folder moni_temp. Adjust the file paths
appropriately. If you want to view additional files centrally, extend the list as required. Each line of the file
specified a log file with its path, file name and its format, and has the structure:
<log pattern="<complete file name>" formattype="ASCIIFormat|ListFormat" />
Save the file in directory server, which is in directory logviewer-standalone that you just created for
the installation of the Log Viewer server.
You now have created a list that is modified for your circumstances, and which contains all files that the
Standalone Log Viewer is to monitor.
Adjusting the LogViewerServer.properties File

In the above folder <J2EE INSTDIR>/tools/logviewer-standalone/server there is a file
LogViewerServer.properties in which you can make settings to restrict the accessible paths. If no restrictions
are made, all files on the monitored host can be displayed using a Log Viewer client. The file also contains
the name and path of the file logdirectory.xml, so that the Log Viewer knows the log files which are to be
monitored. To carry this out, follow the procedure below:
Modify the file LogViewerServer.properties by specifying the name and path of the file
logdirectory.xml in the following line:
Logviewer_LocationForLogDirectory=<file path and name>
Save the LogViewerServer.properties file.
Starting the Log Viewer Server

In directory <J2EE INSTDIR>/tools/logviewer_standalone standalone-logviewer are the files server.bat
(Microsoft Windows) or server.sh (UNIX - make sure there are executable rights on the file).
Start the appropriate script for your operating system.
Starting the Log Viewer Client

The Log Viewer client is started on the central system. In directory standalone-logviewer are the files
client.bat (Microsoft Windows) or client.sh (UNIX).
Start the appropriate script for your operating system.
In the Log Viewer client, you can specify the name, host name, and port of the host on which the Log Viewer
server is to run by choosing File Configuration.
Ensure that the entry Standalone is active for the Connection input field.
You can obtain the port for the Log Viewer server from the file LogViewerServer.properties. The
default port is 1099.
Test Connection checks whether a connection can be made.
Optional: Displaying Other Log Files Non-continuously
To display other log files in the Standalone Log Viewer,
Choose File Add a file from the Log Viewer menu.
The relevant file is displayed until the next restart of the Log Viewer.
Further Information Log File Monitoring

Please find example *ini files in the appendix.
2004 SAP AG
General Settings for the Monitored Log Files

The following parameters of the log file template apply to all log files that fulfill the conditions for
DIRECTORY and FILENAME:
- LOGFILE_TEMPLATE
Key word for the agent; opens a search area
- DIRECTORY="<directory>" (required parameter)
Directory that contains the log file
- FILENAME="<file name>" (required parameter)
Name of the log file. Wildcards are permissible
- MONITOR_CONTEXT="<Context_name>"
Name of the monitoring context to which the log file agent writes the results of the monitoring. By
default this is the context Files_of_<Hostname>. Regardless of whether or not you set this
parameter, the MTE class of the monitoring context is always CcmsFileMonitoring. By specifying
this MTE class, you can define a rule-based monitor that contains the sub trees for all monitored log
files. In this way for example you can store different components in different contexts to further
group the results. Like the PREFIX parameter (see below), this function allows you to differentiate
between the different monitored log files, but provides, unlike PREFIX, an additional hierarchical
level to group the monitored files. Use this parameter only if you require this additional hierarchical
level.
- MONITOR_NEWEST_FILES=<number> (Default = 20)
Maximum number of files that are to be monitored; if the number of files whose names fulfill the
search criteria exceeds this number, exactly <number> files with the newest change time are
monitored. This means that different files are monitored over time. If a file is removed from
monitoring because other files have a newer change date, its monitoring tree is deleted, and its
alerts are reset. The maximum value for number is also 20, to avoid storing an unnecessarily large
quantity of data in the monitoring architecture.
Check this parameter for error and output log in

<J2EE_INSTDIR>/cluster/server/managers/console_logs/ as each restart of the J2EE Engine
creates a new log.
- IGNORE_CASE=[0,1] (default = 0)
By default, all search patterns are case sensitive (0). If upper and lower case are to be disregarded
during the search, set IGNORE_CASE=1.
- RESCANFROMBEGIN=[0,1] (default = 0)
Specifies whether each new read operation reads the log file from the start (1) or only the lines that
have been added since the log file agent last read the file (0).
- MONITOR_FILESIZE_KB=<file size[KB]> (Default: file size is not created)
o Value < 0: file size is not created.
o Value = 0: size of the log file in KB is monitored in the node FileSize.
o Value > 0: The size of the log file in KB is monitored; if the file size exceeds the value, an
alert is generated.
- PREFIX="<character string>"
Appears before the MTE nodes. Allows you to differentiate between different log files with different
paths but the same name (the maximum length of the prefix is 8 characters).
- SHOWNEWLINES=[0,1] (Default = 0)
o Value=1: The Alert Monitor creates the sub node Newlines
(the number of lines created per minute is reported)
o Value=0: Newlines is not created
2004 SAP AG
- ANALYZEMETHOD="<method name>" (Default: no method)

Analysis method that is assigned to the alert (the maximum length of the name is 40 characters).
- MONITOR_LAST_FILE_MODIF=[0,1] (Default = 0)
Specifies whether a separate performance node File Time Stamp is to be created, which then
monitors the last change time point of the log files (1), or whether the last change time point is not to
be monitored (0)
- MTE_CLASS="<MTE class>" (Default: CcmsFile<file name>)
MTE class of the monitoring object that contains the attributes specified above; the MTE class of the
monitoring objects therefore depends on the name of the monitored log file.
- CHECK_EXISTENCE_ONLY=[0,1] (Default = 0)
Specifies whether the system is to check only for the existence of the log files (1). In this case, all
parameters for monitoring and for search patterns (see below) are ignored.
For more information refer to SAP Service Marketplace alias systemmanagement System Monitoring and
Alert Management Media Library Documentation in documentt CCMS Agents: Features, Installations,
and Usage.
Templates for configuration files (as a general

approach):
Example
Configuration File Name File Content
LOGFILE_TEMPLATE
/usr/sap/ccms/ccms_monitoring/templates/log
DIRECTORY="c:\SAP\TREX_6\trace"
monitor/trex_all_log.ini
FILENAME="TREX*"
MTE_CLASS="EP TREX Log"
PREFIX="TREX - "
SHOWNEWLINES=1
ANALYZEMETHOD=""
MONITOR_LAST_FILE_MODIF=1
SHOWLINES=1
PATTERN_0=" e "
VALUE_0=RED
Unless otherwise stated, the search patterns FATAL and ERROR are used for all Java based log files, and
trigger a red alert in the CCMS.
Further information EP Logging

Portal Infrastructure
Logging is performed with the standard logging API through a portal runtime wrapper for the portal
applications.
Log file destination:
<SAP_J2EEngine>/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/
Content Management
Logging is performed with the standard logging API (not with the portal runtime wrapper) through the portal
application: com.sap.netweaver.bc.util.
<SAP_J2EEngine>/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-
INF/portal/logs/knowledgemanagement.%g.log
Configuration:
No UI. Properties file is read every second to get changes; The properties file is
<portalapplication>lib/logging.properties.
Collaboration
2004 SAP AG
Use of CM logging (UI should be delivered with a hotfix)

SP1: Collaboration_logger deployed to the portal infrastructure logging environment, but only partially used.
Will be removed in SP2
<SAP_J2EEngine>/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs
/collaboration.log
UserManagement
Use the portal infrastructure logging (loggers are defined there).
Auditing: file = <SAP_J2EEngine>\cluster\server\sapum.log, written with LoggingAPI.
Monitoring in the CCMS is OK, but not with the common roles errors and fatal errors may not
be marked as red.
Non-Java
LDAP Server
SUN/IPlanet:
Log files: ...\iPlanet\Servers\slapd-<servername>\logs
Filename: error
There are also files named audit and access.
Novell:
Log files: ...only on the fly; it is not known where this data is stored.
ADS:
Log file: Microsoft Windows Eventlog
Siemens DirX:
Log file: ...\Siemens\DirX\Server\Audit\audit.log (unfortunately binary)
TREX
c:\SAP\TREX_6\trace\TrexQueueServer.*
c:\SAP\TREX_6\trace\TrexIndexServer.*
c:\SAP\TREX_6\trace\TrexNameServer.*
c:\SAP\TREX_6\trace\TrexPreprocessorServer.*
c:\SAP\TREX_6\trace\TrexFilter.*
c:\SAP\TREX_6\trace\TREX_HTTP_SERVER_Trace.txt*
c:\SAP\TREX_6\trace\TREX_HTTP_SERVER_Log.txt
The associated log file template TREX-Logfiles_logmon.ini or TREX-Logfiles_logmon.ini is in

directory moni_temp.
Database
Oracle
The associated log file template Ora_Unix-Logfile_logmon.ini or Ora_Win-Logfile_logmon.ini is in
directory moni_temp.
2004 SAP AG
MSSQL
The associated log file template MSSQL-Logfile_logmon.ini is in folder moni_temp.
Further Information Log Viewer

The Log Viewer is able to display 3 different log types: SAPJLog, SATLog, and ASCIILog.
You can register each log from the possible types to the Log Viewer server during runtime by calling from
Log Viewer home.
UNIX
<J2EE INSTDIR>/tools/logviewer_server/register_log.sh register_log <hostname> <port> <logfile name>
<logfile_type>
MS Windows
<J2EE INSTDIR>\tools\logviewer_server\register_log.bat register_log <hostname> <port> <logfile name>
<logfile_type>
<hostname> = localhost
<port> = as that maintained in the parameter Logviewer_socketPort=5465 in
<J2EEINSTDIR>\tools\logviewer_server\LogViewerServer.properties
<logfile name> = log name with complete path
<logfile_type> = SAPJLog or SATLog or ASCIILog
Troubleshooting the Log Viewer

Problem description Problem diagnostics Solution
Standalone Log Viewer server Java is not installed on the server Check with java version if
does not start. node. Java is installed.
Download and install Java 1.3.1.
or higher.
Set environment variables
JAVA_HOME and PATH.
JAVA_HOME or PATH is not set Set these variables as described
above.
RMI port is already occupied by a If the port (default: 4444) is
running Log Viewer server or occupied by another service, edit
another service. the server properties file and
choose an unoccupied port.
Registration of files with script Unsupported file format is given. Choose one of the file formats:
register_log.bat fails ASCIILog, SAPJLog or SATLog.
Wrong port number is entered. Look up the RMI port number in
logviewerServer.properties
(default is:1099)
Wrong file path is entered. Find the correct file path.
Registration of ASCII files in file File path is entered only with \. Use \\ to describe the file paths.
Log Viewer properties fails
Log Viewer client does not start Java is not installed on the server Check with java version if
node. Java is installed.
Download and install java 1.3.1 or
higher.
Set environment variables
JAVA_HOME and PATH.
2004 SAP AG
JAVA_HOME or PATH is not set. Set these variables as described

above.
Connection to the server can not Server is not running. Start the Log Viewer server on
be established this particular node.
Wrong server type is entered. If a standalone server should be
connected the server type must
be standalone.
Wrong port number is entered. Check the RMI port number in the
properties file of the specific
server node.
Availability Monitoring
Availability monitoring of the J2EE Engine
Is done by the J2EEngineMonitorServer as described in the chapters Monitoring the J2EE Engine and SAP
J2EE Service Status Monitoring.
GRMG Check of the Portal

For the portal availability check using GRMG, the central monitoring system periodically calls a portal URL.
The underlying GRMG application checks the portal and reports check results to the central monitoring
system. This availability check is activated in the following steps:
- Adjusting the GRMG Customizing files
- Uploading the GRMG Customizing file to the central monitoring system
- Activating the GRMG check in the central monitoring system
- Checking the mechanism in the delivered CCMS monitor
Different setup steps are required, depending on whether the GRMG check is to be performed using HTTP
or HTTPS. The steps of the setup of GRMG with HTTPS will be described in an upcoming version of this
Best Practice Document.
Activating the GRMG Check Based on HTTP

Load the GRMG Customizing file grmgRequesthttp_template.xml from directory moni_temp in an
editor.
<scendesc> GRMG_HTTP_EP6
the description of the scenario is shown as in the CCMS.
<scenstarturl>http://...
replace the placeholders for:
<host> Host name of the portal start address

<http-Port>: HTTP port of the J2EE Server (default 50000)
<user>: Portal user from the Super_Admin group
<pass>: Password of the above portal user
<compname>TestSAP</compname>
edit the property values according to the logon data for your backend system.
<propname>SAPClient</propname>
<propvalue>...
<propname>userid</propname>
<propvalue>...
2004 SAP AG
propname>password</propname>
<propvalue>...
<propname>host_name</propname>
<propvalue>...
<propname>system_number</propname>
<propvalue>...
<compdesc>Component_TestWeb
line http://localhost:50000/irj/...
Enter a URL of your portal you want to be checked regularly
Save the file on your front end.
Setup Importing GRMG Config File into the CCMS

system.
In CEN start transaction GRMG by entering /ngrmg in the command field.
Choose the Upload button and import the changed customizing file.
(Please know that you get no error if the xml file is not well formed, but the scenario will not work).
Figure 7:
(this screenshot is from a Web AS 6.20 without the transport as described in the chapter Importing a
Transport Request into the Central Monitoring System/Solution Manager)
2004 SAP AG
Figure 8:
(this screenshot is from a Web AS 6.20 with the transport as described in the chapter Importing a
Transport Request into the Central Monitoring System/Solution Manager)
In the table, select the scenario that you have just uploaded and choose Start sel.
You have now successfully activated the GRMG check for EP.
Start transaction RZ20 by entering /nrz20 in the command field, and open the Availability
Monitoring monitor in your monitor set <my monitor set>.
A few minutes later the GRMG results will be displayed in sub tree Availability checked by GRMG (JAVA)
HTTPS GRMG_https_EP6. If the EP as a whole becomes unavailable, the monitor displays
corresponding error messages in sub tree MoniInfra_... RunStatus/Error Messages.
Call transaction RZ20 and choose SAP CCMS Technical Expert Monitor.
Double click All Monitoring Context.
Here open the MoniInfra_<ccms-hostname>_<SID>_<SysNr> of your CCMS system.
Figure 9:
Here you find an entry showing if the GRMG monitoring works.
2004 SAP AG
Browse the tree All Monitoring Context for your scenario description as given in the GRMG
configuration file described above.
Example <scendesc>EP_Heartbeat_n1</scendesc>
Figure 10:
Further Information: GRMG Check of the Portal
For detailed information about additional GRMG EP checks, see the EP documentation.
GRMG tests using HTTP may transfer user and password information across the network in plain text. You
can avoid this by using SSL/HTTPS.
In the future, the GRMG check will also include availability tests for LDAP and the database.
There are 4 scenarios currently delivered for GRMG Heartbeat Monitoring of the Portal:
- The first scenario describes the availability check of the Portal.
- The second scenario describes the availability test for the SAP J2EE cluster nodes.
There is no adjustment necessary.
- The third scenario describes the availability test of connected SAP Systems with a Web AS or an
R/3 basis. Configure the connection data accordingly to your jCodestination.xml. The GRMG test
will check if the SAP system is available for the portal.
- The fourth scenario describes availability test for URL.
You can check the availability of a specific URL.
- <propvalue> URL to
http://<server>:<http_port>/irj/portalapps/com.sap.portal.heartbeats/html/heartbeat.html</propvalue>.
This can be the server and port of your portal installation or of your load balancer.
Save your work and give the grmgRequestCust.xml a distinguished name for example
grmg<servername>.xml.
Troubleshooting
You can simply check if the xml file is well formed by opening it with an IE. The IE will give you an indication
of whether the xml file is well formed or not.
If the EP GRMG as a whole becomes unavailable, the monitor displays the corresponding error messages
in sub tree MoniInfra_... RunStatus/Error Messages.
2004 SAP AG
TREX Heartbeat with GRMG (Generic Request and

Message Generator)
With TREX 6.0 SP1 the availability of TREX services can be checked using a GRMG heartbeat. The R/3
system (CCMS) uses an HTTP request to send a GRMG-defined XML to one of the TREX GRMG servers
running on the TREX host. The TREX GRMG server then analyzes the XML and starts the relevant scenario
test in order to check the availability of the individual TREX servers on the chosen TREX host.
The following TREX servers (services) can be checked on a physical machine in a TREX installation:
Index server
Queue server
Preprocessor
Name server
Web server
Set Up TREX Heartbeat Monitoring with GRMG on

TREX-Side
UNIX only
To start the TREX GRMG server, execute the script TREXSettings.sh as the TREX administrator (it
is in directory <TREX home directory>/TREX_6), by entering the following command:
. TREXSettings.sh
(or, written out, <period> <SPACE> TREXSettings.sh)
If you have problems during this step, switch to the bash shell for the execution of the step by executing the
bash command.
Unix and MS Windows
Copy the TREX GRMG server files.
Copy the following TREX GRMG server files from directory moni_temp to directory:
<TREX_home_directory>/TREX_6/python_support/test_tools/lib:
TREXgrmg.py
TREXgrmgconf.py
TREXgrmgparse.py
TREXgrmgsrvcheck.py
installed.xml
grmgconfig.xml
If the TREX GRMG server files already exist make sure that you use the latest version.
Unix
Make sure that the owner is TREX administator for all files in <TREX_6 installation
dir>/python_support/test_tools/lib. Make also sure that all files have execution
authorization for the group.
For example trexadm:sapsys.
As root:
cd <TREX_6 installation dir>/python_support/test_tools/lib

chown <trexadm>:sapsys *
chmod 775 *
2004 SAP AG
MS Windows
Make installed.xml writeable (remove the read only flag) and open it with an appropriate editor
(not MS Notepad).
Replace <hostname> with your host name. There is no fully qualified host name necessary. Please
be aware that if your CCMS is on a Web AS 6.20 the TREX host needs an entry in the DNS.
(A ping on the host must return a fully qualified host name).
<?xml version="1.0" encoding="UTF-8"?>
<components>
<component name="IS_01" installed="X">
<property name="HOST" value="hostname"/>
<property name="PORT" value="8351"/>
</component>
<component name="QS_01" installed="X">
</component>
<component name="PP_01" installed="X">
</component>
<component name="NS_01" installed=" ">
</component>
<component name="WS_01" installed="X">
<property name="URL" value="http://hostname:8353/trexhttpserver/trexhttpserver.dll"/>
</component>
</components>
Please find an example installed.xml in the appendix.
IS_01 = TREX index server

QS_01 = TREX queue server
PP_01 = TREX Preprocessor
NS_01 = TREX name server
WS_01 = TREX Web server
Replace the URL:
If TREX is running on W2K IIS,
http://<hostname>:8353/trexhttpserver/trexhttpserver.dll?CMD=PING
If TREX is running on UNIX Apache, change the URL to

http://<hostname>:8353/TREX?CMD=PING.
2004 SAP AG
Modify the port:

If you have not changed the standard installation, you do not need to modify the port. If you started the
servers on other ports, enter the port numbers as appropriate.
Specify which servers are to be checked:
If installed has the value X, the server in question is to be checked. The name server is not active by
default, so it should also not be checked. This is why the entry for the name server has a blank character in
place of the X. This causes CCMS to register OK and to produce the entry not installed.
<component name="NS_01" installed=" ">
Start the TREX GRMG server:

UNIX
As <trexadm> with a bash shell:
cd <TREX_6 install-dir>\
. TREXSettings.sh
cd <TREX_6 install-dir>\python_support\test_tools\lib
python TREXgrmg.py 8366
You will get a response:
starting on port:
8366
Now you can run the process in the background to be able to use or leave the terminal:
cntrl + z
bg
To stop the server:
fg (to bring it in the foreground)

cntrl + d to stop python
MS Windows
Open a cmd-prompt from directory <TREX_6 install-dir>\python_support\test_tools\lib.
Call the command:
Python TREXgrmg.py [port number]
By default, the TREX GRMG server runs on port 8366.

Stop is : CTRL + Pause
A response like this should appear similar on UNIX as on MS Windows:
2004 SAP AG
Set Up TREX Heartbeat Monitoring with GRMG on the

CEN Side
Load the GRMG customizing file trex_grmgconfig.xml from directory moni_temp in an editor.
Define the GRMG scenario name.
This has to be unique in the CCMS system. Recommendation: sequential numbering in the form
TREXnnnn.
For example <scenname>TREX001</scenname>
Specify the URL of the TREX GRMG server.

This has to end in a forward slash (/).
For example <scenstarturl>http://p70569:8366/</scenstarturl>
Choose a meaningful description for the scenario.

Recommendation: Replace the xyz with your host name.
For example <scendesc>TREX on host p70569 </scendesc>
<scendesc>TREX on host xyz </scendesc>

<customizing>
<control>
<grmgruns>X</grmgruns>
<runlog>X</runlog>
<errorlog>X</errorlog>
</control>
<scenarios>
<scenario>
2004 SAP AG
<scenname>TREX001</scenname>
<scenversion>001</scenversion>
<sceninst>01</sceninst>
<scentype>URL </scentype>
<scenstarturl>http://host:8366/</scenstarturl>
<scenstartmod>Unknown</scenstartmod>
<scentexts>
<scentext>
<scenlangu>EN</scenlangu>
<scendesc>TREX on host xyz </scendesc>
</scentext>
</scentexts>
Save your changes.

Save the file on the front end.
In CEN, start transaction GRMG by entering /ngrmg in the command field.
Choose Upload and import the modified customizing file.
In the table, select the scenario that you have just uploaded, and choose Start sel.
You have now successfully activated the GRMG check for TREX.
Start transaction RZ20 by entering /nrz20 in the command field and open the Availability
Monitoring monitor in your monitor set <my monitor set>.
After a few minutes, the GRMG results appear in sub tree Availability checked by GRMG (JAVA) TREX
TREX on Host.
Further Information on TREX GRMG Availability Check

The GRMG check of TREX is described in detail in SAP Note 637124.
Check the monitor if you do not have imported the transport as described in Importing a Transport
Request into the Central Monitoring System / Solution Manager.
Call up transaction RZ20.
Expand SAP CCMS Technical Expert Monitors.
Choose All Monitoring Contexts.
Find the text description: <scendesc>TREX on host xyz </scendesc> and expand the
segment.
2004 SAP AG
Add the new monitor to your monitoring set as described in chapter Set up CCMS in a central
monitoring landscape.
Start the TREX HTTP GRMG Server on UNIX as a

Daemon
UNIX
Add the following entry to your <your_TREX_install_directory /TREXDaemon.ini:
[daemon]
programs=indexserver, queueserver, preprocessor, isapiregister, grmg
Create the following section and replace <.>:

[grmg]
executable=<you_python_install_dir>/python
arguments="<your_TREX_install_directory>/python_support/test_tools/lib/TR
EXgrmg.py"
startdir=<your_TREX_install_directory>/python_support/test_tools/lib
instances=1
MS Windows
Add the following entry to the <your_TREX_install_directory \TREXDaemon.ini file:
[daemon]
programs=indexserver, queueserver, preprocessor, isapiregister, grmg
Create the following section and replace <.>:
2004 SAP AG
[grmg]
executable=<you_python_install_dir>\python.exe
arguments=<your_TREX_install_directory>\python_support\test_tools\lib\TR
EXgrmg.py
startdir=<your_TREX_install_directory>\python_support\test_tools\lib
instances=1
If you want the TREX GRMG server to be started on another port, for example 8777, enter the
following:
arguments="<your_TREX_directory>\python_support\test_tools\lib\
TREXgrmg.py" 8777
Save the file and restart the TREX daemon.
Troubleshooting
If the EP as a whole becomes unavailable, the system displays corresponding error messages in sub tree
MoniInfra_... RunStatus/Error Messages.
UNIX
If the TREX Apache web server did not react properly please check with:
netstat a | grep 8353 if the port is not blocked
If the TREX Apache web server did not react on restart of the TREX shut down the Apache manually as
<trexadm>:
apachectl stop
and start the web server again with:
apachectl start
only apachecntl will bring you the options
GRMG Check of the Portal based on HTTPS

This section describes only the enabling of https without using a certification authority. If you are using a
certification authority please continue as described in Further information about SSL
If you want to use GRMG availability monitoring based on HTTPS, the HTTPS connections for the SAP
J2EE Engine and the central monitoring system CEN must already be set up
This HTTPS connection use the secure socket layer (SSL). There are 4 main steps for enabling SSL
communication between the Portal and a Web AS
Installing the sapcryptolib into the Web AS (CEN)
Create PSE and configure the ICM (internet connection manager) for HTTPS
Installing the cryptographic Library into the J2EE Engine of the Portal
Create the key pair and configure the J2EE Engine for HTTPS
Installing the SAP Cryptographic Library

The SAP Cryptographic Library is the default security product delivered by SAP for performing encryption
functions in SAP Systems. For example, you can use it for providing Secure Network Communications
(SNC) between various SAP server components or for using the Secure Sockets Layer (SSL) protocol with
the SAP Web Application Server.
The SAP Cryptographic Library can be used in case you want to
2004 SAP AG
Enable SSL communication on the Internet Communication Manager (ICM)

Use Secure Network Communication (SNC) on the ABAP stack
Use Secure Network Communication (SNC) on the J2EE Engine
Obtaining the SAP Cryptographic Library

The installation package is available for authorized customers on the SAP Service Marketplace at
http://service.sap.com/swcenter.
You must comply with German export regulations in order be able to receive the SAP Cryptographic Library.
The distribution of the SAP Cryptographic Library is subject to and controlled by German export
regulations and is not available to all customers. In addition, the library may be subject to local
regulations in your own country that may further restrict the import, use and (re-)export of
cryptographic software. If you have any further questions on this issue, contact your local SAP
subsidiary.
The SAP Cryptographic Library installation package sapcrypto.car contains the following files:
The SAP Cryptographic Library (sapcrypto.dll for Windows NT or libsapcrypto.<ext> for UNIX)
A corresponding license ticket (ticket)
The configuration tool sapgenpse.exe
The JDK 1.3.1 supports only 32-bit applications. Thus you need the 32-bit SAP Cryptographic
Library for the J2EE Engine, independent of the operating system you are running.
If your Web AS runs with 64-bit, you have to use the 64-bit library for the ABAP kernel and the 32-bit library
for the J2EE Engine.
2004 SAP AG
Installing the SAPCRYPTOLIB on the SAP Web AS (ABAP Stack)

To install the SAP Cryptographic Library on the SAP Web AS, follow the following procedure:
Logon to the operating system of the Web AS as user <sid>adm
Extract the content of the SAP Cryptographic Library installation package using the SAPCAR tool
(see SAP Note 212 876).
UNIX:
DIR_EXECUTABLE: /usr/sap/<SID>/SYS/exe/run/
Location of SAP Cryptographic Library: /usr/sap/<SID>/SYS/exe/run/libsapcrypto.so
Windows NT:
DIR_EXECUTABLE: <DRIVE>:\usr\sap\<SID>\SYS\exe\run\
Location of SAP Cryptographic Library: <DRIVE>:\usr\sap\<SID>\SYS\exe\run\sapcrypto.dll
Copy the configuration tool sapgenpse.exe to any local directory, for example, also
$(DIR_EXECUTABLE).
Check the file permissions for the SAP Cryptographic Library.
If, for example, you copied the library to its location using ftp on UNIX, then the file permissions
may not be set correctly. Make sure that <sid>adm (or SAPService<SID> under Windows NT) is
able to execute the library's functions.
Copy the ticket file to the sub-directory sec in the application server's instance directory
$(DIR_INSTANCE):
UNIX:
DIR_INSTANCE: /usr/sap/<SID>/<instance>
Location of the ticket: /usr/sap/<SID>/<instance>/sec/ ticket
Windows NT:
DIR_INSTANCE: <DRIVE>:\usr\sap\<SID>\ <instance>
Location of the ticket: <DRIVE>:\usr\sap\<SID>\ <instance>\sec\ticket
Set the environment variable SECUDIR to the sec sub-directory. The application server uses this
variable to locate the ticket and its credentials at run-time.
If you set the environment variable using the command line, then the value may not be applied
to the application server's processes. Therefore, we recommend setting SECUDIR in the
startup profile for the application server's user or in the registry (Windows NT).
Result
The SAP Cryptographic Library is installed on the application server and the environment is set up correctly
so that the application server can locate the library at run-time.
Enabling SSL on the ICM of the Web AS (ABAP Stack)

Process Flow
To enable SSL on the ICM the following steps are necessary:
Setting the profile parameters for using SSL
2004 SAP AG
Creating the SSL server PSE
Creating the standard SSL client PSE
Testing the connection for SSL server authentication.
Setting the Profile Parameters for using SSL

Set the profile parameters in the application server's instance profile as shown in the table below. If you
used the recommended directory DIR_EXECUTABLE, then use the following values for the location of the
SAP Cryptographic Library:
UNIX:
$(DIR_EXECUTABLE)/libsapcrypto.<ext>
Windows NT:
$(DIR_EXECUTABLE)\sapcrypto.dll
Logon to the Web AS and start transaction RZ10.
Set the following profile parameters in the application server's instance profile:
ssl/ssl_lib
path and file name of the SAP Cryptographic Library
o UNIX: /usr/sap/<SID>/SYS/exe/run/libsapcrypto.soWindows
o NT: <DRIVE>:\usr\sap\<SID>\SYS\exe\run\sapcrypto.dll
sec/libsapsecu
ssf/ssfapi_lib
ssf/name
o UNIX: SAPSECULIB
o NT: SAPSECULIB
icm/plugin_<xx>
o <xx>
the number of the ICM plug-in. By default 0 is used for HTTP, and 1 for HTTPS.
Example
icm/plugin_1=PROT=HTTPS,PLG=/usr/sap/CT5/SYS/exe/run/httpplugin.so
icm/server_port_<xx>
o HTTPS port for SSL communication

Example
icm/server_port_1=PROT=HTTPS, PORT=44322, TIMEOUT=900
Save the settings.
2004 SAP AG
Ignore the warnings that the parameters are not known to the system.
Restart the application server.
Creating the SSL Server PSE

The SSL Server PSE contains the application server's security information that it needs to communicate
using SSL. If you have a system with multiple application servers, then the following options are available:
Use a single system-wide SSL server PSE for all servers.
Use server-specific SSL server PSEs for individual application servers.
Use a combination of both types.
(Some application servers use a system-wide SSL server PSE, and other application servers use
server-specific SSL server PSEs)
Use a system-wide PSE for those application servers that are accessed via a Network Address
Translator (NAT). Use the NAT's fully-qualified host name as the Common Name (CN) part of
the Distinguished Name.
Prerequisites
You know the naming convention to use for the server's Distinguished Name. The syntax of the
Distinguished Name depends on the Certification Authority (CA) you use.
If you use the SAP CA, the naming convention is CN=<host_name>,

OU=I<installation_number>-<company_name>, OU=SAP Web AS, O=SAP Trust Community,
C=DE.
Procedure
Logon to the Web AS and start transaction STRUST.
Select the SSL Server PSE node. Using the context menu by right mouseclick, choose Create (if no
PSE exists) or Replace.
The <Create/Replace> PSE dialog appears.
2004 SAP AG
The SSL entries are only visible if the SAP Cryptographic Library is installed and the profile
parameters are set and active.
Enter the distinguished Name parts for the default SSL server PSE in the corresponding fields.
Name = <host_name>
Use a wildcard for the host_name for the default SSL server PSE. (*.<domain>).
Org. (opt.) = Test
Comp./Org. = MyCompany
Country = US
If you use the SAP CA, see the SAP Web AS certificate request area on the SAP Service
Marketplace at http://service.sap.com/tcs for information on how to determine the server's
Distinguished Name.
If you want to use a reference to a CA name space, then elements contained in the CA's name
space are automatically used for the server's Distinguished Name. In addition, you cannot
modify the Country field. Use the toggle function to activate or deactivate the reference to a CA
name space.
The system uses these components to build a default Distinguished Name to use for a system-wide PSE, as
well as for building the server-specific names for individual PSEs.
The SSL Server screen then appears. In this screen, you can decide whether the individual application
servers should use the default Distinguished Name and system-wide SSL server PSE or individual PSEs.
The default Distinguished Name appears in the Default PSE DN field. The server-specific Distinguished
Names appear in the table in the Distinguished Name column.
If necessary, modify or delete any of the individual application server's Distinguished Names to
meet you own needs.
Delete the distinguished name entry for any servers that should receive the default
distinguished name.
Assign the same Distinguished Name to all servers that are to be accessed via a NAT.
Modify the distinguished name to adhere to your CA's naming convention (for example, adding
an attribute such as L=<Locality>).
2004 SAP AG
If the system could not determine a Distinguished Name for the server, then an error has
occurred (for example, the ICM has not been installed on the server).
Choose Enter.
You return to the Trust Manager screen.
Result
The system creates the SSL server PSEs SAPSSLS.pse and distributes them to the individual application
servers.
Creating the SSL Client PSE

In a GRMG scenario the Web AS (ABAPStack) also acts as a client. You therefore also need to create an
SSL client PSE. Please carry this out in the same way as for the creation of the SSL server PSE as
described above for the node SSL-Client (Standard).
2004 SAP AG
Result
The system creates the SSL server PSEs SAPSSLC.pse and distributes them to the individual application
servers.
Restarting the ICM

Before the SSL configuration becomes active, you need to restart the ICM.
Start transaction SMICM.
Choose Administration ICM Exit soft.
Check if the services are running.
If the service is not active:

Activate the service.
2004 SAP AG
Testing the Connection for SSL Server Authentication

Use this procedure to make sure that SSL support is set up correctly for connections where the SAP Web
AS is the server component in the connection.
Procedure
Start a Business Server Page (BSP) using an HTTPS connection and the SSL port.
Start the standard BSP test application IT00 with the URL.
https://host123.mycompany.com:443/sap/bc/bsp/sap/it00/default.htm.
If your Web browser cannot completely verify the SAP Web AS's server certificate, then you will receive a
dialog stating the reason. For example, if your Web browser does not possess the issuing CA's root
certificate as a trusted root certificate, then you are informed and have the opportunity to trust the server at
this time.
If you have problems calling the URL please check if the service is active in transaction SICF. You need to
navigate through the tree according to the called URL.
2004 SAP AG
Result
The ICM is enabled to accept incoming SSL communication requests.
Installation of the cryptographic library on the Portal

J2EEngine (SAP Web AS Java Stack)
Prerequisites
To enable SSL on the SAP Web AS, you need to install the SAP Cryptographic Library. As this library is not
only used for SSL communication, but also for SNC, we have described the installation in a separate
document. The SAP Cryptographic Library is not needed for SSL on the SAP J2EE Engine.
For enabling SSL on the SAP J2EE Engine, a different cryptographic software component is necessary. As
this component is only needed for enabling SSL on the SAP J2EE Engine, the installation is described in
this chapter.
Process Flow
To enable SSL on the SAP J2EE Engine the following steps are required
- Downloading the cryptographic software
2004 SAP AG
- Installing the cryptographic software

- Setting the HTTP port for secure communication
- Enabling the keystore and SSL services
- Configuring key pairs and certificates
- Configuring the SSL service
- Testing the connection for SSL server authentication
Downloading the required Cryptographic Software

Due to export restrictions on military and dual use goods, the cryptographic modules required for secure
communication are not part of the SAP J2EE Engine installation package. You have to download them
separately from the SAP Service Marketplace.
The current EP 60 SP1 installation process by SAPINST forces you to install the Cryptographic Software as
a mandatory step of the Portal Installation. If you are sure you sure you have installed the cryptographic
software already, you can skip this chapter. In case of problems this is a good point to start at.
Start your browser and browse to http://service.sap.com/swcenter.
Log in with your SAP S-user ID.
Navigate to SAP Cryptographic Software.
Sign the agreement on export regulations (if this is your first visit to the site).
Select the Java Cryptographic Toolkit and download it to a temporary directory on your system.
Obtain the SAPCAR.exe tool (see SAP Note 212 876)
Create a directory named CryptoToolkit in the temporary directory mentioned above
Open a command window in the CryptoToolkit directory
Unpack the Java Cryptographic Toolkit
SAPCAR xvf /usr/sap/tmp/CryptoToolkit/SAPJAVACRYPTOTOOLKIT.CAR

This creates the files
LEGAL.TXT
README.TXT
iaik_jce.jar
iaik_jsse.jar
iaik_ssl.jar
w3c_http.jar
2004 SAP AG
Installing the Cryptographic Libraries

Copy the Java archive files iaik_jce.jar, iaik_jsse.jar and iaik_ssl.jar to the following
directories:
<J2EE_INSTDIR>/admin/lib
<J2EE-INSTDIR>/cluster/dispatcher /additional-lib
<J2EE-INSTDIR>/cluster/server /additional-lib
If you connect remotely to the J2EE Engine through the Administrator tool, the libraries have to
be available in directory local /admin/lib.
Copy the Java archive file w3c_http.jar to the following directory:
<J2EE-dir>/cluster/server /additional-lib
Setting the HTTP Port for secure Communication

Per default, the port for secure HTTP communication is set to 443. The SAPINST changes the default ports.
Please check <J2EE INSTDIR>/prepconf.log to find the new ports. If you would like to choose a
different port, you need to configure the server correspondingly.
Launch the J2EE configtool with
UNIX
<J2EE INSTDIR>/configtool/configtool
MS Windows
Start Programs SAP J2EE Engine 6.20 Tools Config tool
Navigate to Dispatcher Services http.
Change to your port and add the new value.
Apply your settings.
2004 SAP AG
Restart your portal with

<J2EE_INSTDIR>/confgtool/unixdeamon stop
<J2EE_INSTDIR>/confgtool/unixdeamon start
Enabling the Keystore and SSL Services

After installing the IAIK libraries, you have to make sure that the SSL and the keystore services are started
automatically during the start-up of the SAP J2EE Engine. Per default these services are set to the manual
mode.
Shut down all running instances of the SAPJ2EE engine server (service) and the dispatcher.
Launch the J2EE configtool with
UNIX
<J2EE INSTDIR>/configtool/configtool
MS Windows
Start Programs SAP J2EE Engine 6.20 Tools Config tool
Navigate to:
cluster/dispatcher services keystore
cluster/server services keystore for all service nodes.
2004 SAP AG
Navigate to the SSL service(s).

Set the Startup Mode from Manual to Always.
Restart your portal with:

<J2EE_INSTDIR>/confgtool/unixdeamon stop
<J2EE_INSTDIR>/confgtool/unixdeamon start
2004 SAP AG
Creating a Key Pair and a self-signed Certificate

For the server authentication during the SSL handshake, a server certificate is needed on the J2EE Engine.
These steps describe, how you can generate a key pair and a certificate signing request, which might be
signed by a certification authority (CA). The EP 60 SP1 comes with a self-signed certificate by default. You
find this self-signed certificate at <J2EE_INSTDIR>/ume/ as verify.dse and verify.pse.
Launch the SAP J2EE Engine Administrator.
UNIX
<J2EE_INSTDIR>/admin/go
Windows
Start Programs SAP J2EE Engine 6.20 Administrator
Logon to the Visual Administrator.
Administrator is not the j2eeadm.

Port is the <p4port> of your J2EE Engine.
In the left pane, navigate to Cluster Server Services Keystore.
2004 SAP AG
If the tab Runtime is not displayed, check whether the IAKI libraries are available in the
/admin/lib directory of your Administrator tool.
Change to the Certificate Generation tab.
Edit the Subject Properties.

Change the record values to match your requirements.
Use the TAB key to change between input fields.
For the Common Name you might use the fully qualified host name that you want to use in com-
munication with the J2EE Engine
After changing the Common Name value, submit your editing with the TAB key.
The entry in the field edited last will only become active, if you navigate away from this field.
Choose a name for the certificate and enter it in the Key Alias field.
2004 SAP AG
Click the Generate button.
Based on your editing, the SAP J2EE Engine Administrator generates a new key record containing a self-
signed certificate. It stores the key record in the keystore of the SAP J2EE Engine.
Result
You have created a key pair and a self-signed certificate in your keystore.
2004 SAP AG
Configuring the SSL Service

The next step is to assign the new certificate for SSL authentication to be used by new and active sockets in
the SSL service.
Start the J2EE Engine Administrator and log on to the SAP J2EE Engine.
Navigate to the SSL service of server node Server Services ssl.
If you are using the cluster version of the J2EE Engine with several server nodes, it is sufficient
to configure the SSL service only on one server node.
Choose Dispatcher One and activate the Server Identity tab in the lower right pane.
Assign your server certificate to new and active sockets as follows:
Choose New Sockets in the Configuration pane.
Choose Add in the Certificates tab and select your server certificate from the pop-up list.
Close the pop-up list with OK.
2004 SAP AG
The certificate is shown in the list of enabled certificates.

Choose Active Sockets in the Configuration pane.
Add your server certificate to each socket in the socket list.
Close the SAP J2EE Engine Administrator.
2004 SAP AG
Testing the connection for SSL server authentication

Verify that the J2EE Engine has been successfully configured for SSL.
Logon to your portal by calling the URL
https://<host>.<ssl_port>/irj
Confirm the information with Yes.
Result
Your Portal has been enabled for SSL communication.
Importing The Self-signed Portal Certificate into the Web AS

Call your portal via the HTTPS URL https://<portal_host><https_port/irj/ in an Internet Explorer.
At the security alert prompt choose View Certificate.
2004 SAP AG
In the next screen choose the tab Details and then Copy to File.
Use the Certification Export Wizard to copy the certificate to a directory on your PC.
2004 SAP AG
Start transaction STRUST in your Monitoring System again.
Import the certificate from your PC into the SSL Server PSE as well as into the SSL Client PSE.
2004 SAP AG
Now you can configure the GRMG test as described in the chapter GRMG Check of the Portal with the
single difference that you need to adapt the grmgRequesthttps_template.xml (it is a different scenario
name and https port).
Further information on SSL

For more details on SSL especially if you want to use an internal or external Certification Authority, please
see: http://service.sap.com/securityguide How to - Guides SAP Web AS 6.20:
How to Security Series: 2 SAP Cryptographic Library
http://service.sap.com/~sapidb/011000358700008896112002E/
How to Security Series: 3 Enabling SSL
http://service.sap.com/~sapidb/011000358700008892512002E/
Troubleshooting GRMG (http and https)

If you face problems uch as failure of the http connection:
Go to transaction SMICM and set the trace level to 3.
2004 SAP AG
Start the GRMG scenario in transaction GRMG.
Open the trace file again in transaction SMICM.
2004 SAP AG
Analyze the trace file.
Here for example the SSL Server pse SAPSSLS.pse does not contain the right certificate to
connect to the portal J2EE.
2004 SAP AG
Availability Check by Process monitoring

Checking the availability of the database is currently restricted to checking the process availability at
operating system level. Process monitoring requires the operating system collector SAPOsCol and the
CCMS agent SAPCCMSR, both of which you have already installed (see SAPCCMSR and SAPOsCol).
Configuring the MS SQL Server Availability Check Under Microsoft Windows
Switch to SAPOsCols working directory //<host>/saploc/prfclog (Microsoft Windows)
Edit the file dev_proc. Ensure that the file begins with $PROC and ends with $. Enter a new line
with the following content between the start mark $PROC and the end mark $:
*sqlservr.exe*
Save your changes.
Open the Windows Service Manager and stop and restart the SAPOsCol service.
Configuring the Oracle Availability Check
Switch to SAPOsCols working directory //<host>/saploc/prfclog (Microsoft Windows) or
/usr/sap/tmp (UNIX).
Edit the file dev_proc. Ensure that the file begins with $PROC and ends with $. Enter new line(s)
between the start mark $PROC and the end mark $ with the following content:
MS Windows
*oracle.exe*
UNIX
*ora_arc*
*ora_reco*
*ora_smon*
*ora_ckpt*
*ora_lgwr*
*ora_dbw*
*ora_pmon*
Save your changes.
MS Windows
Open the Windows Service Manager and stop and restart the SAPOsCol service.
UNIX
Restart SAPOsCol manually. To do this, switch to /usr/sap/ccms/bin and enter the following
commands:
saposcol k (stops the process)
saposcol l (starts the process)
You have now successfully activated process monitoring for the database processes.
Start transaction RZ20 by entering /nrz20 in the command field and open the Availability Monitoring
monitor in your monitor set <my monitor set>.
After a few minutes, the results appear in the sub tree OS Process Availability Processes monitored by
SAPOsCol. You can also find information about the availability of SAPOsCol and SAPCCMSR there.
You can monitor any processes at operating system level in this way. You can optionally make
the following entries in dev_proc depending on the components to be monitored:
#J2EE Server *java*
2004 SAP AG
#TREX *TREXDaemon.exe*
*TREXFilter.exe*
*TREXIndexServer.exe*
*TREXPreprocessor.exe*
*TREXQueueServer.exe*
*TREXNameServer.exe*
#IIS
*Inetinfo.exe*
*dllhost.exe*
Ensure that the file begins with $PROC and ends with $.
Further Information on availability check by process monitoring
You can monitor any processes at operating system level in this way. You can optionally make
the following entries in dev_proc depending on the components to be monitored:
#TREX *TREXDaemon.exe*
*TREXFilter.exe*
*TREXIndexServer.exe*
*TREXPreprocessor.exe*
*TREXQueueServer.exe*
*TREXNameServer.exe*
#IIS
*Inetinfo.exe*
*dllhost.exe*
# Novel eDirectory
*dhost.exe*
The processmonitoring appears in the CCMS.
2004 SAP AG
Setting Up Central Configuration

Central Parameter Reporting for EP6 SP1
Enable the CCMS reporting of the portal monitoring data inside the portal.
Log on with a user with portal administration rights.
Navigate to System Administration System Configuration Monitoring Configuration and check

the check boxes Collect monitoring Data and Write monitoring data to CCMS.
As of EP6 SP2, EP parameters are automatically transferred to the central monitoring system if
SAPCCMSR and JMON are installed.
To display the aggregated JARM (Java Application Responsetime Measurement) records:
Start transaction RZ20 in the central monitoring system, by entering /nrz20 in the command field.
Open the Configuration Monitoring monitor in your monitor set <my monitor set>.
You can view the portal-specific parameters and version information in the J2EE Applications sub
tree.
This data is only transferred if the shared memory segment is correctly set up. SAPCCMSR must be started
with the correct user before JMON and the EP are started.
After proper setup of the portal, the jmon api and the sapccmsr the portal versions and configuration
monitoring appears in rz20:
2004 SAP AG
Detailed portal versions and configuration monitor
The Portal Runtime Monitor appears:
Detail Portal Runtime Monitor
Central Parameter Reporting for the SAP J2EE Engine

The SAP J2EE Engine also reports important configuration information to the central monitoring system.
2004 SAP AG
Start transaction RZ20 in the central monitoring system, by entering /nrz20 in the command field
Open the monitor Configuration Monitoring in your monitor set <my monitor set>.
You can view the portal-specific parameters and version information in the J2EE Engine sub tree.
Central Parameter Reporting for TREX

Central configuration and TREX alerting is described in detail in SAP Note 639786.
Copy the trexmon shared library that is appropriate for your operating system from the
moni_temp directory to the SAPCCMSR working directory (using Microsoft Windows, the directory
is //<host>/saploc/prfclog/sapccms; under UNIX, it is /usr/sap/tmp/sapccmsr):
MS Windows
trexmon.dll
UNIX
trexmon.so
Insert the following line into the file sapccmsr.ini, which is in the SAPCCMSR working directory:
PlugIn <drive>/saploc/prfclog/sapccms/trexmon.dll (Microsoft Windows)
PlugIn /usr/sap/tmp/sapccmsr/trexmon.so (UNIX)
Save your changes.
You can find an sapccmsr.ini example in the appendix.

Copy the file Trxmon.ini from the moni_temp directory to the agents working directory:
<drive>/saploc/prfclog/sapccms/
/usr/sap/tmp/sapccmsr/
Adjust the following line for your installation:
TREXROOT1= <Root dir TREX>
Save your entries.
Restart SAPCCMSR. Using Microsoft Windows, restart the service with the same name; using
UNIX, enter the following commands:
/usr/sap/ccms/bin/sapccmsr stop pf=/usr/sap/tmp/sapccmsr/j2ee.pf
/usr/sap/ccms/bin/sapccmsr DCCMS pf=/usr/sap/tmp/sapccmsr/j2ee.pf
Check whether the file sapccmsr.log contains entries of the following type:
INFO: PlugIn: trying to load Dynamic Library
c:/usr/sap/prfclog/sapccmsr/trexmon.dll, trace level 1...
INFO: PlugIn: Dynamic Library c:/usr/sap/prfclog/sapccmsr/trexmon.dll
successfully loaded.
INFO: PlugIn manager initialized successfully.
As of this point, using the shared library, the configuration information is sent to the central monitoring
system through SAPCCMSR.
Start transaction RZ20 in the central monitoring system by entering /nrz20 in the command field.
Open the monitor Configuration Monitoring in your monitor set <my monitor set>.
You can view the portal-specific parameters and version information in the TREX sub tree.
Your configuration monitor also displays configuration information about the CCMS agents
registered with the central system and your SAP Web AS.
2004 SAP AG

Activating the single activity trace in the Portal
Logon to the portal with administrator rights.
Go to System Administration Monitoring Activity Tracing.
Search for the user you want to trace (he must not be logged in currently) and click Activate
Tracing.
The trace is written to file ../cluster/server/log/sat.trc.0.
Do not delete without planning to restart the J2EE Engine.
Register the sat.trc.0 to the Log Viewer_server

cd /usr/sap/Epdir//j2ee/j2ee_00/tools/lib/server
./register_log.sh localhost 4444
/usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/log/sat.trc.0 SATLog
For more details about registering log files see chapter Standalone Log Viewer.
Start the SAP Log Viewer client, connect with the Standalone Log Viewer server and check the log.
2004 SAP AG
Change the standard time frame for SAT tracing in the

Portal
The default time frame for a single activity trace is 30 minutes. If you want to change this time frame:
Logon to the portal with administration rights.
Choose System Administration System Configuration Service Configuration.
Browse the Portal Catalog to com.sap.portal.runtime.application.monitor Services

SATController.
2004 SAP AG
Open the service SATController by clicking the right mouse button and choose Edit.
Configure the desired time frame in property SATExpirationLength with syntax h for hours or m for
minutes in every language.
This setting is now valid for every user, specific settings for single users are not supported.
2004 SAP AG
A restart of the portal service is necessary in order to enable the setting on each portal node.
Activating the single activity trace in the TREX

The TREX carries out search, index-create, etc. requests in different services. Therefore the activity tracing
must be enabled for each service separately. The configuration files:
TREXIndexServer.ini
TREXNameServer.ini
TREXPreprocessor.ini
TREXQueueServer.ini
TREXWebServer.ini
need to be adapted.
Open the configuration files and check for the entry.
If they dont exist you have to create them.
[ccms]
record = on
satracer = Jarmlike
[satjarmlike]
file = <sat_file>
<sat_file>
Replace <sat_file> with the destination file of the trace information.
Use a path relative to <TREX INSTDIR> eg.
trace/TrexIndexServer.sat
2004 SAP AG
trace/TrexQueueServer.sat
trace/TREXPreprocessor.sat
trace/TREXQueueServer.sat
trace/Webserver.sat
Install a Log Viewer server on every TREX host and register the TREX trace files as described in
the chapter Installing and Configuring the Standalone Log Viewer 6.30.
Manually adding new monitor sets to CCMS
This is background information should you not import the transport as described in Importing a
Transport Request into the Central Monitoring System/Solution Manager.
Log on to the monitoring R/3 system, and call transaction RZ20.
Choose Extras Activate maintenance function.
Click the button Create to create a new monitor set and click Enter.
Click Enter.
The message Monitor set Portal Monitor EP60 was saved appears in the status line.
Position the cursor on the monitor set and click the button Create to create a new monitor.
Adding a new Monitor
Expand the tree that belongs to the SID of the monitoring R/3 system and select the monitor
elements that are of interest.
As an example, we suggest selecting the following element if you do not send data to the CCMS from one of
your EP component servers:
2004 SAP AG
System Configuration
This element shows some configuration data from the monitoring R/3 system itself, which can be removed
later on because at least one element needs to be selected to create a monitor. In case you have already
installed the SAPOSOL and the CCMS Agent to report data into the monitoring R/3 system you should
choose the elements that are of interest instead.
Click Save.
In the next pop-up enter the name of the monitor.

Here, we assumed that a monitor set EP Monitor was already created.
Click Enter.
Expand the monitor set Portal Monitor 60 and double click the monitor EP Monitor to view the
monitored data.
Adding a new monitor to a monitor set
Log on to the monitoring R/3 system and call transaction RZ20.
Position the cursor on the monitor set and click Create to create a new monitor.
2004 SAP AG
Follow the instructions in the section [Adding a new Monitor] in Adding new monitor sets in CCMS.
Adding new elements to a monitor in CCMS
Log on to the monitoring R/3 system and call transaction RZ20.
Expand the monitor sets that are of interest.
Position the cursor on the monitor and click the button Change to get the list of systems and
elements.
Choose the new monitor data to be referenced to your monitor.
Click Save.
As a result the monitors appears in the RZ20 SAP CCMS Technical Expert Monitors Al Monitor
Contexts.
Log file monitor
Operating System Monitor
SAP CCMSR Self Monitor
2004 SAP AG
Defining a CCMS Monitor for the SAP J2EE Engine

As an additional benefit of the configuration and starting of the J2EE Monitor Server you can monitor
performance and availability information of the J2EE Engine in the CCMS.
With SAP System 6.20, you already have a monitor SAP CCMS Monitor Templates J2EE Engine. If you
want remote services to check your SAP J2EE Engine, then proceed with the following steps to define a
new monitor in RZ20:
Start transaction RZ20.
Activate the maintenance function by choosing the menu Extras Activate maintenance function.
Create a new monitor within an existing monitor set.

Otherwise you have to create a monitor set in advance.
Now create a new monitor in the [new] monitor set.
Create a new node.
Position the cursor on <<< New monitor >>> and select Edit Create nodes.
2004 SAP AG
For release 6.20 of the SAP J2EE Engine:

In the popup choose Rule node.
Select the rule 'CCMS_GET_MTE_BY_CLASS'.
You are now prompted to enter a value for the parameter 'R3System'.
2004 SAP AG
Select the R/3 system and then enter the MTE class 'SAP J2EE Engine' (for release 6.20).
Save your changes and enter as a name for the new monitor 'EWA SAP J2EE Engine'.
The name of the monitor must have exactly this same name for SAP Remote Services.
If you did not define a monitor for the SAP J2EE Engine in the previous step:
In transaction RZ20, choose SAP CCMS Technical Expert Monitors and System All Monitoring
Segments All Monitoring Contexts to find your monitoring data.
If you double click on the newly defined monitor, the monitor trees for all your installations of the SAP J2EE
Engine that report to CCMS should appear, as shown below:
2004 SAP AG
SAP J2EE Version monitoring

After proper setup of the SAP J2EE Engine monitor server the versions monitoring appears in the RZ20.
2004 SAP AG
SAP J2EE Service Status Monitoring

After proper setup of the SAP J2EE Engine monitor server the status monitoring appears in the rz20.
SAP J2EE Workload Monitoring

After proper setup of the SAP J2EE Engine monitor server the workload monitoring appears in the rz20.
2004 SAP AG
Defining Automatic Alert Notification in the

Central Monitoring System
With the monitoring architecture, you can define auto-reaction methods that are automatically executed
when alerts occur. As of SAP Basis 4.6A, you can assign the method CCMS_OnAlert_Email to MTE classes
in your system. If an alert occurs in this MTE class, you are informed by e-mail, fax, or pager, even if you
are not working in the Alert Monitor.
CCMS_OnAlert_Email can automatically dial a pager or send an e-mail or a fax to the following addresses:
A Business Workplace user in client 000
A distribution list or an external e-mail address
The auto-reaction method for sending the e-mail is started at the most five minutes after the alert occurs.
However, there can be a delay before the e-mail is sent to external e-mail addresses (that is, addresses of
users that are not defined in client 000 of the same SAP R/3 System), depending on the settings in
SAPconnect. You should therefore set the period for the SAPconnect send process to less than an hour.
The message text of the e-mail contains the same information that is displayed in the Alert Monitor:
What is the problem?
Where and when did it occur?
What severity and what color does the alert have?
Create a Distribution List

To dial multiple pagers or to send an e-mail or a fax to multiple users (external recipients or recipients in
client 000), you must first create a distribution list that contains the required data for the recipients (pager
number, name, e-mail address, fax number).
Use the following description to create a distribution list:
Enter transaction SBWP.
Create a subfolder for Shared Folders

(right mouse click on Shared Folders).
2004 SAP AG
Double click the newly created sub folder to create the distribution list.
Select Distribution List.
Select Shared Distribution List.
Set a name and a title and choose Create.
2004 SAP AG
On the new screen choose the tab Attributes.
Under Feature list select with the F4 help the newly created shared folder (here EP 60 Monitor).
Select the tab Distr. List content and add your email address with Recip. type Internet Address.
Here admin@company.com.
2004 SAP AG
Select Save.
Leave the Buisness Workplace and return with transaction SBWP.

If you now select the newly created share folder EP 60 Monitor it should appear as shown below:
2004 SAP AG
Set up an Email Connection for SAPconnect

SAPconnect must be configured in client 000, if the message is to be sent to an external address.
Use transaction SCOT to configure SAPconnect.
Open the tree INT and double click SMTP for the appropriate settings.
Note 455140 describes in more detail how to setup the mail server settings.
Tailoring the Auto-Reaction Method

Choose CCMS Configuration Alert Monitor or call transaction RZ21.
In the methods group box, select Method Definitions and choose Display Overview.
Select the method CCMS_OnAlert_Email and choose Edit Data.
Choose change mode with the Display Change ( ) push button, and choose tab page
Parameters.
Fill out the fields as follows:
Parameter Description
SENDER SAP user name of the person in whose name the e-mail is sent.
Therefore a user in client 000 is needed.
RECIPIENT SAP user name of the e-mail recipient, distribution list, or external
e-mail address; to automatically send an e-mail to multiple external
e-mail addresses, you must create a distribution list in client 000
that contains these external addresses.
If the user is not defined in client 000 you must also specify the
system and the client in which the user exists (such as
C11:003:PARKERJ).
RECIPIENT-TYPE Indicator for the address type

ID
Users that are defined in the SAP R/3 System in clients other than 000 cannot be specified in the Business
Workplace directly as sender or recipient; they are regarded as shared distribution list. You should therefore
specify the address type C (Shared distribution list) for client-specific senders and recipients in the
parameters tab page.
If you want to define different recipients for different alerts:
Copy the method definition of CCMS_OnAlert_Email.
Select the method in the list and choose Copy ( ).

You must release the copied method as a data collection method again (see Defining, Releasing,
and Transporting Methods).
2004 SAP AG
Save your entries.
Assigning the Thresholds and Autoreaction Methods to

the Desired Node
For a reliable assignment you should assign auto reaction methods to MTE-classes and thresholds to
attribute groups. If you assign the method/threshold to a node directly, the method/threshold will be
assigned to the TID of the node. This TID can change if the node changes its position in the monitor tree, a
result of this can be that the node has a new TID and the TID where you have assigned the
method/threshold points to nothing.
Assign auto reaction Method to the Selected MTE Class

Start the Alert Monitor using transaction RZ20 or choose CCMS Control/Monitoring Alert
Monitor.
Start the desired monitor from the list by double clicking it.
Select the desired node and choose from the menu Views Method allocation as result the display
of the monitor tree should appears like this:
You should assign the auto reaction method to a MTE-class.
2004 SAP AG
Select Extra Activate maintenance function.
Select the node where you want assign an auto reaction method and choose Properties.
Double click on the MTE class.
2004 SAP AG
Choose change mode with the Display Change ( ) pushbutton.
Select method name from the auto reaction method box and choose the F4-help.
From the F4help select CCMS_OnAlert_Email or CCMS_OnAlert_SMS.
As result the screen should appear like this.

Save your work and use the back button twice.
2004 SAP AG
The assigned auto reaction method appears in the monitor tree in the method allocation view.
Repeat these steps for each node from which you require an e-mail or sms as auto reaction
method.
For further information see SAP Note 0176492.
Setting the Threshold Values for monitored processes

As the expected CPU and memory usage is different for each process, you should customize the threshold
values of the corresponding performance attributes to be able to use the alert functions optimally. Please
assign the threshold to:
Start the Alert Monitor using transaction RZ20 or choose CCMS Control/Monitoring Alert
Monitor.
Start the desired monitor from the list by double clicking it.
2004 SAP AG
Select the desired node and choose from the menu Views Method allocation.
As result the display of the monitor tree should appear like this:
Select Extra Activate maintenance function.
Select the node where you want to assign a threshold and choose Properties.
Choose change mode with the Display Change ( ) pushbutton.
Choose the Performance Attribute tab and enter the thresholds in the thresholds values box.
Please know, that all thresholds are assigned to the attribute group which is in the box Performance
properties assigned from group.
2004 SAP AG
Save your work and go back.
Saving collected data for the last 30 days in Operating

System Monitor
The data collected by SAPOSCOL are stored in the shared memory segment as hourly average values for
24 hours and then deleted. The data collected by SAPOSCOL is only saved for the last 30 days for those
hosts for which the indicator Save last 30 days is activated in transaction AL15 (Modify SAPOSCOL
Destination) (see Setting the SAPOSCOL Destination in the Central System [Page 38] of the documentation
for SAPOSCOL).
If you are using CCMS agents, you can display the data collected by SAPOSCOL not only for the local
system, but also for remote systems. This means that all possible data for remote SAP application servers
and their database servers (specified using the parameter SAPDBHOST) is available to you in the operating
system monitor. For any hosts or dedicated database servers, this applies only for the data for the last 24
hours.
The data for the last 30 days is only stored if you maintain the SAPOSCOL destination:
Install SAPOSCOL and the appropriate CCMS agent [Agents] on the host.
Start transaction AL15 (SAPOSCOL Destination) in the central system.
Enter the SAPOSCOL destination of the remote host.

If the connection uses a CCMS agent, this is the RFC destination of the CCMS agent on this host.
For agent SAPCCMSR (which monitors any hosts with no SAP system), the destination has the
name structure SAPCCMSR.<Hostname>.99.
To edit the destination, choose Modify.

The Modify SAPOSCOL Destination screen appears.
2004 SAP AG
The individual fields have the following meanings:

Text
Description of the destination.
DB Server
This indicator is activated for a database server; its values for the last30 days are then automatically
available.
Save last 30 days
Select this indicator if you want to save the values collected by SAPOSCOL in the operating system monitor
for 30 days.
Further Information
Appendix
Useful Programs
Replace.exe
replaces strings in a large number of files under Microsoft Windows. The program can be found in the
moni_temp directory.
Task Scheduler
To start Task Scheduler on your Windows server:
Click Start, - All Programs, - Accessories, - System Tools, and then select Scheduled Tasks.
You can also drag-and-drop programs such as iis_status.bat into the Task Scheduler to quickly add a new
task or use the provided "Create Scheduled Task" wizard. More information about this tool is available via
the following links at Microsoft:
Task Scheduler:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddo
cs/server/tasksched_topnode.asp
Checklist: Configuring Task Scheduler:
http://www.microsoft.com/windowsxp/home/using/productdoc/en/default.asp?url=/windowsxp/home/using/pr
oductdoc/en/Tasksched_checklist.asp
HOW TO: Use Iisreset.exe and Task Scheduler to Schedule IIS to Restart in Windows 2000:
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B317584
WGET:
WGET enables you to call URLs from the command line or from within a script.
Download:
You can download and install from one of the following links. WGET 1.8.2 from
http://studwww.rug.ac.be/~bpuype/wget/ were downloaded and implemented to build the tests described
above.
http://www.gnu.org/software/wget/wget.html
http://studwww.rug.ac.be/~bpuype/wget/
Leech ftp
LeechFTP is a freeware FTP client with some nice features.
Its available here: http://stud.fh-heilbronn.de/~jdebis/leechftp/
2004 SAP AG
JEdit
JEdit is a freeware editor based on java with some nice features.
Its available here: http://www.jedit.org
Useful SAP Notes

498179 Enable Monitoring of InQMy/SAP J2EE Engine
451166: SAPOSCOL: Monitoring processes
639786 TREX 6.0 Central Config & Alerting
637124 TREX 6.0: Check of Heart Beat by using GRMG
For a list of the most important SAP Notes about the monitoring architecture, see:
http://service.sap.com/~sapidb/011000358700008149502002E
Useful SAP Tutors

Name Language Link
E-Mail-Versand als Autoreaktions- Deutsch http://service.sap.com/~sapidb/01100035
methode konfigurieren 8700000785922003D
Configuring the Sending of E-Mails as English http://service.sap.com/~sapidb/01100035
an Auto-Reaction 8700000785922003E
Installation, Registrierung und Deutsch http://service.sap.com/~sapidb/01100035
Customizing von CCMS-Agenten 8700003043352003D
Installation, Registration, and English http://service.sap.com/~sapidb/01100035
Customizing of CCMS Agents 8700003043352003E
Verfgbarkeitsberwachung und Deutsch http://service.sap.com/~sapidb/01100035
CCMSPING 8700003645502003D
Availability Monitoring and CCMSPING English http://service.sap.com/~sapidb/01100035
8700003645502003E
Components in the CSN

BC-CCM-MON SAPOSCOL, SAPCCMSR, RZ20
EP-BC Portal Availability Monitoring, Central Configurations
BC-JAS-ADM J2EE Monitoring
EP-SYS-SPT Single Activity Trace
BC-SEC Security
XX-SER-TCC-EP this document
Example dev_proc
$PROC
#SAPOSCOL Operating system resources
*saposcol*
#SAP Agent
*sapccmsr*
#J2EE-Prozesse
*SVR1* j2eeadm
*SVR2* j2eeadm
*DIS* j2eeadm
2004 SAP AG
#oracle#
*ora_arc0* oraep0
*ora_arc1* oraep0
*ora_lgwr* oraep0
*ora_chpt* oraep0
*ora_smon* oraep0
*ora_pmon* oraep0
*ora_dbw0* oraep0
*ora_reco* oraep0
Example j2ee.pf
SAPLOCALHOST=ep-prod-02
alert/MONI_SEGM_SIZE=64000000
ipc/shm_permission_1008=760
Example oscolfile.ini
#Monitor Filesystems MTE_CLASS Attribute_Group
MonitorFilesystem / CL_FS_EP GR_FS_EP

MonitorFilesystem /var CL_FS_EP GR_FS_EP
MonitorFilesystem /dbarchive CL_FS_EP GR_FS_EP
MonitorFilesystem /oracle/EP0 CL_FS_EP GR_FS_EP
MonitorFilesystem /usr/sap CL_FS_EP GR_FS_EP
MonitorFilesystem /oracle/EP1 CL_FS_EP GR_FS_EP
# Process Configuration MTE_CLASS Attribute_Group

MonitorProcess *saposcol* CL_PS_OS GR_PS_OS
MonitorProcess *sapccmsr* CL_PS_OS GR_PS_OS
MonitorProcess *SVR1* CL_PS_JA CG_PS_JA
MonitorProcess *DSP* CL_PS_JA CG_PS_JA
MonitorProcess *ora_arc0* CL_PS_OR CL_PS_OR
MonitorProcess *ora_arc1* CL_PS_OR CL_PS_OR
MonitorProcess *ora_lgwr* CL_PS_OR CL_PS_OR
MonitorProcess *ora_chpt* CL_PS_OR CL_PS_OR
MonitorProcess *ora_smon* CL_PS_OR CL_PS_OR
MonitorProcess *ora_pmon* CL_PS_OR CL_PS_OR
MonitorProcess *ora_dbw0* CL_PS_OR CL_PS_OR
MonitorProcess *ora_reco* CL_PS_OR CL_PS_OR
MonitorProcess *tnslnr* CL_PS_OR CL_PS_OR
Example sapccmsr.ini
### Format of entries for plugins:
# PlugIn <full path of shared library to load>
PlugIn /usr/sap/tmp/sapccmsr/trexmon.so
###
###
### Format of entries for logfile monitoring:
###
LogFile /usr/sap/ccms/ccms_monitoring/templates/j2ee_engine/ALERT/dr-39-log.ini
LogFile /usr/sap/ccms/ccms_monitoring/templates/j2ee_engine/ALERT/sr-1-log.ini
LogFile /usr/sap/ccms/ccms_monitoring/templates/j2ee_engine/ALERT/s2-1-log.ini
2004 SAP AG
LogFile /usr/sap/ccms/ccms_monitoring/templates/j2ee_engine/ERROR/dr-29-log.ini
LogFile /usr/sap/ccms/ccms_monitoring/templates/j2ee_engine/ERROR/sr-3-log.ini
LogFile /usr/sap/ccms/ccms_monitoring/templates/j2ee_engine/ERROR/s2-3-log.ini
LogFile /usr/sap/ccms/ccms_monitoring/templates/j2ee_engine/J2ee_error_log.ini
LogFile /usr/sap/ccms/ccms_monitoring/templates/j2ee_engine/J2ee_output_log.ini
LogFile /usr/sap/ccms/ccms_monitoring/templates/j2ee_applications/1063701432204logmon.ini
###
### Format of entries for the option to delete trees if no corresponding logfile exists:
### This Parameter is optional, if not specified the tree still remains
LogFileParam DelTree
###
###
2004 SAP AG
### Format of entries for mechanism to filter out SAPOSCOL values:

OsColFile /usr/sap/tmp/sapccmsr/oscolfile.ini
#
###
Example J2ee_error_log.ini
LOGFILE_TEMPLATE
DIRECTORY="/usr/sap/EP/j2ee/j2ee_00/cluster/dispatcher/managers/console_logs/"
FILENAME="*error.log"
MTE_CLASS="J2EE Error Log P"
PREFIX="J2EE D1- "
SHOWLINES=1
SHOWNEWLINES=1
MONITOR_NEWEST_FILES=1
PATTERN_0="Fatal"
VALUE_0=RED
PATTERN_1="Error"
VALUE_1=RED
PATTERN_2="Exception"
VALUE_2=YELLOW
PATTERN_3="Warning"
VALUE_3=YELLOW
.
Example J2ee _output_log.ini

LOGFILE_TEMPLATE
DIRECTORY="/usr/sap/PORTAL/j2ee/j2ee_00/cluster/dispatcher/managers/console_log
s/"
FILENAME="*output.log"
MTE_CLASS="J2EE Output Log P"
PREFIX="J2EE D1- "
SHOWLINES=1
SHOWNEWLINES=1
PATTERN_0="Fatal"
VALUE_0=RED
PATTERN_1="Error"
VALUE_1=RED
PATTERN_2="Exception"
VALUE_2=YELLOW
PATTERN_3="Warning"
VALUE_3=YELLOW
.
Example J2ee_procmon.ini
LOGFILE_TEMPLATE
DIRECTORY="/usr/sap/trans/log/"
FILENAME="check_portal_proc_P2PORTAL.log"
MTE_CLASS="J2EE Proc P"
PREFIX="Proc - "
SHOWLINES=1
SHOWNEWLINES=1
PATTERN_0="D1 DOWN"
VALUE_0=RED
PATTERN_1="S1 DOWN"
VALUE_1=YELLOW
2004 SAP AG
PATTERN_2="S2 DOWN"
VALUE_2=YELLOW
PATTERN_3="S3 DOWN"
VALUE_3=YELLOW
PATTERN_4="no SVR running"
VALUE_4=RED
PATTERN_5="M1 UP"
VALUE_5=GREEN
.
Example J2ee_alert_log.ini
LOGFILE_TEMPLATE
DIRECTORY="/usr/sap/P2PORTAL/j2ee/j2ee_00/cluster/server/managers/log"
FILENAME="ALERT.log"
MTE_CLASS="J2EE Alert Log P"
PREFIX="J2EE S1- "
SHOWLINES=1
SHOWNEWLINES=1
PATTERN_0="ALERT"
VALUE_0=RED
.
Example J2ee_critical_log.ini
LOGFILE_TEMPLATE
DIRECTORY="/usr/sap/P2PORTAL/j2ee/j2ee_00/cluster/server/managers/log"
FILENAME="CRITICAL.log"
MTE_CLASS="J2EE Critical Log P"
PREFIX="J2EE S1- "
SHOWLINES=1
SHOWNEWLINES=1
PATTERN_0="CRITICAL"
VALUE_0=RED
.
Example J2ee_ermergency.ini
LOGFILE_TEMPLATE
DIRECTORY=/usr/sap/P2PORTAL/j2ee/j2ee_00/cluster/server/managers/log/
FILENAME="EMERGENCY.log"
MTE_CLASS="J2EE Emergency Log P"
PREFIX="J2EE S1- "
SHOWLINES=1
SHOWNEWLINES=1
PATTERN_0="EMERGENCY"
VALUE_0=RED
.
Example J2ee_http_alert_log.ini
LOGFILE_TEMPLATE
DIRECTORY="/usr/sap/P2PORTAL/j2ee/j2ee_00/cluster/server/services/http/log"
FILENAME="ALERT.log"
MTE_CLASS="J2EE Http Alert Log P"
PREFIX="http S1- "
SHOWLINES=1
SHOWNEWLINES=1
2004 SAP AG
PATTERN_0="ALERT"
VALUE_0=RED
.
Example J2ee_http_critical_log.ini
LOGFILE_TEMPLATE
FILENAME="CRITICAL.log"
MTE_CLASS="J2EE Http Critical Log P"
PREFIX="http S1- "
SHOWLINES=1
SHOWNEWLINES=1
PATTERN_0="CRITITCAL"
VALUE_0=RED
.
Example J2ee_http_emergency_log.ini
LOGFILE_TEMPLATE
FILENAME="EMERGENCY.log"
MTE_CLASS="J2EE Http Energency Log"
PREFIX="http S1- "
SHOWLINES=1
SHOWNEWLINES=1
PATTERN_0="EMERGENCY"
VALUE_0=RED
.
Example pcd_log.ini
LOGFILE_TEMPLATE
DIRECTORY="/usr/sap/P2PORTAL/j2ee/j2ee_00/cluster/server/services/servlet_jsp/w
ork/jspTemp/irj/root/WEB-INF/portal/logs"
FILENAME="pcd.log"
MTE_CLASS="Pcd Log P"
PREFIX="PRT S1- "
SHOWLINES=1
SHOWNEWLINES=1
PATTERN_0="Fatal"
VALUE_0=RED
PATTERN_1="Error"
VALUE_1=RED
.
Example Portal_log.ini
LOGFILE_TEMPLATE
FILENAME="portal.log"
MTE_CLASS="Portal Log P"
PREFIX="PRT S1- "
SHOWLINES=1
SHOWNEWLINES=1
PATTERN_0="Fatal"
2004 SAP AG
VALUE_0=RED
PATTERN_1="Error"
VALUE_1=RED
.
Example Service_log.ini
LOGFILE_TEMPLATE
FILENAME="service.log"
MTE_CLASS="Service Log P"
PREFIX="PRT S1- "
SHOWLINES=1
SHOWNEWLINES=1
PATTERN_0="Fatal"
VALUE_0=RED
PATTERN_1="Error"
VALUE_1=RED
.
Example Usermanagement_log.ini
LOGFILE_TEMPLATE
FILENAME="usermanagement.log"
MTE_CLASS="UM Log P"
PREFIX="PRT S1- "
SHOWLINES=1
SHOWNEWLINES=1
PATTERN_0="Fatal"
VALUE_0=RED
PATTERN_1="Error"
VALUE_1=RED
.
Example Oracle_alertlog.ini
LOGFILE_TEMPLATE
DIRECTORY="/oracle/K2P/saptrace/background/"
FILENAME="alert_K2P.log"
MTE_CLASS="Oracle Alert Log K"
PREFIX="Oracle- "
SHOWLINES=1
SHOWNEWLINES=1
PATTERN_0="checkpoint not complete"
VALUE_0=RED
PATTERN_1="ORA-"
VALUE_1=RED
.
Example grmgRequestCust.xml



<scentype>URL</scentype>

<scenstarturl>http://us7202:8080/irj/servlet/prt/portal/prtroot/com.sap.portal.
heartbeats.PortalHeartbeat?j_user=user&j_password=password&login_submit
=off</scenstarturl>
<scentexts>
2004 SAP AG
<scentext>
<scendesc>EP_Heartbeat_n1 </scendesc>
</scentext>
</scentexts>
<components>
<component>
<compname>Cluster</compname>
<compversion>001</compversion>
<comptype>Unknown</comptype>
<comptexts>
<comptext>
<complangu>EN</complangu>
<compdesc>Component_Cluster</compdesc>
</comptext>
</comptexts>

<properties>
<property>
<propname>text</propname>
<propvalue>y</propvalue>
</property>
</properties>
</component>
<component>
<compname>TestSAP</compname>
<comptexts>
<comptext>
<compdesc>Component_TestSAP</compdesc>
</comptext>
</comptexts>

<properties>
<property>
<propname>SAPClient</propname>
<propvalue>001</propvalue>
</property>
<property>
<propname>userid</propname>
<propvalue>user_name</propvalue>
</property>
<property>
<propname>password</propname>
<propvalue>user_password</propvalue>
</property>
<property>
<propname>language</propname>
<propvalue>DE</propvalue>
</property>
<property>
<propname>host_name</propname>
<propvalue>csnmain.wdf.sap.corp</propvalue>
</property>
<property>
<propname>system_number</propname>
<propvalue>24</propvalue>
</property>
</properties>
2004 SAP AG
</component>
<component>
<compname>TestWeb</compname>
<comptexts>
<comptext>
<compdesc>Component_TestWeb</compdesc>
</comptext>
</comptexts>

<properties>
<property>
<propname>url</propname>
<propvalue>http://us7202:8080/irj/portalapps/com.sap.portal.heartbeats/html/hea
rtbeat.html</propvalue>
</property>
</properties>
</component>
</components>
</scenario>
</scenarios>
</customizing>
2004 SAP AG
2004 SAP AG
Example list of J2EE Engine log files
Please know that the actual console logs are changing their name at every startup of the J2EE Engine.
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/console_logs/2003_9_16_at_9_38_53_output.log
SAPJLog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/console_logs/2003_9_16_at_9_38_53_error.log
SAPJLog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/hs_err_pid20556.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/config.0.trc SAPJLog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/ccms_jmon.trc SAPJLog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/ccms_agent.trc SAPJLog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/tools/ccms_jmon.trc SAPJLog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/dev_rfc.trc ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/log/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/r3startup/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/thread/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/thread/WARNING.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/timeout/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/memory/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/INFO.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/connections/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/cluster/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/classloader/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/ports/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/ports/WARNING.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/lock/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/lock/WARNING.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/service/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/ERROR.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/ALERT.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/managers/log/EMERGENCY.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/log/work/DEFAULT.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/log/work/DEFAULTCRITICAL.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/log/work/EMERGENCY.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/log/work/ALERT.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/log/work/CRITICAL.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/log/work/ERROR.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/log/work/WARNING.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/log/work/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/log/work/INFO.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/monitor/log/INFO.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/r3startup/log/CRITICAL.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/r3startup/log/EMERGENCY.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/r3startup/log/ALERT.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/r3startup/log/ERROR.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/r3startup/log/WARNING.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/r3startup/log/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/dispatcher/services/r3startup/log/INFO.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/ejb/log/CRITICAL.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/ejb/log/EMERGENCY.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/ejb/log/ALERT.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/ejb/log/ERROR.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/ejb/log/WARNING.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/ejb/log/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/ejb/log/INFO.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/log/work/DEFAULT.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/log/work/DEFAULTCRITICAL.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/log/work/EMERGENCY.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/log/work/ALERT.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/log/work/CRITICAL.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/log/work/ERROR.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/log/work/WARNING.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/log/work/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/log/work/INFO.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/monitor/log/INFO.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/ts/log/CRITICAL.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/ts/log/EMERGENCY.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/ts/log/ALERT.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/ts/log/ERROR.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/ts/log/WARNING.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/ts/log/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/ts/log/INFO.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/http/log/CRITICAL.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/http/log/EMERGENCY.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/http/log/ALERT.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/http/log/ERROR.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/http/log/WARNING.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/http/log/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/http/log/INFO.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/http/log/http.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/PRTBridge/log/Critical.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/PRTBridge/log/Emergency.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/PRTBridge/log/Alert.log ASCIILog
2004 SAP AG
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/PRTBridge/log/Error.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/PRTBridge/log/Warning.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/PRTBridge/log/Notice.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/PRTBridge/log/Info.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/log/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/thread/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/thread/INFO.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/thread/WARNING.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/timeout/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/memory/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/INFO.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/cluster/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/classloader/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/swap/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/lock/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/lock/WARNING.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/r3startup/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/service/NOTICE.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/WARNING.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/ERROR.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/EMERGENCY.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/managers/log/ALERT.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/log/system.log SAPJLog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/logviewer_server.log SAPJLog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/hs_err_pid20556.log ASCIILog
Example list of portal application log files

localhost 4444 localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/ccms_agent.trc=localhost 4444
/usr/sap/ccms/ccms_monitoring/templates/j2ee_applications/1063701432187logmon.ini
localhost 4444 localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/logviewer_server.log ASCIILog
localhost 4444 localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/dsm.log
ASCIILog
localhost 4444 localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-
INF/portal/logs/collaboration.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/pageBuilder.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/usermanagement.log
ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/./services/servlet_jsp/work/jspTemp/irj/root/WEB-
INF/portal/logs/knowledgemanagement.*.txt * ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/http.log ASCIILog
2004 SAP AG
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-
INF/portal/logs/com.sapportals.portal.design.StyleService.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/unification.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/TestAPI.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/umWebService.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/portal.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/debug.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/diagnostic.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/JSPLogAnalyser.log
ASCIILog
INF/portal/logs/com.sapportals.portal.design.StyleEditor.log ASCIILog
INF/portal/logs/com.sapportals.portal.design.StyleArchive.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/acl.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/pcdadmintools.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/sapapplication.log
ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/config.*.trc*
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/service.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/notification.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/dynamic.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/JCOClientPool.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/iview.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/transport.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/monitor.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/yahoo.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/pcdeditor.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/jsp.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/ccms_jmon.trc
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/locking.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/iviewserver.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/soap.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/appdesigner.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/generic_creator.log
ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/pcd.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs/navigation.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/log/default.trc ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/log/system.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/sapum.log ASCIILog
localhost 4444 /usr/sap/EP0dir/j2ee/j2ee_00/cluster/server/log/applications.log ASCIILog
2004 SAP AG
TREX Monitoring ini files
DaemonWatch.ini
LOGFILE_TEMPLATE
DIRECTORY="/usr/sap/TREX_6/trace"
FILENAME="TrexDaemon.*.trc"
MONITOR_FILESIZE_KB=0
MTE_CLASS="TRexDaemon"
PREFIX="TRex: "
RESCANFROMBEGIN=0
SHOWNEWLINES=1
PATTERN_0=" w "
CMP_FROM_BEGIN_0=0
#MESSAGECLASS_0="SAP-T100"
MESSAGEID_0="RT 999"
SEVERITY_0=0
VALUE_0=YELLOW
PATTERN_1=" e "
CMP_FROM_BEGIN_1=0
SEVERITY_1=90
VALUE_1=RED
PATTERN_2=" f "
CMP_FROM_BEGIN_1=0
SEVERITY_1=90
VALUE_1=RED
.
IndexServerWatch.ini
LOGFILE_TEMPLATE
FILENAME="TrexIndexServer.*.trc"
MTE_CLASS="TRexIndexServerTrc"
PREFIX="TRex: "
RESCANFROMBEGIN=0
SHOWNEWLINES=1
PATTERN_0=" w "
CMP_FROM_BEGIN_0=0
SEVERITY_0=0
VALUE_0=YELLOW
PATTERN_1=" e "
Best Practice: Enterprise Portal 6.0 SP1 System Landcape Monitoring 119
CMP_FROM_BEGIN_1=0
SEVERITY_1=90
VALUE_1=RED
PATTERN_2=" f "
CMP_FROM_BEGIN_1=0
SEVERITY_1=90
VALUE_1=RED
.
NameServerWatch.ini
LOGFILE_TEMPLATE
FILENAME="TREXNameServer.*.trc"
MTE_CLASS="TREXNameServerTrc"
PREFIX="TRex: "
RESCANFROMBEGIN=0
SHOWNEWLINES=1
PATTERN_0=" w "
CMP_FROM_BEGIN_0=0
SEVERITY_0=0
VALUE_0=YELLOW
PATTERN_1=" e "
CMP_FROM_BEGIN_1=0
SEVERITY_1=90
VALUE_1=RED
PATTERN_2=" f "
CMP_FROM_BEGIN_1=0
SEVERITY_1=90
VALUE_1=RED
.
PreprocessorWatch.ini
LOGFILE_TEMPLATE
FILENAME="TrexPreprocessor.*.trc"
MTE_CLASS="TRexPreprocessorTrc"
PREFIX="TRex: "
2001 SAP AG
RESCANFROMBEGIN=0
SHOWNEWLINES=1
PATTERN_0=" w "
CMP_FROM_BEGIN_0=0
SEVERITY_0=0
VALUE_0=YELLOW
PATTERN_1=" e "
CMP_FROM_BEGIN_1=0
SEVERITY_1=90
VALUE_1=RED
PATTERN_2=" f "
CMP_FROM_BEGIN_1=0
SEVERITY_1=90
VALUE_1=RED
.
QueueServerWatch.ini
LOGFILE_TEMPLATE
FILENAME="TrexQueueServer.*.trc"
MTE_CLASS="TRexQueueServerTrc"
PREFIX="TRex: "
RESCANFROMBEGIN=0
SHOWNEWLINES=1
PATTERN_0=" w "
CMP_FROM_BEGIN_0=0
SEVERITY_0=0
VALUE_0=YELLOW
PATTERN_1=" e "
CMP_FROM_BEGIN_1=0
SEVERITY_1=90
VALUE_1=RED
PATTERN_2=" f "
CMP_FROM_BEGIN_1=0
SEVERITY_1=90
VALUE_1=RED
.
2001 SAP AG
WebServerWatch.ini
LOGFILE_TEMPLATE
DIRECTORY="/usr/sap/TREX/trace"
FILENAME="TrexWebServer.*.trc"
MTE_CLASS="TRexWebServerTrc"
PREFIX="TRex: "
RESCANFROMBEGIN=0
SHOWNEWLINES=1
PATTERN_0=" w "
CMP_FROM_BEGIN_0=0
SEVERITY_0=0
VALUE_0=YELLOW
PATTERN_1=" e "
CMP_FROM_BEGIN_1=0
SEVERITY_1=90
VALUE_1=RED
PATTERN_2=" f "
CMP_FROM_BEGIN_1=0
SEVERITY_1=90
VALUE_1=RED
.
dev_proc for TREX

$PROC
#SAPOSCOL Operating system resources

*saposcol*
#SAP Agent
*sapccmsr*
#J2EE-Prozesse
*SVR1*
*DSP*
#Trex-Prozesse
*TREXDaemon.*
*TREXFilter.*
*TREXIndexServer.*
*TREXPreprocessor.*
*TREXQueueServer.*
*TREXNameServer.*
2001 SAP AG
Example installed.xml for TREX GRMG



<components>
<component name="IS_01" installed="X">
<property name="HOST" value="us7202"/>
</component>
<component name="QS_01" installed="X">
</component>
</component>
<component name="NS_01" installed="X">
</component>
<component name="WS_01" installed="X">
<property name="URL" value="http://us7202:8353/TREX?CMD=PING"/>
</component>
</components>
Example grmgconfig.xml

<customizing>
<control>
<runlog>X</runlog>
<errorlog>X</errorlog>
</control>
<scenarios>
<scenario>
<scenname>TREX001</scenname>
<scentype>URL </scentype>
<scenstarturl>http://us7201:8366/</scenstarturl>
<scentexts>
<scentext>
<scendesc>TREX on host us7201 </scendesc>
</scentext>
</scentexts>
<components>
<component>
<compname>IS_01</compname>
<comptexts>
<comptext>
<complangu>EN </complangu>
<compdesc>Indexserver </compdesc>
</comptext>
2001 SAP AG
</comptexts>
<properties>
<property>
<propname>foo</propname>
<proptype/>
<propvalue> bar</propvalue>
</property>
</properties>
</component>
<component>
<compname>QS_01</compname>
<comptexts>
<comptext>
<compdesc>QueueServer</compdesc>
</comptext>
</comptexts>
<properties>
<property>
<proptype/>
</property>
</properties>
</component>
<component>
<compname>PP_01</compname>
<comptexts>
<comptext>
<compdesc>PreProcessor </compdesc>
</comptext>
</comptexts>
<properties>
<property>
<proptype/>
</property>
</properties>
</component>
<component>
<compname>NS_01</compname>
<comptexts>
<comptext>
<compdesc>NameServer </compdesc>
</comptext>
</comptexts>
<properties>
<property>
<proptype/>
</property>
</properties>
</component>
2001 SAP AG
<component>
<compname>WS_01</compname>
<comptexts>
<comptext>
<compdesc>WebServer</compdesc>
</comptext>
</comptexts>
<properties>
<property>
<proptype/>
</property>
</properties>
</component>
</components>
</scenario>
</scenarios>
</customizing>
Python HTTP server README

Using the Python http server
------------------------------------------------------------------------
The Python HTTP server is an HTTP server for TREX written entirely in
Python. It uses the server framework built into Python and does not
need one of the big web servers (Apache or IIS) to host it.
Python HTTP server will probably be slower (for some functions) than
the IIS extension delivered with TREX, and it offers less
functionality in some areas. The Python HTTP server may not be
started as a service - startup is only via the command line interface.
The XML syntax of the Python HTTP server is the same as supported by
the TREX IIS extension so that the Python HTTP server may be used as a
replacement for the IIS extension, if, for some reason the IIS
extension can not be used. There are currently no security features
built into Python HTTP server.
There are logging features, mainly for debugging, available in the

Python HTTP server that are not available elsewhere.
1. You can log the XML requests and the XML responses to stdout
(options --logRequest, --logResponse)
2. You can create a log file with a Python script for each operation
performed by the HTTP server. Theses scripts can later be used to
reproduce errors without having to use the software that generated the
XML request (option --logFile=)
3. You can print the (ims_search_api) API calls executed in response

to an XML request to stdout, either to better understand the API or to
debug the HTTP server it self (option --log)
The Python http server may be extended very easily. Implementing a

new call is usually done in less than an hour, after the underlying API
is implemented in Python.
The operation of the Python HTTP server is entirely stateless. You

have to specify the HTTP port number and all other parameters on the
2001 SAP AG
command line when you start up the server. There is no configuration

file to remember settings.
To start up the server on port 8000, type the command
indexServer.py 8000
To stop the server, type the command (in another window on the same
machine):
stopServer.py 8000
To get information about the options type:
indexServer.py --help
Feedback and Questions

Send any feedback by formulating an SAP customer message to component SV-GST-SMC. You can do this at
http://service.sap.com/message.
Copyright 2004 SAP AG. 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 AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of
Microsoft Corporation.
IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390, AS/400, OS/390, and OS/400 are
registered trademarks of IBM Corporation.
ORACLE is a registered trademark of ORACLE Corporation.
TM
INFORMIX-OnLine for SAP and Informix Dynamic Server are registered trademarks of Informix Software Incorporated.

UNIX , X/Open , OSF/1 , and Motif are registered trademarks of the Open Group.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts
Institute of Technology.
JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used
under license for technology invented and implemented by Netscape.
SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,
Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several
other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.
Disclaimer: SAP AG assumes no responsibility for errors or omissions in these materials. These materials are provided as is without a
warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may
result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other
items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained
in these materials and does not endorse your use of third party Web pages nor provide any warranty whatsoever relating to third party Web
pages.
2001 SAP AG

Enterprise Portal 6.0 SP1

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Enterprise Portal 6.0 SP1

Transféré par

Droits d'auteur :

Formats disponibles

Enterprise Portal 6.

Best Practice for Solution Management

Applicability, Goals, and Requirements

Staff and Skills Requirements

Duration and Timing

Best Practice Procedure and Verification

Important: Using this document

Example Monitoring Set

SAP Enterprise Portal Overview

SAP Enterprise Portal Architecture

Short Description of the Monitoring and Supportability

Advantages of central log file monitoring and alerts:

Single Activity Trace

Importing a Transport Request into the Central

CATT process for creating CSMREG

Post Processing in Client 000 in CEN

Start transaction SCAT by entering /nscat in the command field.

Installing and Configuring the Monitoring

Usage of virtual and physical memory

Process of the automated installation:

Switch to directory moni_temp.

(be sure that the script is executable - chmod a+x install_root.sh)

(make sure that the script is executable)

Parameter Name Description

Data for the central monitoring system

$SID$ System ID of the central monitoring system

$CEN_HOST$ Host name of an application server in CEN

$INSTANCE_NUMBER System number of CEN

$CLIENT$ Client in CEN, in which the user exists

$USER$ User with administrator authorization

$PASSWD$ Associated password.

$CLIENT$ Client in CEN, in which the user exists

$USER_CSMREG$ Name of the user

$PASSWD$ Associated password.

Check file sapccmsr.install.log in the current directory for errors.

Further Information SAPCCMSR

Process for alternative manual installation of the

mkdir /usr/sap/tmp (if not already exist)

chown R j2eeadm:sapsys /usr/sap/ccms

chown R j2eeadm:sapsys /usr/sap/tmp

Download the files into a directory for example /usr/sap/ccms/32bit.

Check the unpacked files via command ls ltr

Remove all unpacked files except sapccmsr:

Copy file sapccmsr into directory /usr/sap/bin/ccms.

Check file sapccmsr.install.log in the current directory for any errors.

Option: dialog free SAPCCMSR Registration

CEN_CSMREG_SYSNR=<instance no. of monitoring R/3 system>

Option: Starting the SAPCCMSR agent

Troubleshooting Shared Memory Segment properties

- --rw-rw---- write permission to the group

edit this file

Add the following lines

Further information SAPOsCol

Copy the new SAPOsCol version to /usr/sap/ccms/bin.

chmod 4755 saposcol

Make sure the binary is executable.

Start the SAPOsCol as root by entering

Giving the java processes an identifier for SAPOsCol

Configuration of SAPOsCol by editing dev_proc

The file dev_proc has the following structure:

Filtering Processes and Rile Systems reported by

Starting and Stopping SAPOsCol

Checking the version of the jmonapi.jar

Some Unix derivates / shell need the option print.