Configuring Properties

You can double-click Configuration in the tree to display system configuration properties and customize the behavior of predefined properties.

The following properties are available:

  • Add system description to alert notification subject: Allows you to add a system description to the alert notification subject of the e-mail. By default, the system description is not added to the e-mail subject.

  • Maximum runtime for execution of collector BG jobs in seconds: Determines the maximum runtime for the execution of collector background (BG) jobs. If the background job runtime reaches this time limit, it is aborted. Default value: 600 seconds

  • Use kill WP for long-running collector BG jobs: Allows you to use the OS-level function Kill Work Process to terminate a collector background job that cannot be aborted with the standard function. It only works if the previous property Maximum runtime for execution of collector BG jobs in seconds is specified. Possible values: X = enabled; <empty> = disabled (default)

  • Kill long-running WP on the remote system: Allows you to check and kill a work process on the remote system that was triggered by a background collector job executed on the central system. When any background collector job is long-running (exceeding the defined maximum runtime threshold) on the central system, this job is automatically terminated. However, in special cases, it does not kill the triggered work process on the remote system. If this property is enabled, it checks whether any long-running work process triggered by the terminated collector job is still running on the remote system and kills this work process automatically.
    By default, this property is disabled because it requires an additional RFC call to the remote system, so the existing functionality is not impacted. If you want to always check for any long-running work processes on the remote system, you can enable this function. Possible values: X = enabled; <empty> = disabled (default)

  • Retention time for background jobs in days: Deletes background jobs periodically to clean the table TBTCO. The property BG_JOB_RETENTION_TIME sets a time condition in days, based on which the system deletes background jobs in the past. Default value: 7 days

  • Priority class for the execution of collector BG jobs: Defines the background job priority class for the execution of collector background jobs. Possible values: C = lowest priority (default); B = medium priority; A = highest priority. If you do not enter a priority class, the priority is the same as the default value C.

  • Server group for executing collector BG jobs: Specifies the name of a server group on which background jobs are executed. You must create the server group via transaction SM61. It determines a specific list of application servers on which background jobs can run. Default value: <empty> (no specific server group is used)

    WARNING If the server group is not defined correctly, i.e. it does not exist in SM61, the execution of collector jobs fails.

  • User ID used for the execution of collector BG jobs: Defines the user ID that is used for the execution of collector jobs. Each execution of collector jobs and all monitoring actions on the central system are performed under this user ID. If a user ID is not defined (default value), the ID of the logon user who triggers the execution of the collector background job is used. If the user ID is not valid, the system displays the following error message: Cannot start a background job! Reason: <user ID> does not exist.

    We recommend creating a system type user on the central monitoring system and setting it up with limited authorizations, which can be defined in the role /DVD/MON_ADMIN.

    If the defined user ID used for the execution of background jobs is deleted, all affected jobs start failing. CrystalBridge® Monitoring can identify these failures and display them by marking the particular row with a red icon in the Collector jobs tab in the CrystalBridge® Monitoring monitor. In addition, affected systems are marked with a red icon in the list of monitored systems.

    NOTE To ensure that collector jobs are executed correctly, it is important that the user ID is not deleted or locked.

  • Name of the cleanup job: Specifies the name of the background job that cleans up all transaction data according to retention dates. The retention date for all collected data is calculated based on the retention time in days that you define in the definition of the collector background job.

    This cleanup job is scheduled and executed only once per day. The starting time of this job depends on the property Starting time of cleanup job. The purpose of this cleanup job is to delete all transaction data that has a retention date older than the date of the cleanup job execution. After you execute this cleanup job, the system will only contain data that fulfills the retention period. 

  • Starting time of clean up: Specifies the starting time of the background job to clean up all transaction data according to retention dates. If you change the starting time to a time that has already passed that day, the cleanup job is rescheduled to the next day. The time must be set in the following way: HH:MM:SS. 

  • External storage ID in Storage Management: Allows you to store monitoring results in a different (external) transparent storage with the help of Storage Management (SM). To do so, you must define a storage ID in Storage Management via transaction /DVD/SM_SETUP. Monitoring results stored on an external storage are protected against retention deletion. Only transparent storages are supported. For more information about Storage Management, contact SNP Support. Default value: <empty> (no external storage is used)

  • Maximum allowed percentage of used aRFC resources: CrystalBridge® Monitoring checks the system and server availability using asynchronous processes (aRFC) to prevent communication freezes. Each system has a limited number of dialog work processes that are used for aRFCs. The default system value is 75%. You can check transaction SARFC for more details.

    This property determines the maximum number of aRFC resources that can be used by CrystalBridge® Monitoring availability checks. If CrystalBridge® Monitoring requests aRFC resources that have exceeded the configured limits, it waits until aRFC resources are available again. The waiting time is defined in the property Maximum waiting time to check available aRFC resources. If the waiting time is exceeded, the availability check is not performed and an error message is written to the log. Only use this property if the CrystalBridge® Monitoring central instance is running on a system with limited resources or on a system where aRFC can be used by other transactions. Default value: <empty>

  • Maximum waiting time to check available aRFC resources: Defines the waiting time in seconds before checking if aRFC resources are available for the CrystalBridge® Monitoring availability check. This property only works in combination with the previous property Maximum allowed percentage of used aRFC resources. If no free aRFC resources are found in the specified time, the collector job is canceled, and an error message is displayed. Default value: 10 seconds

  • Scenario to ping the server from the OS level: Defines the scenario of how the server is pinged from the OS level. The following scenarios are currently supported:

    • C: Ping function is executed from the central system
    • R: Ping function is executed from the remote system
    • N: Ping function is not executed for any server

    By default, the central scenario is used, and servers are pinged from the central system as it worked before this property was created. If any other value than C, R, or N is defined for this property, the central scenario is automatically used. If there is any technical limitation so that the server cannot be pinged from the central system (e.g. network restrictions), you can change the ping function to be executed from the remote system if the remote system is reachable through the RFC destination, or you can skip the ping function.

    NOTE This configuration property is available as of version 2305. To be able to use the remote scenario, the remote (satellite) system must be upgraded to version 2305 or higher as well. Otherwise, you will receive the warning message Function module '/DVD/MON_RFC_PING' does not exist on the system! because the function is not available on lower versions. In this case, the default central scenario is automatically used.
    Also note that it is possible to define dependent values for this property only for a system, not for a specific profile.

  • E-mail address used for the sender of the notification: Defines the e-mail address that is used as a sender in notification e-mails. Default value: do_not_reply@snpgroup.com (the same e-mail address is used if the value is not specified)

    WARNING If you enter an invalid e-mail address, no notification e-mails will be sent.

  • Suppress collector runtime statistics: Allows you to suppress the calculation of the collector runtime statistics. Each collector job calculates the runtime of its current run and an average runtime from the previously calculated values. You can speed up the collector job executions by stopping the calculation of these runtime statistics. 

  • Don't save each message occurrence: Allows you to suppress the saving of occurred messages in the database table /DVD/MON_MSG. You can define this property the database table /DVD/MON_MSG contains many records. If you set this property to X, messages are not saved, and it is not possible to display these messages in the non-aggregated view.

  • Displays pop-up in a different time zone: Informs you that there are time zone differences between the system and the user. The default value is X. Possible values:

    • X: If the system and user time zones differ, a pop-up appears, and the user can still execute CrystalBridge® Monitoring.
    • Y: If the system and user time zones differ, a pop-up appears, but the execution of CrystalBridge® Monitoring is canceled.
    • <empty>: No pop-up appears, even if different time zones are identified.

  • Username for default variant replication: Defines a username whose variant is used as the default variant for other users during the first execution of the CrystalBridge® Monitoring Cockpit or when you reset the user settings. It is not necessary for this username to really exist in the system. The user variant can be copied via transaction /DVD/MON_COPY_USRVAR from an existing user to a non-existing user, and this non-existing username is used for the default variant replication.

