Monitoring TREX with CCMS

Use

You can use the monitoring functions of CCMS (Computing Center Management System) to monitor Search and Classification (TREX). This documentation describes how to configure and use the monitoring functions.

This graphic is explained in the accompanying text

For more information about CCMS, see Monitoring in the CCMS.

After the TREX installation, all files and directories that you require for the correct operation of CCMS and GRMG are available on your host: The SAPCCMSR CCMS agent and the DSRLIB library (name extensions depend on the platform). These files are located in the <TREX_DIR>/exe directory.

This graphic is explained in the accompanying text

The TREX admin tool (stand-alone) also provides a monitoring function for monitoring processes, errors, and alerts. The TREX alert server regularly checks central TREX functions and can notify you by e-mail of the system status in the event of an error or incorrect configuration. This information is also visible via CCMS.

Prerequisites: TREX 7.1 in NetWeaver 7.0

This documentation describes the monitoring of a TREX 7.1 system used with SAP NetWeaver 7.0. To use TREX 7.1 monitoring functions in NetWeaver 7.0, you have to configure and start the sapccmsr agent. This is a different process when using TREX 7.1 in NetWeaver 7.0 than in NetWeaver 7.1, where the TREX name server collects parameter data and alert reports. Since the sapccmsr agent is not needed if using and installing TREX 7.1 in NetWeaver 7.1 and is therefore not preconfigured, you need to configure it manually if using TREX 7,1 in NetWeaver 7.0. To do so, use the ccms_config.py script.

Features

The following monitoring functions are available:

● Monitoring parameters, availability, log files, and processes

○ Parameter reporting

○ Availability monitoring (Heartbeat/GRMG)

○ Log file monitoring

○ Process monitoring

● Activity tracing

Activity tracing is not part of the CCMS monitoring of TREX. You have to configure activity tracing separately. You monitor activity tracing for TREX using the J2EE Log Viewer.

Naming Conventions

<TREX_DIR>

Installation directory for TREX.

The path to the directory is:

● On UNIX: /usr/sap/<SAPSID>/
TRX<instance_number>

● On Windows: <disk_drive>:\usr\sap\<SAPSID>\
TRX<instance_number>

<TREX_GLOBAL>

Global file system for your TREX installation:

● On UNIX:

<SAPGLOBALHOST>/sapmnt/>SYS/
<sapsid>/profile

For example,

/usr/sap/<SAPSID>/SYS/profile

● On Windows:

<SAPGLOBALHOST>\sapmnt\<SAPSID>\
SYS\profile

For example,

<drive>:\usr\sap\<SAPSID>\
SYS\profile

Instance profile for a TREX instance

The instance profile contains specific information about the runtime environment for a TREX instance.

Path specifications

The forward slash (/) is usually used in path specifications such as <TREX_GLOBAL>/START_TRX<instance_number>_<host>.