Prerequisites/Settings for Displaying J2EE
DSR/Traces in the CCMS
Before you can display Distributed Statistics Records (DSRs) and performance trace data of the J2EE Engine in CCMS, they must run through a number of stations, as shown in the figure below:
For an exact description of the route that DSRs and performance traces follow to their display in the CCMS, see Displaying DSRs/Performance Traces of the J2EE Engine in CCMS.
The following prerequisites must be fulfilled so that the data reaches its target:
· Your central CCMS monitoring system must be a SAP Web Application Server ABAP 6.40.
·
You must have
installed, registered, and activated the SAPCCMSR agent with the –J2EE
option. For more information, see
Installing an Agent on
a Java Instance (Java Standalone System) or
Installing an Agent on
a Java Instance (Double-Stack System).
· The DSR service of the J2EE Engine must be active.
By default, the DSR service is already active. For information about starting the service if it was deactivated, see the documentation for the Visual Administrator.
· To display DSR aggregates using the Global Workload Monitor (transaction ST03G), the DSR collector must be active and collect data for aggregation hourly.
For
information about maintaining the collector and the collector database, see
Control Functions
of the Global Workload Monitor, such as:
¡ Displaying and deleting contents of the Collector Database (DSR Performance Database)
¡ Reorganizing the Collector Database
¡ Displaying and storing collector logs
¡
Controlling
collectors, where the following
Parameters for Controlling the DSR
Collector are
available:
§ Parameters to determine whether the preaggregation should be performed by the agent or by the collector.
If the load on the agent’s host is too high, you can have the preaggregate generated by the collector.
§ Parameter to define the maximum number of statistics records that the collector can process per run. The default value is 20000.
§ Parameter to set the retention period of the collector logs. The default value is 14 days.
§ Parameter to define the retention period of the statistics files on the J2EE Engine.
However, the value for the J2EE Engine is set to 24 hours and cannot be changed.
§ Parameter to set the type of statistics generation; that is, which aggregations should be created. You can deactivate individual aggregates separately, which reduces the runtime of the collector and the memory requirement of the performance database.
You cannot assume that the component is not available because the statistics records are not available in the Global Workload Monitor. There are diverse, critical and non-critical reasons for the lack of data, such as
§ There are no requests at the component
§ Statistics collection is deactivated
§ The file system has become full