Information for transformation-related content packages only (DTS, TC)

If any content package for Data Transformation Streamlined (DTS) or the Transformation Cockpit (TC) is installed on the system, the following configuration property is also available in the list. If no content package is installed on the system, this configuration property is not available.

Minimum retention time in days to retain data on the system: Overrides the predefined (either default or custom) retention time in days for the collector job(s). This retention time in days defines how long the collected data is retained in the monitored system. If this property is set to a value greater than 0, the retention time for the affected collector jobs (the collector jobs whose defined retention time is smaller than the value of this property) is automatically updated to retain the collected data based on this configured value.

By default, this configuration property is empty and the existing retention times (either default or custom) are used. If you define any value greater than 0, only the collector jobs with retention times smaller than this value are updated.

WARNING

Only use and configure this property if you are sure that you have enough system resources to be able to retain all the collected data for longer than the recommended period (default values).

Example of affecting the retention function by using this configuration property:

  • If you have one KPI collected every minute and the default retention time is 7 days, the collected values for this KPI are retained on the system for 7 days. This would amount to approximately 10,000 records for all collected values for this one KPI.
    If this configuration property is set to the value 90, for example, the collected values for this KPI are retained on the system for 90 days. This would amount to approximately 130,000 records for all collected values for this one KPI.

This example shows the impact when setting this configuration property. Ensure that you consider this impact before defining any custom value for this configuration property.

Dependent configuration

Under Configuration > Dependent configuration, you can define each value of the properties mentioned above for a specific system ID, profile or a combination of both. If multiple rows with the same system ID or profile exist, the property value is loaded according to the following rules:

  1. Property values with a specified system ID and profile (both fields are filled) have the highest priority.

  2. Property values with only a specified system ID (Profile field is empty) have a medium priority.

  3. Property values with only a specified profile (System ID field is empty) have the lowest priority.

Example in the screenshot:

The configuration property AGENT_MAX_RUNTIME has the default value of 600 seconds, which means that the background job will be aborted after this time limit.

The first row sets the value for each collector job with the profile DEF_1MIN for each system except the system NSD. Here, the second row has a higher priority because it has the same profile and adds the specified system ID NSD.

The second row overrides the value for the system NSD and the profile DEF_1MIN. It also overrides the property value of the first row for the profile DEF_1MIN.

The third row overrides the value for each collector job executed for the system NSD and any profile of the system except the profile DEF_1MIN, which is defined in the second row. The third row overrides the fourth row too. This is because a property value with a specified system ID has a higher priority than a property value with a specified profile only.

The fourth row overrides the default value for each collector job with the profile DEF_5MIN and on every system except the system NSD. This is because the third row has a specified system ID and therefore has a higher priority.