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.
After the TREX installation, all files and directories that you require for correct operation of CCMS and GRMG are available on your host: the CCMS agent SAPCCMSR and the DSRLIB library (the name extensions depend on the platform). These files are located in the <TREX_DIR>/exe directory.
The TREX admin tool (standalone) 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 SAP 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 SAP NetWeaver 7.0, you have to configure and start the sapccmsr agent. This is a different process when using TREX 7.1 in SAP NetWeaver 7.0 than in SAP 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 SAP NetWeaver and is therefore not preconfigured, you need to configure it manually if using TREX 7.1 in SAP NetWeaver 7.0. To do so, use the ccms_config.py script.
The following monitoring functions are available:
Monitoring of Parameters, Availability, Log Files, and Processes
Parameter reporting
Monitoring availability (Heartbeat/GRMG)
Monitoring log files
Process monitoring
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.
<TREX_DIR> |
Installation directory for TREX. The path to the directory is:
|
<TREX_GLOBAL> |
Global file system for your TREX installation:
|
<SAPSID>_TRX<instance_number> _<host> |
Instance profile for a TREX instance The instance profile contains specific information about the runtime environment for a TREX instance. |
Paths
The forward slash (/) is usually used in path specifications such as <TREX_GLOBAL>/START_TRX<instance_number>_<host>.