Basis Displaying the Technical View: Status Autoreaction CCMS
Posted by
Admin at
|
Share this post:
|
|
In the monitoring architecture, you can react automatically to an alert using auto-reaction methods. These methods are automatically started in the case of an alert and by default are executed in the system in which the alert occurs. Almost no assignments are made in the standard SAP system; however, there are several predefined auto-reaction methods in the monitoring architecture that you can assign to any MTE classes.
As of SAP Web Application Server 6.10, you can also define central auto-reaction methods. The auto-reaction methods are not started in the system, in which the alert occurs, but rather in the central monitoring system. In this way, it is possible for reactions to events that occur in monitored components to be performed immediately in a central location.
If problems occur during the execution of auto-reaction methods, it can be useful to check the status of the auto-reaction methods. You can find out the definition and runtime status of an MTE by choosing Display Details (
In this technical view, you can also manually start the auto-reaction method for any MTE to which an auto-reaction method is assigned. To do this, choose the relevant MTE by double clicking it. This is especially useful during test phases.
Note that when you start an auto-reaction method manually, it runs under your user name and therefore also under your authorizations. As the method runs under the SAPSYS user when it is started automatically, and this user has only very few authorizations, you can assume from a successful test with a manual start that the method will also run without problems during normal operation.
Procedure
To activate the Status Autoreaction technical view, follow the procedure below:
...
1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.
2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.
3. Choose Views ® Status Autoreaction. The alert tree now no longer displays the alert status and reported values, but information about the auto-reaction methods of the MTEs of the monitor.
Result
The view displays the following information for the active monitor about the auto-reaction methods that are assigned to the individual MTEs:
· Assigned auto-reaction method
· Type of the auto-reaction method; depending on the definition of the method, the following types are possible:
| Type | Description |
| [Central Autoreaction] | The method is defined as a central auto-reaction method. |
| [Running in Autoabap] | The method is executed in the dialog process. |
| [Running in Background] | The method is executed in the background process as a job. |
| [???] | The method type is not yet known; this type is only displayed for a short type after the method is created. |
· Definition status of the method:
| Type | Description |
| PRESET | The method has just been created; the properties of the method are still determined by the settings in the data supplier. After a maximum of five minutes, the system reads the current settings of the method from the active properties variant and the definition status is changed. |
| DBSET | The settings of the active properties variant are already included in the properties of the method in this status. However, as it is not in the CHECKED definition status, you should check whether the method is released as an auto-reaction method. |
| CHECKED | The method is released and can therefore be executed as a local auto-reaction method. |
| CEN_CHECKED | The method is released as a central auto-reaction method. |
· Runtime status of the method:
| Type | Description |
| Ready | The method is ready for the next execution; however, this is not yet due. |
| Run required | The method is to be executed, however the responsible dispatcher has not yet started the method. |
| Running | The method is currently running; the color of the corresponding attribute is yellow. |
| Error | An error occurred during the last run of the method. The difference between the two statuses is that a method in the status Error is started again at the next scheduled run, a method in the status Fatal Error is not. A method in the status Fatal Error is only started again after a warm start of the monitoring segment (see Resetting the Segment to WARMUP Status). The color of the corresponding attribute is red. You can also reset the method status by selecting the corresponding MTE, choosing Display Details ( |
· The time specification after the runtime status shows the time since which the method has been in this status.
· The color of the nodes is not passed upward in the alert monitoring tree. Monitoring objects and summary nodes therefore always have the color Green.
Keyword: BASIS
Title : Basis Displaying the Technical View: Status Autoreaction CCMS
