UCON CCMS Monitoring: Functions

Detailed information for monitoring UCON processes in the CCMS Monitor (transaction RZ20).

In the following section you find a detailed description of the functions of the UCON CCMS Monitoring that are available in the central CCMS Monitor (transaction RZ20). The individual monitoring functions are shown in the following navigation nodes:

  • Prerequisites
  • Worklist for UCON Phase Tool
  • Transport Status of Phase Assignments
  • Status of Runtime and Design Time
  • Status of Batch Jobs

Prerequisites

The prerequisites for the execution of the UCON CCMS Monitoring can be divided into two categories:

  • System-wide prerequisites (valid for all SAP clients (client-independent) and all application servers)
  • Client-dependent prerequisites

    System-Wide Settings

    • Profile Parameter Settings: Node Profile Param. Status of Appl. Servers shows the value of the profile parameter on the available application servers in your ABAP system. SAP recommends setting the value of the profile parameter ucon/rfc/active for all application servers to value 1 (UCON RFC is active) in order to make it possible to set up the UCON RFC. If the value of profile parameter ucon/rfc/active does not have the same value on all application servers, those application servers with different settings are displayed.

      The application server has a different setting here:

  • Profile Parameter Settings
    • Default Communication Assembly (CA): The setting of the Communication Assembly(CA) as client-independent attribute is monitored under the node Default Communication Assembly (CA). You can also see the status of the CA setup in your ABAP system. If you configure a CA in your ABAP system and the Default CA is missing, you can double-click the node Default Communication Assembly Status and have the Default CAconfigured.
    • Exceeding No. of RFC Sub Records: The RFC log status is displayed here. UCON RFC uses the information using all called RFC-enabled function modules on the basis of statistical data records. In certain cases it is however possible that not all RFC calls are collected in the statistics data. This can be the case if the value of the profile parameter stat/rfcrecs is less than the number of called RFCs. In this case you must adjust the value of the profile parameter accordingly.
    Client-Specific Settings

    Client-dependent settings contain the monitoring data using client-specific attributes for UCON RFC such as CA Config (CA and Virtual Host are linked here with each other in UCON RFC) and the virtual host itself.

    The following diagram shows an overview of the settings in the CCMS Monitor:

Client-Specific Settings

Worklist for UCON Phase Tool

This node delivers you the necessary information about the status transitions in transaction UCONPHTL and informs you about the number of RFC-enabled function modules in the individual UCON phases.

The monitor attribute RFMs with Expired Logging Phase informs you about the number of RFC modules that can be transferred from the logging phase to the evaluation phase.

By double-clicking on the node under Worklist for UCON Phase Tool you can navigate directly to transaction UCONPHTL a get detailed information about the RFC modules and their statuses.

The monitor attribute Rejected Calls in UCON Phase Tool displays a list with RFC modules that

  • were transferred to the UCON Phase Active
  • were called externally (by another ABAP system, an external connector, or another SAP client of the same ABAP system)
  • were not yet assigned to a certain CA

With this information you can find out the case for rejected RFC modules without time-consuming analyses.

The node Attributes of Rejected Calls in Syslog shows additional information about a rejection. If the call of an RFC module was rejected by the RFC server, you find a syslog entry (transaction SM21) under Message ID URA. Node Attributes of Rejected Calls in Syslog in the CCMS Monitor shows exactly this syslog entry.

The following graphic shows the monitoring attributes for Worklist for UCON Phase Tool:

Worklist for UCON Phase Tool

Transport Status of Phase Assignments

The UCON RFC framework creates a status object for every RFC function module. Since the status creation and creation of a transport object can lead to an error message, the UCON RFC Monitor provides a node with which you can administer the transport status.

In the case of errors, you are requested to navigate to transaction UCONPHTL and solve the problem.

Transport Status of Phase Assignments

Status of Runtime and Design Time

Since it is very time-intensive to read data from tables from the development environment (unbuffered database tables), runtime tables have been introduced that are better buffered.

These runtime tables must be synchronous with the tables of the development environment. If this is not the case, the UCON CCMS Monitor informs you about existing problems and offers relevant solutions.

The following graphic shows the node Status of Runtime and Design Time:

Status of Runtime and Design Time

Status of Batch Jobs

Creating external RFC calls for assigning a certain UCON phase must be permanently monitored. UCON RFC CCMS therefore offers a view of its own for monitoring the standard batch job SAP_UCON_STATISTIC_RECORDS.

SAP_UCON_STATISTIC_RECORDS starts a program that creates external RFC modules. On the basis of the data that was created you can assign the RFC modules in transaction UCONPHTL to a UCON-specific phase and this way make your system safe for RFC calls..

Status of Batch Jobs