Central Monitoring using
the Monitoring Cockpit 
Use
The Monitoring Cockpit provides you with status information and also serves as a navigation platform to access important administration and monitoring tools.
Features
Status information on generation and runtime environment as well as further status information and system settings are displayed in a tree structure. You can expand the nodes of this tree.
The displayed information is updated after a certain period of time. But you can also update the information of an individual node manually.
You can navigate around in various ways.
Activities
You can choose views, update individual nodes and trigger actions.
Detailed information on the updating intervals of the corresponding nodes contain the node properties in the context menu.
The provided activities are described in the following chapters.
Choosing Views
You
can choose the following views and display the view with symbol 
:
· All nodes
· Generation
· Runtime
· System setup
· System settings
Every single view provides a certain selection of information.
You can define a view as a start view for further sessions. Furthermore, you can save the expanded hierarchy representation of the selected view.
Updating the Status of a Node
Traffic lights indicate the status of the individual entries. The field in the right-hand column contains date and time of the last status determination.
You can update the status of a node by selecting the corresponding node and choosing Refresh immediately in the context menu (not available with the WebGUI).
An additional scheduled status determination will be carried out at the current time.
Note that several nodes are reference nodes.
Displaying Details and Triggering Actions
Double-click on a line to get to the detail display. In the detail display you can trigger further actions.
For example, you can regenerate runtime objects for BDoc types that were faulty or you can stop queues.
The status information is contained under the following main nodes:
· Generation details:
Here you can find details of generated objects.
See the following topics for further details:
Checking the Syntax of the Generated Function Groups
Displaying Status Information for Repository Objects
· Runtime Information:
See the following topics for further details:
Note the following explanations on Adapter status details:
· The details of R/3 backend outbound queues represent a consolidated view of all outbound queues of connected R/3 back-end systems.
Keep in mind the following explanations on the parameters under Adapter status details:
· CRMRFCPAR in R/3 back-end systems
The Parameter File CRMRFCPAR is the RFC parameter file on the R/3 backend side.
You will get an evaluation of the parameters entered here:
- Number of parameters in all the connected R/3 back-end systems.
- Existence of CRM standard values for unlimited data transfer (parameter 0BJ and DOWNLOAD: default value *). These default values must be available for all the connected R/3 back-end systems. Otherwise you will receive a warning in the form of a yellow traffic light.
- XML support (default value *)
- Use of RFC inbound queues on the CRM server (default value *)
· CRMPAROLTP
Although this parameter file is evaluated, it is normally no longer used.The RFC-relevant parameters have been transferred to CRMRFCPAR.
· System settings:
This node contains the number of sites for every site type.
Sites are CRM components that receive or send data via CRM Middleware.
To connect SAP components there are a range of standard site types available (CRM, CDB, Mobile Client and R/3). For more information about creating sites see the Administration Console.
One or more sites may be available for the site type R/3. Only one site may exist for each site type CRM and CDB. Otherwise a yellow traffic light is displayed. For more information on site types see Site Types.
· Monitoring Tools / Statistics
This node contains several statistics and the status of the alert monitoring.
· Background Jobs:
This node provides an overview over all background jobs.