Operations Automation Content

SAP Focused Run provides several predefined operation flows as guided procedure templates. These guided procedure templates can be either used out of the box or copied into customer name space and adapted.

 

Operation Flows for System Management

  •  "System Health Check for ABAP Systems": Performs several health checks for ABAP systems and sends out a result report with all findings to interested parties. It can be executed manually or scheduled to be executed automatically in regular intervals.
  • "System Health Check for JAVA Systems": Performs several health checks for JAVA systems and sends out a result report with all findings to interested parties. It can be executed manually or scheduled to be executed automatically in regular intervals.

     

Operation Flows for Alert Management

Operation flows for alert management  consist of problem context collection activities and manual activities that guide you through the resolution of the alert. They are triggered either automatically as soon as a new alert was raised or manually from the alert details screen. 

The following predefined  operation flows for alert management are delivered as guided procedures:

  • ARP ASE Database Not Available
  • ARP JAVA Instance Not Available
  • ARP ABAP System Not Available
  • ARP BOE Server Not available
  • ARP HDB Database Not Available
  • ARP JAVA System Not Available
  • ARP ABAP Instance Not Available

Activity Plug-ins

SAP Focused Run provides activity plug-ins automating different tasks. The plug-ins help you to develop your own operation flows of type guided procedure that include tailored, automatic activities. These activities can be triggered manually or executed entirely in the background as part of an alert reaction, service level reporting, health check  or other type of operation flow.

Proceed as follows to include a new plug-in activity in your guided  procedure:

  1. Select the relevant step.
  2. Select Automatic Activity > New.
  3. Choose Select a Plug-in and select the required plug-in from the value help.
  4. Select Display Help and read the plug-in documentation
  5. Rename the activity.
  6. Maintain the plug-in design-time attributes per your requirements.
  7. Select OK.
  8. While the new activity is selected, click Help text > New.
  9. Enter a name for the documentation.
  10. Enter a suitable documentation text. Click Save.
  11.  Use the Move up or Move down buttons to change the order of activities in the step.

SAP delivers many plug-ins that can be easily customized and included into your own guided procedures. The available plug-ins are explained below.

Purpose

For the specified time frame display alerts for the selected system and its instances.

Attributes

Define the following attributes for the plug-in:

  • Time Frame Source: Source for reading the evaluation timeframe: start timestamp and end timestamp - possible values are:
    • Read Timeframe from GP Attributes 
      If you select “Read Timeframe from GP Attributes” you need to specify the timeframe in the GP under Properties – Search Attributes – Free Search Attributes. Press “Add”. Enter Key “TIMEFRAME”. Enter one of the following values: TODAY, LAST_HOUR, LAST_30MIN, LAST_24H, YESTERDAY, CURRENT_WEEK, LAST_WEEK, THIS_MONTH,
    • Specify custom time frame. 
      If you select “Specify custom Timeframe” you need to fill the plug-in parameter “Time Frame” as explained below.
  • "Time Frame (Only with Specify Custom Time Frame)": Specify number of days between 1 and 29. Example: Enter 7d = last 7 days starting from 7 days ago 0:00 am to yesterday 12 pm. 
    Please note: Alerts can be displayed for maximum of 14 days in the past.
  • Chart Title: Specify the table title to be displayed.
  • Max. Number of Rows to Display: max number of alerts in the result table.
  • Monitoring Use case: Choose the monitoring scenario for which to display alerts .
  • Display Closed: whether to display closed (confirmed) alerts or only open alerts.
  • Display Details: whether to display additional attributes like Additional Alert Keys.
  • Alert1 .. Alert10: alert names (texts) of the alerts to be displayed. Wildcards at the end of the alert name are supported.

Result

The result is displayed as a table containing a list of all alerts in the specified time frame. The plug-in will set a yellow rating if corresponding alerts were found. Otherwise the rating is green.

Purpose

To display OCC dashboard data in a guided procedure report.

Prerequisite

Limitations

  • The plug-in will display the data for the scope (managed systems) defined in the OCC dashboard and not necessarily for the scope of the guided procedure.
  • The plug-in supports only a limited set of chart types (line chart, column chart and table) and not all other chart types supported by OCC dashboards. 

Design-Time attributes

  • Title: Enter a title to be displayed on top of the chart or table
  • Graphic Type: Choose Line chart, Column chart or Table. If the gadget uses the dynamic table renderer, choose Table. Otherwise, you can choose what you wish.
  • Page Id: Enter the page id guid of the gadget. Example: 98F2B3032CD31EECBC8F8585F8BB32D5.
  • View Id: Enter the view id guid of the gadget. Example: guid_1b1bee70-3c1b-4f25-9fc7-ceb60a50377b
  • Max Row Count: Only if you have chosen Graphic Type Table: Enter optionally the maximum number of rows to be displayed in the table.

Purpose

To check and report aborted jobs in a managed system.

The plug-in retrieves all aborted jobs in the given time frame and groups them by job name. It uses the local data available in the Job & Automation Monitoring.

Prerequisites

Job & Automation Monitoring has been setup for selected managed systems.

 

Attributes

Define the following attributes for the plug-in:

  • Time-Frame Source: Specify how the time frame for the evaluation is to be determined. Possible values are:
    • Read Time Frame from Alert: If the guided procedure is started from the Alert Inbox, select this option to read the time stamp from the alert
    • Read Time Frame from GP Attributes: Select this option to read the time stamp from the guided procedure (step or guided procedure level)
    • Specify Custom Time Frame: Select this option to read the time stamp defined in the Time Frame attribute
    • Time Frame (Only with Specify Custom Time Frame): Specify the time frame only if you have set the time-frame source to Specify Custom Time Frame. Possible values are:
      • TODAY (current day from 00:00)
      • XXm (last XX minutes)
      • XXh (last XX hours)
      • XXd (last XX days, including a full day)
      • YESTERDAY (previous full day)
      • CURRENT_WEEK (from Monday 00:00 to now)
      • LAST_WEEK (from Monday 00:00 to Sunday 23:59)
  • Graphic Type: Specify whether you want the result to be displayed as a table or bar chart.

        Number of Rows to Display: Maximum size of result list

Result

Both the table and the bar chart show the number of aborted runs for the top n aborted jobs or job types.

Purpose

To verify that all standard reorganization jobs have been executed successfully.

Prerequisites

Job & Automation Monitoring has been setup for selected managed systems.

Result

The result is displayed as a table containing the job name, program name, interval, time at which the job was last executed, status of the last job, results, and the status.

Purpose

to report about long running jobs in managed systems for selectable time frames.
The plug-in retrieves all jobs that were active for more than x minutes in the given time frame and groups them by job name. It uses the data available in the Job & Automation Monitoring.

Prerequisites

Job & Automation Monitoring has been setup for selected managed systems.

Attributes

  • Red Threshold for Batch Job Runtime (Minutes): Specify the threshold for runtime in minutes. Jobs running for longer than this threshold will be reported
  • Graphic Type: Specify whether you want the result to be displayed as a table or bar chart
  • Time-Frame Source: Specify how the time frame for the evaluation is to be determined. Possible values are:
    • Read Time Frame from GP Attributes: Select this option to read the time stamp from the guided procedure (step or guided procedure level)
    • Time Frame (Only with Specify Custom Time Frame): Specify the time frame only if you have set the time-frame source to Specify Custom Time Frame. Possible values are:
      • XXm (last XX minutes)
      • XXh (last XX hours)
      • XXd (last XX days, including a full day)
      • TODAY (current day from 00:00)
      • YESTERDAY (previous full day)
      • CURRENT_WEEK (from Monday 00:00 to now)
      • LAST_WEEK (from Monday 00:00 to Sunday 23:59)
  • Please note: Job & Automation monitoring provides the data for a maximum of 3 days in the past.

Data Source

The long-running jobs are retrieved from Job & Automation Monitoring.

Result

The result is displayed as a table or bar chart containing the job name and runtime in minutes.

Purpose

With the plugin “Execute Custom Process via SAP Landscape Management” you can trigger from a guided procedure in SAP Focused Run a Custom process in SAP Landscape Management. Currently supported are

  • ABAP, JAVA and HANA systems
  • ABAP, Java and HANA system instances
  • Databases

 

By default, the plug-in will trigger the specified SAP Landscape Management Custom process for the managed system specified by the scope object of the Guided procedure. When, however, the guided procedure is performed for an instance alert, the Custom process will be triggered only for the instance reported in the alert.

Prerequisite

  • You need to maintain in transaction SM59 an HTTP connection type G to the SAP Landscape Management with administrator credentials
  • The managed ABAP, Java and Hana systems need to be known to both SAP Focused Run and SAP Landscape Management
  • The user executing the guided procedure needs to have authorization object FRN_GP_LMP object with following fields:
    • CUSTOM_OP - LAMA custom process
    • LDB_CUSNET - customer network hash or *
    • GP_SCOPE - system's SID, hostname or *

 

Parameters

  • RFC Destination - the Http destination to the LAMA system (HTTP Connection to External Server)
  • Execution Timeout - the operation timeout in seconds, this means how long to wait for the operation results
  • Custom process - the custom process name
  • Wait for result - Yes/No. If No, the plugin won't wait for the operation's results (success/errors)           

Notes

  • SAP Landscape Management operations can run for several minutes. it is recommended to execute the guided procedure from background to avoid UI refresh issues in SAP Focused Run.

ABAP System Logs from Integration Error Monitor

Purpose

You can use this guided procedure plug-in to get an overview over the top system log messages reported per time frame. This plug-in reads system log data from the Integration Error Monitor in Integration & Cloud Monitoring.
There is another “old” plug-in “ABAP System Logs” that reads the system log messages directly from the managed system. In order to avoid redundant data collection we recommend to use this plug-in instead of the old plug-in.

Prerequisites

  • This plug-in can be used only for guided procedures that are executed for ABAP systems
  • The category “ABAP System Log” needs to be enabled in Integration & Cloud Monitoring à Configuration for the respective managed systems

Attributes

Define the following attributes for the plug-in:

  • Time-Frame Source: Specify how the time frame for the evaluation is to be determined. Possible values are:
    • Read Time Frame from Alert: If the guided procedure is started from the Alert Inbox, select this option to read the time stamp from the alert.
    • Read Time Frame from GP Attributes: Select this option to read the time stamp from the guided procedure (step or guided procedure level).
    • Specify Custom Time Frame: Select this option to read the time stamp defined in the Time Frame attribute.
  • Time Frame (Only with Specify Custom Time Frame): Specify the time frame only if you have set the time-frame source to Specify Custom Time Frame. Possible values are:
    • TODAY (current day from 00:00)
    • XXm (last XX minutes)
    • XXh (last XX hours)
    • XXd (last XX days, including a full day)
    • YESTERDAY (previous full day)
    • CURRENT_WEEK (from Monday 00:00 to now)
    • LAST_WEEK (from Monday 00:00 to Sunday 23:59)
  • Graphic Type: Specify whether you want the result to be displayed as a table or bar chart.
  • Number of Rows to Display: Specify the number of top system logs that you want to be displayed in the results. If you want to view all the logs, leave this entry blank.
  • Write Time Stamp as Log Message: Select this checkbox to display the message "The following time frame was evaluated from <time stamp> to <time stamp> time zone <TZ>" in the log.         

Data Source

Integration Error Monitor in Integration & Cloud Monitoring.

Result

The result is displayed as a table or chart. The table contains the full message ID, the type of system log error, the last occurrence, which is a timestamp on the system time zone of the managed system, and the number of errors. The chart shows the number of errors per system log.

Purpose

Display  past and ongoing planned downtimes

Attributes

Define the following attributes for the plug-in:

  • Show Data for last N hours: Specify the last number of hours in to be included in the report. The default value is 24.
  • Show Dates and Times in Time Zone: Enter the time zone that is to be used to display dates and times.

Data Source

The data is retrieved from work modes that are scheduled in work mode management.

Result

The result is displayed in a table that shows the start and end of the planned downtime, the duration in minutes, the category, and the reason.

Purpose

This plug-in shows the average response times, database times, CPU times, processing times and roll wait times for task types Dialog, HTTP, HTTPs and RFC.

Prerequisites

This plug-in works only in guided procedures for ABAP Systems.

Attributes

Define the following attributes for the plug-in:

  • Reporting Period: Specify the period for which you want to generate the report. You can enter the last n weeks or months.
  • Reporting Granularity: Specify the level of detail in which you want the results to be shown.
  • Task Type: Select the task type for which you want to view the performance metrics.

Data Source

Workload data are read from ABAP aggregated statistical records (“ST03 data”) in Focused Run .The collection of ST03 data (hourly and daily aggregates) is automatically scheduled as part of simple System Integration.

Result

The result is displayed as a line chart.

Purpose

Trigger from a guided procedure in SAP Focused Run instance operations for ABAP and JAVA systems and HANA Databases in SAP Landscape Management.
Supported are the following operations:

  •   start
  •   stop
  •   restart

 

By default, the plug-in will trigger the specified SAP Landscape Management instance operation on all instances of the managed system which is in scope of the guided procedure excluding the instances of the assigned system database.
When, however, the guided procedure is performed for an instance alert,  the instance operation will be triggered only for the instance reported in the alert.

Prerequisites

  •  You need to maintain in transaction SM59 a HTTP connection type G to the SAP Landscape Management system with administrator credentials.
  • The managed ABAP, Java and Hana systems need to be known to both SAP Focused Run and SAP Landscape Management.
  • The user executing the guided procedure needs to have the following authorizations:
    Authorization object  FRN_GP_LAM object with following fields:
    • -             LAMA_OPER - permitted  operations: start/stop/restart
    • -             LDB_CUSNET - customer network hash or *
    • -             SYSTEMID - system's SID or *

Parameters

  • RFC Destination - the Http destination to the LAMA system (HTTP Connection to External Server)
  • Execution Timeout - the operation timeout in seconds, this means how long to wait for the operation results
  • Instance Operation - the operation, currently following operations are supported: start/stop/restart
  • Wait for result - Yes/No. If No, the plugin won't wait for the operation's results (success/errors)

        

Notes

  • SAP Landscape Management operations can run for several minutes. it is recommended to execute the guided procedure from background to avoid UI refresh issues in SAP Focused Run
  • For stop and start operations , if the instance is already in target state , SAP Landscape Management will do nothing and return a warning message that the instance is already in target state.
  • If SAP Landscape Management detects, that in addition to the instances provided by the guided procedure, other dependent instances need to be stopped or started, the operation will be canceled and an error message "Error executing LAMA operation 'start' : An exception was raised" with details "Status: 400. Code: VALIDATION_FAILED. Message: Dependent instances are missing in the request." will be returned.

This guided procedure plug-in schedules one ABAP job ad hoc in the managed ABAP systems. After successful job completion it displays optionally job log and spool output from this job in the guided procedure and the result report.

Details

  • The job scheduling will be triggered from SD Agent user in the managed ABAP system in the default client. The default client for a managed ABAP system is defined in Simple System Integration under "Edit Configuration". It is not possible to schedule the job in a different client.
  • The plug-in will wait for a specified time to fetch the job results. If this time is exceeded and the jobs were not finished it will return with an error message. If the plug-in is executed a 2nd time it will schedule the job again.
  • If it is expected that the job runtime in the managed system exceeds some seconds, then the corresponding guided procedure should be executed in background via GP Planning and not manual.
  • The spool output of some jobs might contain print controls for list output. These print controls cannot be interpreted and displayed by the guided procedure and the result report and will be displayed in plain text.

Prerequisites

  • This plug-in is available as of FRUN 3.0 SP00.
  • This plug-in works only for managed ABAP systems with releases 7.4 and higher.
  • ST-PI version 740 support package 15 or ST-PI version 740 support package 14 + SAP Note 2984060 has to be installed on the managed ABAP System.
  • The user triggering the corresponding guided procedure in Focused Run (e.g. FRN_BTC_GPA) needs to have authorization object FRN_GP_REP with field report name = Name of the reports that should be triggered in the managed system and Activity Execute. This authorization object is delivered with the roles SAP_FRN_APP_GP_ALL, SAP_FRN_APP_GP_EXE, SAP_FRN_BTC_GPA with empty report name values that need to be completed user specific.
  • The SDAGENT user creates the job in the managed ABAP system . If the job steps should be executed under a different user then you need to grant the SDAGENT user in the managed ABAP system the authorization to create jobs for another user. The required authorization object is S_BTC_NAM with field "BTCUNAME". This authorization object is not part of the standard roles delivered for the SDAGENT user and you need to assign it to the SDAGENT user .

Design Time Attributes

You need to configure the following parameters:

  • Job Name: The Plug-in will schedule the job under this job name in the selected managed ABAP systems.
  • Report Name 1..5: Name of the ABAP reports that should be executed as steps of the job. Up to 5 ABAP reports can be scheduled in one job. At least one report name must be entered in field Report1. The specified ABAP reports must exist in the managed ABAP systems.
  • Variant Name 1…5 : Name of the variants for report 1 to 5. If no variant is specified, the corresponding report will be scheduled without variant. The specified variants must exist in the managed ABAP system.
  • Batch job username: The username under which the reports will be executed. This user must exist in the managed ABAP systems and must have authorization to execute the corresponding reports and their variants.
  • Timeout (in seconds): Threshold of waiting time in seconds. It should be set to longer than the expected runtime of the complete job. If the expected runtime of the complete iob is more than a few seconds, then the guided procedure should be triggered from guided procedure planning and not manually to avoid time out issues in the guided procedure runtime UI.
  • Display maximum number of lines from job log: Whether the job log should be displayed in the guided procedure and the result report after successful job execution and up to how many lines from the job log are shown. 0 or space means the job log is not shown at all. Maximum permitted value is 100.
  • Display maximum number of lines from spool: Whether the spool output of the reports should be displayed in the guided procedure and the result report after successful job execution and up to how may lines from the spool output are shown. 0 or space means the job log is not shown at all. Maximum permitted value is 100.

Runtime

The plug-in displays navigation links to transaction SM37 in the managed system.

When triggered it checks first if the focused run user executing the guided procedure is authorized to execute the specified reports (authorization object FRN_GP_REP). If not, it stops processing, sets a red rating and a corresponding error message in the guided procedure.

Afterwards, it will attempt to trigger the job in the managed system via ST-PI data provider /SDF/CL_GPCR_SCHEDULE_JOB. If the managed system is not on the right ST-PI level it will stop the processing, set a red rating and return error message “The object could not be created: The class /SDF/CL_GPCR_SCHEDULE_JOB does not exist”.

If the plug-in can schedule the job successfully it returns a success message “Job <jobname> has been scheduled. “

Otherwise it stops processing and returns an error message.

Now it waits up to the specified time for job completion.

if the job does not finish within this time interval , the plug-in will return a warning message “Job <Job Name> is still running after <Timeout (sec)> seconds. No result display possible", set a yellow rating and stop processing.

If the job cancels, the plug-in will set a red rating and error log message Job <Job Name> canceled".

If the job finishes successfully it will set a green rating and display success message "Job <Job Name> finished". Depending on the configured settings  it will display the job log and the spool output.

Purpose:

This guided procedure plug-in checks whether the SAP EarlyWatch Alert has been activated for the managed system and optionally whether

  • Service Data request is picked up by the collecting system
  • Service data is received by FRUN
  • EWA Service data is successfully forwarded to SAP

It does not check whether the SAP EarlyWatch Alert was successfully generated in SAP BackBone or not.

Design Time Attributes:

You can disable or enable the following checks:

  • Check whether Service Data request is picked up by the collecting system
  • Check whether Service data is received by FRUN
  • Check whether EWA Service data is successfully forwarded to SAP

The “Check whether SAP EarlyWatch Alert is active” is always enabled by default.

Runtime:

The plug-in returns success or error messages depending on the selected checks and status.

It provides a navigation link to the SAP EarlyWatch Alert Status UI from where you can see more detailed information and obtain troubleshooting information about the displayed statuses.

Rating:

If all checks return a success status, the overall rating is set to success , otherwise to error.

You can use this plug-in to execute a SQL statement via SAP Host Agent on a SAP HANA Database

The plug-in executes the statement and displays the results as a table. Only the statements that are listed below can be executed.

 

Prerequisites

  • This plug-in works only with  SAP Hana database
  • It is available as of SAP Focused Run 2.0 FP03
  • The SAP host agent installed on the database hosts fulfills the minimum requirements listed below.
  • Depending on your host agent version you need to download the latest version of "50.adhocsql.frun.hdb.cimobj" file from SAP Note 2555664 and copy it to the host agents .

Available SQL Statements

The following SQL statements are available as of SAP Host Agent 7.21 PL 47 + SAP Note 2555664 or SAP Host Agent 7.21 PL 48

  • HANA_Security_MiniChecks
    • Security related check list. See SAP Note 1969700 for details
  • HANA_Trace_Files_Mini_Checks
    • Reports trace files entries that may indicate an issue. See SAP Note 1969700 for details.
  • HANA_Configuration_Overview
    • Shows general information. See SAP Note 1969700 for details.
  • HANA_Configuration_Infrastructure
    • Shows Infrastructure configuration (hosts, disk, network, OS, memory, CPU, ...). See SAP Note 1969700 for details.
  • HANA_Replication_SystemReplication_ParameterDeviations
    • Displays statistic server information for SAP HANA parameter deviations between primary and replication side. See SAP Note 1969700 for details.

Plug-in Configuration

Configure the Plug-In exactly as follows

  • SQL statement: <enter the name of SQL statement as listed above Example: HANA_Security_MiniChecks> 
  • Arguments: dbname=${HDBDBNAME};dbtype=hdb;dbinstname=${HDBINSTNAME};dbhost=${HOST}; 
  • Execution Scope: SAP HANA Master Node

The Plug-in must be configured exactly as above. The argument string must be entered exactly as above. Do not replace ${HDBDBNAME} , {HDBINSTNAME}, ${HOST} in the argument string by something else.

Purpose

You can use this guided procedure plug-in to assess the following key performance indicators (KPIs) for different tasks types:

  • Average response time

  • Database time

  • CPU time 

  • Number of steps per hour

Prerequisites

This plug-in is available only for ABAP systems.

Attributes

Define the following attributes for the plug-in:

  • Reporting Period: Specify the period for which you want to generate the report. You can enter the last n weeks or months.

  • Reporting Granularity: Specify the level of detail in which you want the results to be shown. You can choose between the total results, or the results broken down by month or day.

  • Task Type: Select the task type for which you want to view the performance metrics.

  • Metrics: Specify the KPI that you want to assess.

Data Source

The plug-in gets its data from reader CL_STATRAGG_READER.

Result

The result is displayed as a line chart showing the average response time, database time, and CPU time for each task over a given time frame. It also shows the number of steps based on the attributes that you selected.

Purpose

You can use this guided procedure plug-in to check aborted jobs in ABAP technical systems.

The plug-in retrieves all aborted jobs in the given time frame and groups them by job name.

Prerequisites

This plug-in is available only for ABAP systems.

Attributes

Define the following attributes for the plug-in:

  • Time-Frame Source: Specify how the time frame for the evaluation is to be determined. Possible values are: 

  • Read Time Frame from Alert: If the guided procedure is started from the Alert Inbox, select this option to read the time stamp from the alert.

  • Read Time Frame from GP Attributes: Select this option to read the time stamp from the guided procedure (step or guided procedure level).

  • Specify Custom Time Frame: Select this option to read the time stamp defined in the Time Frame attribute.

  • Time Frame (Only with Specify Custom Time Frame): Specify the time frame only if you have set the time-frame source to Specify Custom Time Frame. Possible values are:

  • TODAY (current day from 00:00)

  • XXm (last XX minutes)

  • XXh (last XX hours)

  • XXd (last XX days, including a full day) 

  • YESTERDAY (previous full day)

  • CURRENT_WEEK (from Monday 00:00 to now)

  • LAST_WEEK (from Monday 00:00 to Sunday 23:59)

  • Graphic Type: Specify whether you want the result to be displayed as a table or bar chart.

Data Source

The aborted jobs are retrieved via RFC call from managed ABAP System.

Result

Both the table and the bar chart show the number of aborted runs for the top n aborted jobs or job types. 

Purpose

This guided procedure plug-in shows the  installed languages in the managed ABAP  system.

Prerequisites

  • This plugin- is available as of FRUN 2.0 FP01

Data Sources

  • Installed languages data is retrieved using the CCDB store: SMLT_LANGUAGES.

Result

  • Table Chart Output
  • Log Output:

The following log messages are returned by the plugin depending on the result of the check

  • <N> installed languages found. (Success)
  • No data found. (Error)

Purpose

This guided procedure plug-in is displays errors reported in the TMS Transport Logs of  the managed ABAP system.

Prerequisites

  • FRUN 2.0 FP01 or higher
  • ST-PI version 740 Support package 11 has to be installed on the managed ABAP System.

Data Source

  • Data is retrieved using the ST-PI data provider: /SDF/CL_GPCR_CHECK_TRANS_ERROR

Result

  • Table Chart Output
  • Log Output

The following log messages are returned by the plugin depending on the result of the check

  • No Errors detected in TP System Log    (Success)
  • Errors detected in TP System Log (Error)

Purpose

This guided procedure plug-in displays qRFC queues in waiting and error state.

Prerequisites

  • FRUN 2.0 FP01 or higher
  • This plugin works only for ABAP systems.
  • ST-PI version 740   Support package 11 has to be installed on the managed ABAP System.

Design Time Attributes

You can configure the following parameters:

  • Direction (Inbound or outbound queue)
  • Check queues in error state (A checkbox to filter on queues in qstate =ANORETRY, CPICERR, SYSFAIL, VBERROR)
  • Check queues in waiting state (A checkbox to filter on queues in qstate =WAITING, WAITSTOP, WAITUPDA)
  • Display top N queues
  • Sort by
  • Show only queues older than n days

Data Source

  • qRFC queues in waiting and error state is retrieved using the ST-PI data provider: /SDF/CL_GPCR_CHECK_QRFC_QUEUE

Result

  • Table Chart Output
  • Log Output

The following log messages are returned by the plugin depending on the result of the check:

  • <N> qRFC Queues in waiting status detected. (Warning)
  • <N> qRFC Queues in error status detected. (Error)   
  • No queues in error or waiting state found. (Success)   
  • No SDA Agent running or no destination available for ABAP Technical System FT4. (Error)

Purpose

This guided procedure plug-in is designed to trigger a specific task list in the managed ABAP system and monitor the task list run execution and its tasks status.

The task list run which will be created is related to the current GP instance. As long as the user is editing the same GP instance, the plug-in is monitoring the same task list run, so that any further execution of the plug-in on this GP instance will check the status of the related task list run.

However, a first execution of the plugin in a new GP instance will trigger a new task list run of the specified task list.

Prerequisites

  • This plugin- is available as of FRUN 2.0 FP01
  • This plug-in works only for managed ABAP systems with releases 7.4 and higher.
  • ST-PI version 740 Support package 11 has to be installed on the managed ABAP System.
  • This plugin- triggers the execution of the specified task list via SDAGENT user in the managed ABAP System. The required authorizations are not included in the standard roles SAP_FRN_SDAGENT* of the SDAGENT user.
    To be able to execute the task list, SDAGENT user needs to have SAP BASIS Administrator roles in the relevant managed ABAP system.

Design Time Attributes

You can configure the following parameters:

  • Task List Name: Name of the task list to check if it exists or trigger it if not    
  • Task List Variant: Variant of the task list to which it'll be assigned when triggered    
  • Wait for Result: A checkbox to either wait for the result or not if task list is still running    
  • Timeout (in minutes): Threshold of waiting time in minutes (if "Wait for Result")    
  • Show Successful Checks: A checkbox to either show successful checks or not    
  • Show Warning Checks: A checkbox to either show warning checks or not    
  • Show Error Checks: A checkbox to either show red checks or not    
  • Show Unprocessed Checks: A checkbox to either show unprocessed checks or not    
  • Show Task Logs: A checkbox to either show log messages of tasks not    
  • Check to be excluded <N>: Name of Task to be skipped in list execution.
    The name of the tasks that should be skipped from the task list run  can be found as follows:  Open transaction STC01 in the managed ABAP system. Select the task list and press button display. Copy the task name of each task that should not be executed.
    Enter the task name in the GP attribute "Check to be excluded <N>"

Example of plug-in configuration:

You would like to include the task list SAP_BASIS_SYSTEM_CONFIG_CHECK in your guided procedure to check Basis system configuration.

  1. Enhance the roles of the SDAGENT user in the managed ABAP system
    The task list execution will be triggered from the guided procedure in the SAP Focused Run system via the SDAGENT user in the managed ABAP system. The default roles of the SDAGENT user are not sufficient to execute the task list. You need to enhance the authorization of the SDAGENT user in the managed ABAP System as explained in SAP Note 2752780.

  2. Include  the plug-in in your Guided Procedure
    1. Open the GP in Edit Mode
    2. Select your GP step -> Step Content -> Automatic Activities -> New -> Select a Plugin -> Plug-In
    3. Select the plug-in ABAP Execute Task List
       
  3. Fill the plug-in attributes
    Enter the following values:
  • Task List Name: SAP_BASIS_SYSTEM_CONFIG_CHECK
  • Task List Variant: Enter the name of a variant that exists in the managed system or leave it empty
  • Wait for Result: X
  • Timeout (in minutes): 2
  • Show Successful Checks: X
  • Show Warning Checks: X
  • Show Error Checks: X
  • Show Unprocessed Checks: X
  • Show Task Logs: X

The task list SAP_BASIS_SYSTEM_CONFIG_CHECK contains some checks that require  specific configurations in the managed system. Without configuration the task list run  will not finish successfully.

We recommend to exclude these checks from task list processing. Therefore maintain the following:

  • Check to be excluded 1: CL_STCT_CHECK_RFC_DESTINATION
  • Check to be excluded 2: CL_STCT_CHECK_JOB_STATUS
  • Check to be excluded 3: CL_STCT_CHECK_USER
  • Check to be excluded 4: CL_STCT_CHECK_PROFILE_PARAMS

 

Trigger the task list:

After editing and saving the GP, execute a new instance of it in an ABAP managed system either manually or scheduled by GP Planning.

Data Source

  • Task List related data is retrieved using the ST-PI data provider: /SDF/CL_GPCR_TASK_LIST_CHECK_N
  • Task List is triggered using the ST-PI data provider: /SDF/CL_GPCR_TASK_LIST_TRIGG_N

Result

  • Table Chart Output showing the details of the task list checks.
  • Log Output:

The following log messages are returned by the plugin depending on the result of the check

  • The Task list <Task List Name> with variant <Variant ID> and external session id <ext session ID> is still running after <N> minutes. Please try again later. (Warning)
  • The Task list <Task List Name> with variant <Variant ID> and external session id <ext session ID> failed (errors occurred). (Error)   
  • The Task list <Task List Name> with variant <Variant ID> and external session id <ext session ID> finished successfully. (Success)   
  • The Task list <Task List Name> with variant <Variant ID> and external session id <ext session ID> has been triggered successfully. (Success)   
  • The Task list <Task List Name> with variant <Variant ID> and external session id <ext session ID> finished with warnings. (Warning)    
  • The Task list <Task List Name> with variant <Variant ID> and external session id <ext session ID> is <Task List Status>. (Error)   

Possible errors:

Failed Task List Trigger

Log message:

  • Trigger of Task List <Task List Name> with variant <Variant ID> failed with error message: <error message>

Purpose

This guided procedure plug-in checks whether  that all services preparation recommendations are implemented in the managed ABAP System. 

Prerequisites

ST-PI version 740 Support package 11 has to be installed on the managed ABAP System.

Design Time Attributes

No design time attributes required.

Data Source

It performs an RFC call into the managed ABAP System and reads data from the Service Preparation Check (ABAP report RTCCTOOL )

Result

  • Table Chart Output
  • Log Output:

The following log messages are returned by the plugin depending on the result of the check

  • All service preparation check recommendations are implemented. (Success)
  • Missing or incomplete service preparation check recommendations detected. (Error/warning)

Purpose

You can use this guided procedure plug-in to check the status of your system license.

The plug-in can also remind you that your license will be overdue in a specific number of days.

Prerequisites 

This plug-in is available only for ABAP systems.

Attributes

Define the following attributes for the plug-in:

  • Threshold for Red Rating: Enter the number of days until the license will become overdue to generate an error in the result. For example, a value of 5 will return an error for any licenses that expire within the next five days. 

  • Threshold for Yellow Rating: Enter the number of days until the license will become overdue to generate a warning in the result. For example, a value of 10 will return a warning for any licenses that expire within the next ten days.

Data Source

License data is retrieved via RFC Call from managed ABAP System

Result 

The result is displayed as a table containing the system ID, product ID, license key, expiry date, and the validity status.

Purpose

You can use this guided procedure plug-in to evaluate the buffers on each instance of the managed system.

Prerequisites

  • This plug-in is available only for ABAP systems.

  • The user SDAGENT_<SID> in the managed ABAP system  requires authorization object S_ADMIN_FCD with field STOR.

Attributes

Define the following attributes for the plug-in:

  • Minimum Threshold for Hit Ratio (%): Enter a number that represents the minimum threshold in percent for the hit ratio. If the hit ratio is below this threshold, the activity will be rated red.

  • Maximum Threshold for SWAPS: Enter a number that represents the maximum threshold in percent for the buffer swaps.If the buffer swaps exceed  this threshold, the activity will be rated red.

Data Source

Buffer data is retrieved via RFC Call from managed ABAP System

Result

The result is displayed as a table containing the instance name, buffer name, hit ratio, and swaps. A link is also provided so that you can check the result directly in transaction ST02.

Purpose

You can use this guided procedure plug-in to analyze the client change settings in an ABAP technical system. This check is only relevant for production systems.

Prerequisites

This plug-in is only relevant for ABAP production systems.

Attributes

Define the following attributes for the plug-in:

  • Optional Check: Specify whether you want to check CATT and eCATT authorization.

Data Source

The check is based on the CCDB Store CLIENTS:

  • Group name: SYSTEM-CHANGE-OPTION

  • Alias: SYSTEM-CHANGE-OPTION

  • Sub-alias: CLIENT-SETTING

Result

Log messages indicate whether client settings are correct or not for production systems.

Purpose

You can use this guided procedure plug-in to check dialog and HTTP response times from the system monitoring metric data for the selected ABAP technical systems.

You can define a threshold for each response time category.

Prerequisites

  • This plug-in is available only for ABAP technical systems.

  • The following monitoring metrics must be active for the current scope:

  • HTTP Response Time: ABAP_INST_ASR_HTTP_TOTAL

  • HTTPS Response Time: ABAP_INST_ASR_HTTPS_TOTAL 

  • DIALOG Response Time: ABAP_INST_ASR_DIA_TOTAL

Attributes

Define the following attributes for the plug-in:

  • Time-Frame Source: Specify how the time frame for the evaluation is to be determined. Possible values are:

  • Read Time Frame from GP Attributes: Select this option to read the time stamp from the guided procedure (step or guided procedure level).

  • Specify Custom Time Frame: Select this option to read the time stamp defined in the Last n Days attribute.

  • Last n Days: Specify the time frame only if you have set the time-frame source to Specify Custom Time Frame. Possible values are:

  • TODAY (current day from 00:00) 

  • XXm (last XX minutes)

  • XXh (last XX hours)

  • XXd (last XX days, including a full day)

  • YESTERDAY (previous full day)

  • CURRENT_WEEK (from Monday 00:00 to now)

  • LAST_WEEK (from Monday 00:00 to Sunday 23:59)

  • Granularity: Specify the level of detail in which you want the results to be shown.

  • Graphic Type: Specify whether you want the result to be displayed as a table, column chart, or line chart. 

Data Source

  • Data is retrieved from system monitoring.

  • The metrics HTTP Response Time, HTTPS Response Time, and DIALOG Response Time are considered.

Result

The result is displayed as a table, column chart, or line chart depending on the attributes that you configured for the plug-in.

Purpose

You can use this guided procedure plug-in to analyze IDocs with errors in your managed system. Different attributes are available to filter and classify the IDocs. A direct link is also provided so that you can access transaction BD87.

Prerequisites

This plug-in is only available for ABAP technical systems.

Attributes

Define the following attributes for the plug-in:

  • Time-Frame Source: Specify how the time frame for the evaluation is to be determined. Possible values are:

  • Read Time Frame from GP Attributes: Select this option to read the time stamp from the guided procedure (step or guided procedure level).

  • Specify Custom Time Frame: Select this option to read the time stamp defined in the Time Frame attribute.

  • Time Frame (Only with Specify Custom Time Frame): Specify the time frame only if you have set the time-frame source to Specify Custom Time Frame. Possible values are:

  • TODAY (current day from 00:00)

  • XXm (last XX minutes)

  • XXh (last XX hours)

  • XXd (last XX days, including a full day)

  • YESTERDAY (previous full day)

  • CURRENT_WEEK (from Monday 00:00 to now)

  • LAST_WEEK (from Monday 00:00 to Sunday 23:59)

  • Graphic Type: Specify whether you want the result to be displayed as a table or bar chart.

  • IDoc Direction:

  • Inbound

  • Outbound

  • Inbound and Outbound 

  • Threshold for Red IDoc Status: The system checks whether the number of IDocs categorized as "red" exceeds the value you enter here. If so, a log is written, and the activity is rated as red.

  • Threshold for Yellow IDoc Status: The system checks if the number of IDocs categorized as "yellow" exceeds the value you enter here. If so, a log is written, and the activity is rated as yellow.

  • Codes for Green IDoc Status: Specify the codes used to classify an IDoc with a green status. (Multiple codes should be separated by comma, for example, 51,52,53.)

  • Codes for Red IDoc Status: Specify the codes used to classify an IDoc with a red status (Multiple codes should be separated by comma, for example, 51,52,53.)

  • Codes for Yellow IDoc Status: Specify the codes used to classify an IDoc with a yellow status (Multiple codes should be separated by comma, for example, 51,52,53.)

  • Message Types: Specify the types of IDoc message to be considered. Multiple message types must be separated by a comma (,).

  • Clients: Specify the clients to be considered when reading the IDoc. Multiple clients must be separated by a comma (,).

Data Source

Data is retrieved via RFC call in managed ABAP system.

Result

The result is displayed as a table containing the client, message type, status code, number of updated IDocs, and the state.

Purpose 

You can use this guided procedure plug-in to analyze the availability of ABAP instances from the System Monitoring metric data.

The plug-in allows operators to check whether an ABAP instance is still unavailable before they start to investigate further within the guided procedure. The plug-in can also be added at the end of a guided procedure to check whether the actions performed to resolve the instance availability were successful.

Prerequisites 

  • This plug-in is available only for ABAP systems.

  • The following monitoring metrics must be active for the current scope:

  • ABAP_INSTANCE_STATUS

  • ABAP_INSTANCE_LOCAL_HTTP_AVAIL 

  • ABAP_LOCAL_RFC_AVAILABILITY

  • ABAP_LOCAL_LOGON_TEST

Attributes

Define the following attributes for the plug-in: 

  • Check "Local RFC Instance Availability"

  • Check "Local HTTP Instance Availability"

  • Check "Instance Status from SAPSTARTSRV"

  • Check "Local Instance LOGON TEST" 

Data Source

Data is retrieved from system monitoring. The names of the ABAP Instance Availability metrics are taken into consideration.

Result

The result is display as a table containing the system ID, instance name, metric name, status, message, and the time stamp at which the measurement took place. 

Purpose

You can use this guided procedure plug-in to analyze lock entries for ABAP managed systems.

The plug-in performs two types of check:

  • It checks users who have multiple lock entries. 

  • It checks entries that have been locked for over a certain number of hours.

Prerequisites

This plug-in is available only for ABAP systems.

Attributes 

  • Red Threshold for Old Entries (Hours): Specify the number of hours for which an entry can be locked before a red result is returned. The default value is 24 hours.

  • Red Threshold for Number of Entries per User: Specify the amount of entries that a user can lock before a red result is returned. The default value is 10,000 entries.

  • Check Mode: Select whether the plug-in is to check the old lock entries or the users who have multiple locks.

Data Source 

Lock entries are retrieved via RFC Call from managed ABAP System

Result

The result is displayed as a table containing the number of lock entries older than the specified number of hours, or the users with more lock entries than specified.

Purpose

You can use this guided procedure plug-in to determine whether the runtime of active jobs from the managed system exceeds a given threshold.

Prerequisites

This plug-in is available only for ABAP systems. 

Attributes

  • Red Threshold for Batch Job Runtime (Minutes): Specify the threshold for the runtime, as of which an error will be generated in the report.

  • Graphic Type: Specify whether you want the result to be displayed as a table or bar chart.

Data Source 

Related long-running jobs are retrieved via RFC Call from managed ABAP System

Result

The result is displayed as a table or bar chart containing the job name and runtime in minutes.

Purpose

You can use this guided procedure plug-in to perform two types of checks on ABAP managed technical systems: You can check for long-running work processes and you can check the work process statuses (in PRIV mode). 

Prerequisites

This plug-in is available only for ABAP systems. 

Attributes

Define the following attributes for the plug-in: 

  • Yellow Threshold for Dialog Tasks (Seconds): Specify the runtime in seconds after which a warning is to be issued for the dialog work processes.

  • Red Threshold for Dialog Tasks (Seconds): Specify the runtime in seconds after which an error is to be issued for the dialog work processes. 

  • Yellow Threshold for Batch Tasks (Seconds): Specify the runtime in seconds after which a warning is to be issued for the batch work processes.

  • Red Threshold for Batch Tasks (Seconds): Specify the runtime in seconds after which an error is to be issued for the batch work processes. 

  • Check Long-Running Work Processes: Select this checkbox to check long-running work processes.

  • Check Work Process Status: Select this checkbox to check work process statuses (in PRIV mode). 

Data Source

Related long-running work processes are retrieved using the SAPControl data provider. 

Result

The result is displayed as a table containing the task type, instance, work process number, status, time, program name, and rating. 

Purpose: This activity plugin checks memory on each instance of the managed system

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes: Red Threshold for used Memory (%) above

Data Source: Memory Statistics data is retrieved using RFC Data Provider

Output Result:

  • Charts: The table shows the Instance name, the Memory Area and the Used memory (%)
  • Logs:
    • Success (Green): All memory areas below threshold
    • Error (Red): Used Memory for <memory area> on instance <instance name> is above the Red Threshold.
    • Error (Red): Activity Memory Statistics can only be executed on ABAP Systems.

 

Purpose: This activity plugin checks number range objects which is greater than buffer filling degree defined by customer, and if the buffer filling percent is over threshold

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes:

  • Buffer filling degree Threshold for Red Rating (%)
  • Buffer filling degree Threshold for Yellow Rating (%)
  • Show only number ranges above (%)

Data Source: Data is retrieving using RFC Data Provider.

Output Result:

  • Charts: Table shows Object name, Percentage of filling degree and status
  • Logs:
    • Success (Green): All number range objects have a filling degree below Yellow threshold
    • Warning (Yellow): <number of objects> number range objects where the filling level exceeds the Yellow Threshold.
    • Error (Red): <number of objects> number range objects where the filling level exceeds the Red Threshold.
    • Error (Red): Activity Memory Statistics can only be executed on ABAP systems.

Purpose: This activity plugin is used in a service level report and allows to report the Response Time Distribution KPI.

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes:

  • Reporting period Period for reporting data:
    • Last week
    • Last 2 weeks
    • Last 3 weeks
  • Reporting granularity Possible values:
    • Total
    • Month
    • Day
  • Display values as Possible values:
    • % of steps
    • Number of steps
  • Dialog Task type checkbox.
  • RFC Task type checkbox.
  • HTTP Task type checkbox.

Data Source:

Output Result:

  • Charts: Table shows the Period, Task Type, Steps and the duration per segments
  • Logs:
    • Success (Green): The table above shows the response time distribution of all Task types for the reporting period <reporting period> in percentage of executed steps.
    • Success (Green): The table above shows the response time distribution of all Task types for the reporting period <reporting period> in number of steps.
    • Success (Green): The table above shows the response time distribution of Task types <selected task types> for the reporting period <reporting period> in percentage of executed steps.
    • Success (Green): The table above shows the response time distribution of Task types <selected task types> for the reporting period <reporting period> in number of steps.
    • Warning (Yellow): No data were found for the reporting period <reporting period>
    • Error (Red): This activity can only be executed for ABAP Systems.
    • Error (Red): This system is not configured for ABAP performance KPI collection.

Purpose: This activity plugin perform check SAP Default Password on ABAP Technical System.

Prerequisites: This Plugin is only for ABAP systems.

Design Time Attributes: No Design time attribute can be defined for this health check.

Data Source: The Check is based on a CCDB Store.

Output Result:

  • Charts: Table with CLient, User, Password Status, Exists, Locked, Rating 
  • Logs:
    • Success (Green): Client change settings of productive client is not modifiable
    • Success (Green): This check is relevant for Production Client only. The current system doesn't have any productive client.
    • Error (Red): Client change settings of productive client 200 allow modifications.

Possible Errors: No CCDB store Exists

Purpose: This activity plugin performs a check on ABAP Short Dumps

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes:

  • Timeframe Source: start timestamp and end timestamp
    • Read Timeframe from Alert
    • Read Timeframe from GP Attributes
    • Specify custom Timeframe
  • Timeframe: Value used only if Timeframe Source is set ti Read Timeframe from GP Attributes
  • Write timestamp as log message: Check flag to specify if the timestamp should be written in the guided procedure log
  • Select the graphic type: Select Table or Bar Chart style
  • Enter the number of rows to display: Maximum number of top logs to display in the output
  • Old Data provider: Flag of using old Data Provider

Data Source: There is an old RFC data provider and a new one. The way data are retrieved can be controlled at design time using a specific attribute.

Output Result:

  • Charts: The table shows the Component name, the Runtime Errors, the Program name and the occurrence of the dumps. !the bar chart show the Top <N> shortdumps per number of Occurrence . 
  • Logs: 
    • Information:<N> Shortdumps occurred in the timeframe <Start time> to <End time>
    • Error (Red): Activity Short Dumps can only be executed on ABAP Systems.

Purpose: This activity plugin checks if SNC is active

Prerequisites: This plugin works only for ABAP systems

Design Time Attributes: No design time attributes can be defined for this health check

Data Source: SNC Status is retrieved using RFC Data Provider

Output Result:

  • Charts: Table shows the System ID, the Instance Name, the SNC status and the timestamp.
  • Logs:
    • Success (Green): SNC is active on instances <instances name>
    • Error (Red): SNC is not active on instance <instance name>
    • Error (Red): Get SNC Status data failed

Purpose: This activity plugin performs a check on transmission requests numbers group by different status on managed system. It checks also if the number of transmission requests with different status is more than threshold defined by the user.

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes:

  • Timeframe Source: Source for reading the evaluation timeframe: Start timestamp and End timestamp. Possible Values are:
    • Read Timeframe from GP Attributes
    • Specify custom Timeframe
  • Timeframe: Time range for searching transmission requests information , the input value should be an integer value and must end with time unit "d" or "h" or "m"
  • Number of messages with status Error: Threshold for number of transmission requests with status Error.
  • Number of messages with status Waiting: Threshold for number of transmission request with status Waiting

Data Source: Transmission Request data is retrieved using RFC data provider

Output Result:

  • Charts: The Table  shows the CLient number, The Error Messages and number, the Number of transmission requests and the Status
  • Logs:
  • Success (green): Less than <N> Waiting transmission requests found in the timeframe from <Start timestamp> to <End timestamp>.
  • Error (Red): More than <N> Error transmission requests found in the timeframe from <Start timestamp> to <End timestamp>
  • Error (Red): Activity SOST Transmission request can only be executed on ABAP systems

Purpose: This activity plugin help to identify errors or delays in spool processing.

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes:

  • Timeframe Source: Source for reading the evaluation timeframe: Start timestamp and End timestamp. Possible Values are:
  • Timeframe: Value used only if Timeframe Source is set to Read Timeframe from GP attributes
  • Select the graphic type: Table or Bar Chart
  • Threshold for Red rating if number of Waiting spool requests exceeds
  • Threshold for Red rating if number of Failing spool requests exceeds
  • Threshold for Red rating if number of Spool requests without output request exceeds
  • Use old data provider Flag

Data Source: There is an old RFC data provider and a new one. The way data are retrieved can be controlled at design time using a specific attribute.

Output Result:

  • Charts: The table shows the CLient, the Error Message and Number, the Number of Transmission requests and the Status. The Bar CHart shows the Number of Successful and cancelled Spool requests per type of Spool requests
  • Logs:
    • Info (Blue): Spool requests created in the following timeframe were evaluated from <start timestamp> to <end timestamp>
    • Success (Green): No Update errors were detected in the timeframe from <start timestamp> to <end timestamp>
    • Success (Green): Number of successful spool requests: xx
    • Success (Green): <N> spool requests without output requests detected in the timeframe from <start timestamp> to <end timestamp>
    • Success (Green): <N> failed spool requests detected in the timeframe from <start timestamp> to <end timestamp>
    • Success (Green): <N> Waiting spool requests detected in the timeframe from <start timestamp> to <end timestamp>
    • Error (Red): More than <N> spool requests without output requests detected in the timeframe from <start timestamp> to <end timestamp>
    • Error (Red): More than <N> failed spool requests detected in the timeframe from <start timestamp> to <end timestamp> 
    • Error (Red): More than <N> Waiting spool requests detected in the timeframe from <start timestamp> to <end timestamp>
    • Error (Red): Activity Spool requests cqn only be executed on ABAP Systems.

Purpose: This activity plugin verify that all standard reorg jobs have been executed successfully.

Prerequisites: This plugin works only for ABAP Systems

Design Time Attributes: No design time attributes can be defined for this health check.

Data Source: Jobs related data is retrieved using RFC data provider.

Output Result:

  • Charts: Table shows the Job names, Program name, Interval, Last Job Execution, Last Job Status, Results of execution and status
  • Logs: 
    • Success (Green): All standard reorg Jobs have been executed successfully at the expected time
    • Error (Red): Problems with standard reorg Jobs were detected
    • Error (Red): No data retrieved. Call to data provider <data provider> failed with Error <error message>
    • Error (Red): Activity Standard Job can only be executed on ABAP Systems

Purpose: This activity plugin checks ABAP System Availability based on System Monitoring  data. It provides a quick overview whether system is available or not at the time of the health check execution

Prerequisites: This plugin work only for ABAP systems.

  • ABAP_SYSTEM_RFC_AVAILABILITY
  • ABAP_SYS_RFC_LOGONGROUP_SPACE
  • ABAP_MESSAGE_SERVER_HTTP_AVAIL

Design Time Attributes:

  • Check System Availability via "RFC Ping"
  • Check System Availability via "ABAP Message Server HTTP Availability"
  • Check ABAP RFC Availability (Logon Group SPACE)

Data Source: Data is retrieved from system monitoring. The ABAP system availability metrics “Check System Availability" via "RFC Ping", "Check System Availability" via "ABAP Message Server HTTP Availability", ABAP RFC Availability (Logon Group SPACE are taken into account).

Output Result:

  • Charts: Table shows Metric name, Status of system availability, Message from the metric, Measured Timestamp
  • Logs:
    • Success (Green): System is available (RFC/HTTP)
    • Success (Green): System is not available via HTTP due to planned downtime (WM = 010)
    • Error (Red): System <SID> is not configured for monitoring
    • Error (Red): System is not available (RFC / ABAP message server HTTP / Logon Groupe SPACE)
    • Error (Red): Data Collection timestamp older than 5 minutes
    • Error (Red): Could not retrieve metric details ABAP_SYSTEM_RFC_AVAILABILITY (From UDM Store)

Possible Errors:

  • Could not retrieve metric details for <metric type>: Metrics are not active for scope
  • No Check selected: No metrics were selected from the design time
  • Activity System Availability can only be executed on ABAP systems: Selected scope is not ABAP system

Purpose: This activity plugin perform check on System Change Settings on ABAP Technical System. This check is only relevant for Production System.

Prerequisites: This plugin is only for ABAP production systems.

Design Time Attributes: None

Data Source: The check is based on a CCDB Store GLOBAL:

  • Group name: SYSTEM-CHANGE-OPTION
  • Alias: SYSTEM-CHANGE-OPTION
  • Sub-alias: GLOBAL-SETTING

Output Result:

  • Charts: None
  • Logs:
    • Success (Green): System change settings of productive system is not modifiable.
    • Success (Green): This check is relevant for Production Systems only. The current system is set to QA System.
    • Error: System change setting of productive system is modifiable !

Possible Errors: The IT Admin Role must be Production System

Purpose: This activity plugin performs check on ABAP System logs

Prerequisites: This plugin works only for ABAP Systems

Design Time Attributes:

  • Timeframe Source: Source for reading the evaluation timeframe: start timestamp and end timestamp. Possible values are:
    • Read Timeframe from Alert
    • Read Timeframe from GP Attributes
    • Specify custom Timeframe
  • Timeframe: Value used only if timeframe source is set to read timeframe from GP Attributes
  • Select the Graphic type: Table or Bar Chart
  • Enter the number of rows to display: Maximum number of top system logs to display in the output. Let it empty if you want them all
  • Use old data provider flag
  • New data provider without text replacement (faster): Select it to use text replacement without text replacement which is faster but log info less detailed.
  • Write timestamp as log message: Select it to display in log section: "The following timeframe was evaluated from <timestamp> to <timestamp> timezone CET"

Data Source: There is an old RFC data provider and a new one. The way data are retrieved can be controlled at design time using a specific attribute.

Output Result:

  • Charts: The table shows the Full message ID, the Type of the System Log Error, the Last Occurrence and the number of Errors. The Bar chart shows the Number of Errors per System Logs
  • Logs:
    • Info (Blue): <N> system log messages were logged in the timeframe from <start timestamp> to <end timestamp>
    • Error (Red): Activity System Logs can only be executed on ABAP Systems.

Purpose: This activity plugin check if Update Process is up and running and if number of update error and update in initial state from the managed system are not exceeding a given threshold.

Prerequisites: This plugin works only for ABAP systems.

Design Time Attributes:

  • Timeframe Source: Source for reading the evaluation timeframe: start timestamp and end timestamp - possible values are:
    • Read Timeframe from GP Attributes
    • Specify custom timeframe
  • Last n Days: Read Data from the last n Days (Default is 1 - for all update errors you can specify a value of 0).
  • Select the graphic type: Graphic type display in output report: Bar Chart or Table
  • Check status of update service: Check if the update service process is up and running
  • Report update errors: Check if the number of update errors is exceeding the given threshold
  • Show Name of ABAP report: Display graphic report update errors
  • Enter the threshold for red rating for updates in error state: Threshold for the number of update errors
  • Report updates in initial state: Check if the number of update in initial state is exceeding the given threshold

Data Source: Data is retrieved using RFC data provider

Output Result: Logs

  • Success (Green): No Update request(s) in errors were detected in the time frame from <start time> to <end time>
  • Success (Green): <N> Update request(s) in errors were detected in the time frame from <start time> to <end time>
  • Success (Green): No Update request(s) in initial state were detected in the time frame from <start time> to <end time>
  • Success (Green): <N> Update request(s) in initial state were detected in the time frame from <start time> to <end time>
  • Success (Green): Update service is active: Update Service is up and running
  • Warning (Yellow): No check selected: At least one check should be selected at design time
  • Error (Red): <N> Update request(s) in errors were detected in the time frame from
  • Error (Red): <N> Update request(s) in initial state were detected in the time frame from
  • Error (Red): Update service is inactive: Update Service is not running
  • Error (Red): No data retrieved. Call to data provider /SDF/CL_GPCR_GET_UPDATE_STATUS failed with error: <error message>
  • Error (Red): Activity Update Status can only be executed on ABAP systems.

Purpose: This activity plugin checks the current Work Processes configuration on ABAP Managed System.

Prerequisites: This Plugin works only for ABAP Systems

Design Time Attributes: Select the graphic type Table or Bar chart.

Data Source: Data is retrieved using SAPCONTROL Data Provider

Output Result: 

  • Charts: The table shows the Instance name, Workprocess Type and Number of Configured Workprocesses. The Bar chart shows the Configured WorkProcesses per Instance name and workprocess type.
  • Logs: 
    • Success (Green): Current Work process configuration is displayed
    • Error (Red): No destination available for ABAP Instance <instance name>
    • Error (Red): Activity Work Process Configuration can only be executed on ABAP systems.
    • Error (Red): No instance defined for this technical system

Purpose: This activity plugin displays the availability status of services for a BOBJ system.

Prerequisites: This plugin works only for BOBJ systems.

Design Time Attributes:

Technical Metric Name: Name of Technical Metric (Default is BOE SERVER STATE CMS)

Data Source: Data is retrieved from system monitoring.

Output Result:

  • Charts: Table shows the server name, the Availability, the Timestamp and the Rating
  • Logs:
    • Success (Green): All BIP Server are Available
    • Error (Red): No BIP Server State Monitoring metrics were found for instance <instance name>
    • Error (Red): Some BIP Server State monitoring metrics could not be collected for instance <instance name>
    • Error (Red): Availability problems detected for instance <instance name>
    • Error (Red): Activity BOBJ Server State can only be executed on BOBJ Systems
    • Warning (Yellow): No BOBJ Central Management Server Instance found for <SID>

Purpose: This activity shall be used in all alert handling guided procedures to display other open alerts for the system, database, instances of the system and hosts.

Prerequisites: Configure the alert and attach it to the GP.

Design Time Attributes: No design time attribute can be defined for this health check

Data Source: Data is retrieved from Alert Management

Output Result:

  • Charts: Table shows the Alert Name, the Category, the Managed Object
  • Logs:
    • Success (Green): No other alerts are open
    • Error (Red): Other open alerts were found

Purpose

You can use this guided procedure plug-in to display the metric values of a configurable system monitoring - or root cause analysis metric for a selectable period in a stacked column chart or line charts.

Prerequisites

  • This plug-in is available as of SAP Focused Run 2.0 FP02
  • The requested metrics are active in the monitoring template.
  • This plug-in works only for single metrics and not for metric groups. As of SAP Focused Run 2.0 FP03, the plug-in supports also metric groups. 
  • The metrics must be numeric.

Attributes

  • Metric1...Metric10: Technical name of the metric to be displayed as defined in System Monitoring Template Management, up to 10 metrics can be entered.
  • Context type: This parameter specifies from which object type to read the metrics. You need to define it in accordance with the metric. Set it as follows:
    • Technical Instance  if you want to display instance metrics
    • Host  if you want to display  host metrics
    • Technical System  if you want to display system metrics
    • Database  if you want to display  database metrics
    • Database Instance  if you want to display  database metrics.
  • Time Frame Source: Source for reading the evaluation timeframe: start timestamp and end timestamp - possible values are:
    • Read Timeframe from GP Attributes
      If you select “Read Timeframe from GP Attributes” you need to specify the timeframe in the GP under Properties – Search Attributes – Free Search Attributes. Press “Add”. Enter Key “TIMEFRAME”. Enter one of the following values: TODAY, YESTERDAY, CURRENT_WEEK, THIS_MONTH, LAST_MONTH, LAST_12_MONTHS
    • Specify custom Timeframe
      If you select “Specify custom Timeframe” you need to fill the plug-in parameter “Last nDays” as explained below
  • Last n Days (Only with Specify Custom Time Frame): Specify number of days examples (7d = last 7 days starting from 00:00)
  • Granularity The granularity in which the data are displayed. Possible values are 15MIN, HOURS, DAYS
    Note: Reduce granularity or timeframe if too many bars are displayed and result becomes unreadable
  • Chart Title: Specify the chart title to be displayed.

Examples:

You would like to display the daily HTTPS and HTTP Response time for the last month in the guided procedure or the result report

  1. Select Properties Search attributes –Free search attributes. ADD KEY “timeframe” and value “LAST_MONTH”.
  2. Create a new activity in your guided procedure using the plug-in “Display metric  time series”.
  3. Rename the Plug-in to “HTTPS and HTTP Response time”
  4. Define the attributes as follows:
    1. Metric1: ABAP_INST_ASR_HTTPS_TOTAL
    2. Metric2: ABAP_INST_ASR_HTTP_TOTAL
    3. Context Type: Technical Instance
    4. Time Frame Source: Read Time Frame from GP Attributes
    5. Granularity: Days
    6. Chart title: HTTPS and HTTP Response time

You would like to display the daily number of short dumps and canceled jobs for the last month in the guided procedure or the result report

  1. Select Properties Search attributes –Free search attributes. ADD KEY “timeframe” and value “LAST_MONTH”.
  2. Create a new activity in your guided procedure using the plug-in “Display metric  time series”.
  3. Rename the Plug-in to “Dumps and canceled jobs”
  4. Define the attributes as follows:
    1. Metric1: ABAP_SYS_SHORT_DUMPS_TODAY
    2. Metric2: ABAP_SYS_BATCHJOBS_CANCEL_5MIN
    3. Context Type: Technical System
    4. Time Frame Source: Read Time Frame from GP Attributes
    5. Granularity: Days
    6. Chart title: Dumps and canceled jobs

Result

The metrics values for the requested time frame  is displayed as a  column chart or line chart.

Purpose

You can use this guided procedure plug-in to display the metric ratings of a configurable system monitoring - or root cause analysis metric for a selectable period in a stacked column chart. This is especially useful if you want to display the availability of a system or or instance over a configurable time interval.

Prerequisites

  • This plug-in is available as of SAP Focused Run 2.0 FP02
  • The requested metrics are active in the monitoring template
  • Currently it works only for single metrics, not for metric groups.

Design-time attributes

  • Metric1: Technical name of the metric to be displayed as defined in System Monitoring Template Management.
  • Context type: This parameter specifies from which object type to read the metrics. You need to define it in accordance with the metric. Set it as follows:

•Technical Instance - if you want to display an instance metric

•Host - if you want to display a host metric

•Technical System - if you want to display a system metric

•Database - if you want to display a database metric

•Database Instance . if you want to display a database metric.

  • Time Frame Source: Source for reading the evaluation timeframe: start timestamp and end timestamp - possible values are:

•Read Timeframe from GP Attributes
If you select “Read Timeframe from GP Attributes” you need to specify the timeframe in the GP under Properties – Search Attributes – Free Search Attributes. Press “Add”. Enter Key “TIMEFRAME”. Enter one of the following values: TODAY, YESTERDAY, CURRENT_WEEK, THIS_MONTH, LAST_MONTH, LAST_12_MONTHS

•Specify custom Timeframe
If you select “Specify custom Timeframe” you need to fill the plug-in parameter “Last nDays” as explained below

  • Last n Days (Only with Specify Custom Time Frame): Specify number of days examples (7d = last 7 days starting from 00:00)
  • Granularity The granularity in which the data are displayed. Possible values are 15MIN, HOURS, DAYS
    Note: Reduce granularity or timeframe if too many bars are displayed and result becomes unreadable
  • Chart Title: Specify the chart title to be displayed.

Examples:

You would like to display the daily ABAP system  availability for the last month in the guided procedure or the result report

  1. Select Properties Search attributes –Free search attributes. Add KEY “timeframe” and value “LAST_MONTH”.
  2. Create a new activity in your guided procedure using the plug-in “Display metric rating time series”.
  3. Rename the Plug-in to “ABAP message Server Availability”
  4. Define the attributes as follows:
    1. Metric: ABAP_MESSAGE_SERVER_HTTP_AVAIL
    2. Context Type: Technical System
    3. Time Frame Source: Read Time Frame from GP Attributes
    4. Granularity: Days
    5. Chart title: ABAP System Availability

You would like to display the daily ABAP  instance availability per instance for the last month in the guided procedure or the result report

  1. Select Properties Search attributes –Free search attributes. ADD KEY “timeframe” and value “LAST_MONTH”.
  2. Create a new activity in your guided procedure using the plug-in “Display metric rating time series”.
  3. Rename the Plug-in to “Instance Availability”
  4. Define the attributes as follows:
    1. Metric: ABAP_INSTANCE_LOCAL_HTTP_AVAIL
    2. Context Type: Technical Instance
    3. Time Frame Source: Read Time Frame from GP Attributes
    4. Granularity: Days
    5. Chart title: Instance Availability

Result

The result is displayed as a stacked column chart.

Purpose

You can use this guided procedure plug-in to display the current metric values of a configurable system monitoring - or root cause analysis metric in a stacked Bar chart or Table.

Prerequisites

  • This plug-in is available as of SAP Focused Run 2.0 FP02
  • The requested metrics are active in the monitoring template

Design-time attributes

  • Metric1...Metric10: Technical name of the metric to be displayed as defined in System Monitoring Template Management, up to 10 metrics can be entered.
  • Graphic Type: Whether to display the metric values in a bar chart (only for numeric metrics ) or a table 
  • Context type: This parameter specifies from which object type to read the metrics. You need to define it in accordance with the metric. Set it as follows:
    • Technical Instance - if you want to display an instance metric
    • Host - if you want to display a host metric
    • Technical System - if you want to display a system metric
    • Database - if you want to display a database metric
    • Database Instance . if you want to display a database metric.

Examples:

You would like to display the current ABAP message server availability in the guided procedure or the result report

  1. Create a new activity in your guided procedure using the plug-in “Display current metric values”.
  2. Rename the Plug-in to “ABAP message Server Availability”
  3. Define the attributes as follows:
    1. Metric: ABAP_MESSAGE_SERVER_HTTP_AVAIL
    2. Context Type: Technical System
    3. Graphic Type: Table

You would like to display the current Instance availability per instance in the guided procedure or the result report

  1. Create a new activity in your guided procedure using the plug-in “Display metric rating time series”.
  2. Rename the Plug-in to “Instance Availability”
  3. Define the attributes as follows:
    1. Metric: ABAP_INSTANCE_LOCAL_HTTP_AVAIL
    2. Context Type: Technical Instance
    3. Graphic Type: Bar Chart

Purpose: This activity shall be used in all alert handling guided procedures to displays current status of related alert and metrics.

Prerequisites: Configure the alert and attach it to the GP.

Design Time Attributes: No design time parameter required

Data Source: Data is retrieved from Alert Management

Output Result:

  • Charts: Table shows the Metric Name, The First, Worst, Last, Min, Max, Last Value and Text.
  • Logs:
  • Success (Green): The current rating of the alert is Green
  • Error (Red): The current rating of the alert is Red

Purpose

You can use this guided procedure plug-in to check whether the system or the system database is compliant to a policy defined in Configuration & Security Analytics.

Prerequisites

  • This plug-in requires a valid CSA policy for the selected scope.
  • Configuration & Change Database data collection is running successfully for the checked system or database
  • The execution of some CSA policies is protected by additional authorization objects. If you want to include such a policy check in your guided procedure, the user executing the guided procedure (e.g. FRN_BTC_GPA) needs to have additionally role SAP_FRN_APP_CSA_PROTECTED

Attributes

Define the following attributes for the plug-in:

  • Show Details: Select this checkbox if you want to see the checked items. Unselect this checkbox if you only want to get a message if the selected system or database is compliant or not and are not interested in the details.
  • CSA Policy: Enter the name of the CSA policy to be checked.
  • Display Only Non-Compliant Items: Select this checkbox to display only non-compliant items. Unselect this check box to display both compliant and non-compliant items.
  • Relevant For: Select whether you want to run the check for the technical system or the related system database.
  • Ignore Policy Validity Check: Select this checkbox to disable the check for the CSA policy name validity.
    The plug-in checks whether the defined CSA policy exists before saving the plug-in configuration. If the policy is not defined in the system where you define the guided procedure it is not possible to save unless you check this flag.
  • Allow precalculated results from Validation Storage: Select this check box if you want to display the policy results from validation storage. This means the policy results could be some days old. This will provide better performance. Unselect this check box if the policy checks should be reprocessed during execution of the guided procedure. If the validation storage contains no results for the policy and the relevant managed object, the checks will be reprocessed anyway.
  • Show Rule: Whether the policy output of the plug-in shall show the column “Rule”
  • Show Valid Since: Whether the policy output of the plug-in shall show the column “Valid since”
  • Check Filter Regex: This is an optional parameter. By default, all checks of the policy are shown. If you would like to restrict the result to certain checks, you can define a regular expression filtering on the check ids.
    Example: 'XYZ.*' (use .* and not *).
  • Sort By: sort the result table by the specified field name
  • Sort order: Ascending or descending
  • Apply Exemptions: If checked, policy exemptions, when exists, will be applied. The check rating will be displayed as grey and the overall rating as green

 

Result

The result is displayed as a table containing the compliance status, landscape, description, configuration item, value, check, rule, and time stamp.

Purpose: Check Total and Used Data Volume for a database from the System Monitoring metric data.

Prerequisites: This plugin works only for HANA, Maxdb, DB2, Sybase ASE and Oracle databases.

Design Time Attributes:

  • Timeframe Source:
    • Specify custom Timeframe
    • Read Timeframe from GP Attributes
  • Timeframe Selection: Last <N> days
  • Threshold for Red rating: Used Volume (%). Default is 77%.
  • Display Data as Line or Bar Chart.

Data Source: Data is retrieved from system monitoring. Metrics names are taken into consideration.

Output Result:

  • Charts: Line Chart shows the Database Size in GB over the Total Data Volume and Used Data Volume. Bar Chart shows the Database size (%): Total Data Volume and Used Data Volume over the timeframe.
  • Logs
    • Success (Green): No Problem with Database size detected for Database <DB Name>.
    • Error (Red): Problem with Database size detected for Database <DB Name>.
    • Error (Red): No Database size found for Database <DB Name> in timeframe <start timeframe> to <end timeframe>.
    • Error (Red): This activity works only for HANA, Maxdb, DB2, Sybase ASE, Oracle and not for <Database Type>.

Purpose

With the plug-in “Execute Custom Operation New” you can  execute host agent custom operations (scripts) on the managed systems hosts.

Prerequisite

You have developed your own custom operations (*.conf files) and deployed them in the /usr/sap/hostctrl/exe/operations.d directory of the relevant host agents

There are two plug-ins:

  • Execute Custom Operation 
  • Execute Custom Operation New

Please use the plug-in "Execute Custom Operation New" and not "Execute Custom Operation" (deprecated)

Currently the plug-in can be only executed for: host, database, technical system of type Abap, Java, Apache Tomcat, BOE, Hana. Other system types are not supported.

The user triggering the corresponding guided procedure in SAP Focused Run (e.g. user FRN_BTC_GPA) needs to have additionally authorization object FRN_CUSTOP with field CUSTOM_OPE = Name of the custom operation that should  be triggered on the managed system hosts. This authorization object is delivered with the roles SAP_FRN_APP_GP_ALL, SAP_FRN_APP_GP_EXE, SAP_FRN_BTC_GPA with predefined custom operation name SAPHostAgent.Ping. Additional custom operation names need to be added.

 

Attributes

The plug-in has the following attributes

  • Operation Name
  • Operation arguments
  • Execution Scope
  • Time Out
  • Wait for Result
  • Helper Class Name
  • Add Summary Log

Operation Name

The name of the custom operation to be executed.

Execution Scope

  • The scope in which the custom operation is to be executed. There are following values:
  • Database host: execute the operation on all (physical) hosts of the DB instances.
  • Technical system: execute the operation on all (physical) hosts of all technical instances.
  • All hosts; execute the operation on all (physical) hosts, that is, on the DB and technical instance hosts.SAP Hana Master Node: execute the operation on the HANA master node only

The scope Central Host is currently not implemented.

Operation Arguments

Operation arguments for the operation in the format:

      argmentName1=${argumentValue1};argumentName2=${argumentValue2}

The argument strings should contain no blanks.

Following arguments are available

·        ${SID} – SID of a technical system

·        ${DBID} – database ID of a database

·        ${INSNR} – instance number of a technical instance (of a technical system)

·        ${DBINSNR} – instance number of a DB instance (of a database)

·        ${TIMESTAMP} – current timestamp

·        ${HDBKEYPORT} – Hana connection port, the value of the ‘connectaddress’ property

·        ${HDBSYSID} – Hana system ID. In an MDC scenario this returns the ID of the system database  while  ${DBID} would return the ID of the tenant database

·        ${TSINST_WORKDIR} – working directory of technical instance

${HDBKEYPORT} is delivered only for a tenant DB in the MDC scenario. See CL_CHECK_LANDSCAPE_UTIL=>GET_HANA_TS_INFO for more.

Examples of operation arguments:

SID=${SID}  

SID=${SID};INSNR=${INSNR}

DBID=${DBID}

DBID=${DBID};INSNR=${DBINSNR}

DBSID=${HDBSYSID};DBPORT=${HDBKEYPORT}

SID=${SID};WORKDIR=${TSINST_WORKDIR}

Depending on system type and Execution Scope there are some constraints and limitation. The plug-in iterates over all “objects” from the specified Execution Scope and attempts to resolve attributes placeholders. DB -related attributes are supported for appropriate scope objects only. Database instance number are not available, if the command is executed for a host, or for a technical system instance. Technical instance attributes are available for technical systems, and not, let’s say, for a database, and only if the execution scope is set to “Technical System”. For a technical system the ${SID} attribute can be used for every scope. However, the ${INSNR} makes no sense, if the command to be executed, let’s say, on the database hosts only.

 

 

Time Out

The timeout parameter, the time to wait until the operation finishes. Ignored, if the command is executed asynchronously.

Wait for Result

whether to wait until the command finishes: Yes (synchronous execution) or No (asynchronous execution)

Helper Class Name

Optional delegate class helper class to which the plugin class delegates the implementation, an instance of IF_CUST_OPERATION_HELPER_IMPL interface. The plugin always delegates to a helper class instance. If not explicitly specified, an instance of CL_GPRC_CO_ARP_CUSTOP_HLP_DEF is created.

A (custom) helper class is mostly responsible for result evaluation and display. There are several helper classes available.

·        CL_GPRC_CO_ARP_DBCONNECT_HLP_N - check ABAP DB Connection

·        CL_GPRC_CO_ARPHDBQUERY_HLP_N – to display a result of Hana query

·        CL_GPRC_CO_ARPHDBLSTUSRS_HLP_N – used to check on user stores of Hana

·        CL_GPRC_CO_ARPHDBHOSTCNF_HLP_N – used to check on host configuration of Hana

·        CL_GPRC_CO_ARP_CSTP_TSINS_IMPL – specific technical instance helper to replace the values of technical instance number and working directory.

Add Summary Log

If the checkbox is checked, a “summary” log messages from this activity will be included into the summary section of the report

Data Source

The data is retrieved via the Host agent data provider:

  • EXE_CUST_OPERATION: Used to execute custom operations.
  • IS_OPERATION_FINISHED: Used to determine whether the operation has finished.
  • GET_OPERATION_RESULT: Used to get the operation result with the operation-ID.

 

Result

Depending on the operation and used plug-in the result is typically displayed as a table with the columns host name, operation, and one or several operations result related columns.

 

Execute Custom Operation Examples

Execute a SQL Statement on a HANA Database

Prerequisite:
HANA user store on Database server hosts contains keys defined as follows:  <Database ID >SAPDBCTRL<Database Port>

  1. Create a folder to store the SQL statements in the host agent  directories of the HANA hosts.
    Example: usr/sap/hostctrl/exe/operations.d/sqlTemplates/
  2. Create a text file that contains the SQL statement and copy it to the new folder
    Example:
    File Name: HANA_SQL_STATEMENT.txt
    File Content: select * from dummy 
  3. Create a custom operation in usr/sap/hostctrl/exe/operations.d  folder.
    Example:
    Filename: FRUN_HDB_EXEC_SQL.conf
    File Content:
    Command: hdbsql -U $[DBID:#required]SAPDBCTRL$[DBPORT] -I /usr/sap/hostctrl/exe/operations.d/sqlTemplates/HANA_SQL_STATEMENT.txt
    Username:$[DBID:#required#tolower]adm
    Description: Execute SQL Query
    ResultConverter: flat
    Platform: Unix
  4. Test on operating system level whether SAP host agent can execute the custom operation successfully.
    Trigger the command /usr/sap/hostctrl/exe  
     ./saphostctrl -function ExecuteOperation -name FRUN_HDB_EXEC_SQL DBID=<Database ID of system database>  DBPORT=<Database Port>
  5. Include the Plug-in “Execute Custom Operation New” in your guided procedure and configure it as follows:
    1. Operation name: <Name of the custom operation without .conf>
    2. Arguments: DBID=${HDBSYSID};DBPORT=${HDBKEYPORT}
    3. Execution Scope:  SAP HANA Master Node
    4. Time Out:  > 10 (depending on the expected runtime of the statement in seconds)
    5. Wait for results: Yes

  6. Run the guided procedure with the following scope:
    Either with the ABAP or JAVA application system that uses the relevant database as system database or with the HANA Database itself as scope.

Result: The SQL statement results will be displayed in the guided procedure and the report.

Check DB Connectivity (R3trans -d)

An operation to test the DB connectivity from an ABAP system via R3trans -D.

·       Operation Name: FRUN_GP_ABAPDBConnect

·       Arguments:            SID=${SID}

·       Execution Scope:  Technical System

·       Timeout:                 30

·       Wait for Result:     Yes

·       Helper Class Name: CL_GPRC_CO_ARP_DBCONNECT_HLP_N

An example of FRUN_GP_ABAPDBConnect.conf custom operation

   Command: echo R3trans -D skipped

   Username:$[SID:#required#tolower]adm

   Description: DB connectivity test via R3trans.

   ResultConverter: flat

   Platform: Unix

Check Hana  <SID> SAPDBCTRL SQL query

An operation to test whether key <SID> SAPDBCTRL is working and if SQL query can be executed for a Hana database.

·       Operation Name: FRUN_GP_HdbCheckSQLConn

·       Arguments:            DBID=${HDBSYSID};DBPORT=${HDBKEYPORT}

·       Execution Scope:  Hana Master Node

·       Timeout:                 30

·       Wait for Result:     Yes

·       Helper Class Name: CL_GPRC_CO_ARPHDBQUERY_HLP_N

An example of FRUN_GP_ABAPDBConnect.conf file

    Command: hdbsql -U $[DBID:#required]SAPDBCTRL -I     /usr/sap/hostctrl/exe/operations.d/custom_operations/FRUN_GP_HdbCheckSQLConn.txt

    Username:$[DBID:#required#tolower]adm

    Description: Execute SQL Query

    ResultConverter: flat

    Platform: Unix

Display keys defined in HDB userstore

An operation list the content of the HANA user store

·       Operation Name: FRUN_GP_HdbListUserStore

·       Arguments:            DBID=${HDBSYSID};DBPORT=${HDBKEYPORT}

·       Execution Scope:  Hana Master Node

·       Timeout:                 30

·       Wait for Result:     Yes

·       Helper Class Name: CL_GPRC_CO_ARPHDBLSTUSRS_HLP_N

An example of FRUN_GP_HdbListUserStore.conf file

    Name: FRUN_GP_HdbListUserStore

    Command: hdbuserstore list

    Username:$[DBID:#required#tolower]adm

    Description: Display location of HDB User Store and available keys

    ResultConverter: flat

    Platform: Unix

Developing a custom helper for Execute Custom Operation

 

Execute Custom Operation plugin is defined with CL_CHECK_EXE_CUST_OPERA_OP check class. It does not perform much work but delegates to the helper - an instance of IF_CUST_OPERATION_HELPER_IMPL interface.  The abstract class CL_GPRC_CO_ARP_CUSTOP_HLP_IMPL perform all the tasks except the result presentation. The CL_GPRC_CO_ARP_CUSTOP_HLP_DEF implements the default generic result’s view:  a simple table where operation results are shown in plain text. It inherits from CL_GPRC_CO_ARP_CUSTOP_HLP_IMPL and provides the default implementation to the method

EVALUATE_DP_RESULT. Its purpose is to ‘evaluate’ the result (e.g. status) and to create the GP’s report.

 

The available helper classes provide further examples for its implementation. For example, CL_GPRC_CO_ARPHDBQUERY_HLP_N parses the result and shows it in a table.

 

For the sake of compatibility with further SAP updates custom helper implementation should only re-implement the ‘presentation’ method EVALUATE_DP_RESULT

Purpose: Check the status of a database via saphostcontrol operations “GetDatabaseStatus, GetDatabaseSystemStatus, GetDatabaseProperties.

Prerequisites: This plug-in is for Technical Systems, Database and Hosts.

Design Time Attributes: Function name: Possible saphostcontrol functions: GetDatabaseStatus, GetDatabaseSystemStatus, GetDatabaseProperties, ListDatabaseMetrics, ListDatabaseConfiguration.

Data Source: Data is retrieved via Host Agent Data provider

Output Result:

  • Charts: Table shows Hostname, Key, Value, Returned Status
  • Logs:
    • Success (Green): All DB components are running
    • Success (Green): Execution of saphostcontrol <function> was successful on <host(s)>. Please review the results.
    • Error (Red): Some DB components have errors.
    • Error (Red): Status of some DB components could not be retrieved.

Possible Errors:

No Database host were found for Database <DBID>. Please check Database definition in LMDB.

Purpose: Check the status of an ABAP or SAP J2EE System   via sapcontrol operations: ABAPGetWPTable, ABAPGetSysWPTable,  GetProcessList, J2EEGetProcessList, J2EEGetProcessList2

Prerequisites: This plug-in works for  technical systems of type ABAP and Java.

Design Time Attributes:
Operation - Possible sapcontrol commands: ABAPGetWPTable, ABAPGetSysWPTable, GetProcessList, J2EEGetProcessList, J2EEGetProcessList2

Data Source: Data is retrieved via saphostcontrol

Output Result:

  • Table displaying the following columns: Instance name, Name, PID, Description, Dispstatus, Text Status, Start Time, Elapsed Time
  • Logs:
    • Success: Operation <xxx> has been executed successfully
    • Error: Operation <xxx> has Failed on some hosts. Communication Error with SDA. No SDA running or no destination available for ABAP Instance

Purpose: This activity plugin perform check on ABAP or JAVA the Expiring Server Certificates.

Prerequisites:

  • This plugin is only for ABAP and JAVA systems.
  • The relevant CCDB data collector should be configured and running.

Design Time Attributes:

  • Enter the threshold for red rating: Number of days before the server certificate expires (error message). 7 days by default.
  • Enter the threshold for yellow rating: Number of days before the server certificate expires (warning message). 60 days by default.

Data Source: The check is performed on CCDB stores located on the Solution Manager.

Output Result:

  • Charts: Table shows Instance Name, Available certificate, Serial number, Expiry date, Status of the certificate
  • Logs:
    • Error (Red): No Certificate data found for <instance> in Change  reporting in the PSE_CERT store (CCDB store not found).
    • Error (Red): <xxx> number of certificates have expired.
    • Error (Red): Permission denied: Content Authorization missing (CCDB stores reading permissions).
    • Error (Red): Store not existing (CCDB store not found).
    • Error (Red): Error - Unexpected exception
    • Error (Red) Number of certificates will expire in less then <xxx> Days.
    • Success: All certificates are valid for more then <xxx> Days.

Possible Errors:

No Certificate data found for instance

Purpose: This activity plugin may be used to check the backup of the Hana database from the System Monitoring metric data.

Prerequisites:

  • This plugin works only for HANA Database
  • The monitoring metrics cited below should be active for the current scope:
    • HDB_BACKUP_AGE_METR_37
    • HDB_EXISTENCE_OF_DATA_BACKUP_34
    • STATUS_OF_MOST_RECENT_DATA_BACKUP_36_HDB

Design Time Attributes: No design time parameter required.

Data Source: Data is retrieved from System Monitoring. The Data Backup metrics name are taken into consideration.

Output Result:

  • Charts: None
  • Logs: 
    • Success (Green): Current Data backup is available
    • Warning (Yellow): DBMS type of <SID> is not an HANA DB, operation aborted
    • Warning (Yellow): No Primary Database defined
    • Error (Red): No Data Backup exists
    • Error (Red): Status of most recent Data Backup is not OK
    • Error (Red): Most Recent Data Backup is older than 1 day
    • Error (Red): No current metrics for Data backup found

Purpose: This activity plugin may be used to check whether the space usage of the HANA database is < than 90%.

The main used case for this plugin is to allow an operator to check that the used space of Hana database System is high or not.

Prerequisites:

  • This plugin works only for HANA DB.
  • The monitoring metrics cited below should be active for the current scope:
    • HDB_HOST_CPU_IDLE_005
    • HOST_CPU_IDLE

Design Time Attributes:

  • Threshold for red rating (%)
  • Timeframe

Data Source: Data is retrieved from system monitoring. The CPU usage metrics name are taken into consideration

Output Result:

  • Charts: Graphic shows the HANA Overall CPU Usage over a given timeframe
  • Logs:
  • Success (Green): No problems with HDB Host CPU usage detected
  • Warning (Yellow): DBMS type of <SID> is not HANA Operation Aborted
  • Error (Red): HDB Host CPU usage is high
  • Error (Red): No Current monitoring metrics for HDB Host Memory usage found.

Purpose: This activity plugin may be used to check HANA long running threads from the System Monitoring metric data.

The main used case for this plugin is to allow an operator to check that the long-running Blocking Situations, Tasks, Statements, Uncommitted Write Transactions or Serializeable Transactions is lower than the threshold.

Prerequisites:

  • This plugin works only for HANA DB.
  • The monitoring metrics cited below should be active for the current scope:
    • HDB_STATISTICS_METRIC_049
    • HDB_STATISTICS_ALERT_096
    • HDB_STATISTICS_METRIC_039
    • HDB_STATISTICS_METRIC_047

Design Time Attributes:

  • Check Long Running Blocking Situation
  • Check Long Running Tasks
  • Check Long Running Statements
  • Check Long Running Serializeable Transactions

Data Source: Data is retrieved from system monitoring. The Long running metrics name are taken into consideration

Output Result:

  • Charts: The Graphic shows the Long Running Threads (Serializeable and Blocking) for a given time range
  • Logs:
    • Success (Green): No <metric-name> were detected
    • Success (Green): No Long running <metric-name> were detected on database
    • Warning (Yellow): DBMS type of <SID> is not HANA, Operation Aborted
    • Error (Red): <metric-name> running for more then <threshold> minutes were detected on database
    • Error (Red): No current monitoring metrics for <metric-name> found on database

Possible Errors: No current metrics for Long Running Thread found

Purpose: This activity plugin may be used to check the HA/DR of the Hana database from the System Monitoring metric data.

Prerequisites:

  • This plugin works only for HANA DB
  • The monitoring metric cited below should be active for the current scope:
    • HDB_AVL_1015_REPLICATION_STATUS

Design Time Attributes: No design time parameter required

Data Source: Data is retrieved from system monitoring. The replication metric name are taken into consideration.

Output Result:

  • Charts: None
  • Logs:
    • Success (Green): System replication is active.
    • Success (Green): System replication is not configured for this database. No system replication check required
    • Warning (Yellow): DBMS type of SQU is not HANA, Operation Aborted
    • Warning (Yellow): No Primary database defined
    • Error (Red): Problems with system replication detected
    • Error (Red): No SR Replication status metrics found for virtual DB <Virtual DB Name> and on Physical primary <Virtual DB Name>
    • Error (Red): No Primary physical database found for virtual DB <Virtual DB Name>

Purpose: This activity plugin may be used to check space usage of the Hana database from the System Monitoring metric data.

The main used case for this plugin is to allow an operator to check that the space usage of the HANA database is < than 90%.

Prerequisites:

  • This plugin works only for HANA DB.
  • The monitoring metrics cited below should be active for the current scope:
    • HDB_EXP_002_DISK_USAGE_ALRT

Design Time Attributes:

  • Threshold for Red rating: Disk usage (%)
  • Timeframe
  • Last N days: Number of days
  • Granularity: 15m/Hour/Day

Data Source: Data is retrieved from system monitoring. The HANA DB Space metrics name are taken into consideration.

Output Result:

  • Charts: Graphic shows the HANA DB disk usage data and log size for a given timeframe
  • Logs:
    • Success (Green): No problem with database disk usage detected.
    • Warning (Yellow): DBMS type of <SID> is not HANA, Operation Aborted
    • Warning (Yellow): No primary database defined
    • Error (Red): Database Disk usage is high
    • Error (Red): No current monitoring metrics for HDB Disk usage found.

Possible Errors: Metrics are not active for scope. No current monitoring metrics for HDB Disk usage found for database <DBSID>

Purpose: This activity plugin may be used to check HANA Used Memory from the System Monitoring metric data.

The main used case for this plugin is to allow an operator to check that the used memory of the HANA database is < than 90%

Prerequisites:

  • This plugin works only for HANA DB.
  • The monitoring metric cited below should be active for the current scope:
    • HDB_HOST_PHYS_MEM_METR_1

Design Time Attributes:

  • Threshold for Red rating: HANA Host Used Memory (%)
  • Timeframe
  • Last N Days: Number of Days
  • Granularity: Minutes/Hour/Day

Data Source: Data is retrieved from system monitoring. The HANA used memory metric name are taken into consideration.

Output Result:

  • Charts: Graphic shows the HANA Database Host Physical Memory Usage (%) over a given time frame.
  • Logs:
    • Success (Green): No Problem with HANA DB Host Memory usage detected.
    • Warning (Yellow): DBMS type of <SID> is not HANA, operation aborted.
    • Error (Red): HANA DB Host Memory usage is high.

Purpose: To check the overall CPU utilization on all hosts of the managed systems from the System Monitoring metric data.

This activity shall be used for the health check gps to check that the overall CPU utilization on all hosts of the managed systems for the last days is below 70%. 

Prerequisites: The monitoring metric cited below should be active for the current scope: CPU_UTILIZATION_5MIN

Design Time Attributes:

  • Threshold for red rating: HANA Host CPU usage (%)
  • Timeframe

Data Source: Data is retrieved from system monitoring. The CPU usage metrics name are taken into consideration.

Output Result:

  • Charts: Graphic shows the CPU Utilization (%) over the given timeframe.
  • Logs:
    • Success (Green): Average CPU utilization was always below <red Threshold> % detected
    • Error (Red): CPU utilization <red threshold> % detected
    • Error (Red): No current metrics for Host CPU utilization found

Purpose: To check disk usage on the hosts of the managed systems.

Data can be displayed in graphic and log message.

Prerequisites: None

Design Time Attributes:

  • Disk usage threshold: threshold on space usage of each file system. Used tu judge if the free space of special file system is enough.
  • Max Retries: Defined how many times we need to try, when error occurred such as connection to system failed.

Data Source: 

Output Result:

  • Charts: Table shows The hostname, Mount path, File system path, Size (GB), Free (GB), Used (GB), file system usage (%), Status.
  • Logs:
    • Success (Green): No File Systems with more than xx% usage detected
    • Error (Red): x File Systems with more than xx% usage detected.
    • Error (Red): Cannot connect to Agent after sometimes tries.

Possible Errors: 

  • No hosts retrieved from the scope <SID> on <Hostname>. 
  • Error Message: Cannot connect to Agent after xx times tries.

Purpose: To check the top CPU processes running on the hosts of the managed systems. Get and analysis usage percent of top CPU process, then display them within graphic and log message.

Prerequisites: This plugin is for Technical Systems, Database and Hosts.

Design Time Attributes:

  • Threshold of CPU usage: Need a % value. Ex: 90 - Threshold of CPU usage is 90%
  • Max Number of tries: How many times we need to try if error occurred such as connecting to hosts failed.
  • Number of top CPU process: Need a Number. Ex: 10 - Top ten CPU processes

Data Source: The CPU process data is retrieved via Host Agent Data provider

Output Result:

  • Charts: Barchart Shows Host / Process with CPU usage (%)
  • Logs:
    • Success (Green): No OS Processes with more then 10% CPU consumption detected
    • Error (Red): Cannot Get Data from Agent - Error occurred when calling LR8GPD8HOST -> GET_DATA() usually because of bad RFC connection to Host.
    • Error (Red): 15 OS Processes with more than 0.1% CPU consumption detected over all Hosts.

Possible Errors: Cannot Get Data from Agent

Purpose: This activity plugin may be used to check JAVA Instance Availability from the System Monitoring metric data.

The main used case for this plugin is to allow an operator to check that the JAVA Instance is still not available before performing any further investigation within the guided procedure. This activity plugin can also be added at the end of the guided procedure to check if the action performed to solve the JAVA Instance Availability was successful.

Prerequisites:

  • This plugin works only for JAVA systems.
  • The monitoring metrics cited below should be active for the current scope:
    • 'JAVA_SCS_ENQUEUE_STATUS'
    • 'JAVA_SCS_MESSAGE_SERVER_STATUS'
    • 'PORTAL_INST_STARTPAGE_AVAILABILITY'
    • 'JAVA_INSTANCE_HTTP_AVAILABILIT'
    • 'JAVA_ICM_STATUS'

Design Time Attributes: No Design time attribute can be defined for this health check

Data Source: Data is retrieved from system monitoring. The JAVA Instance Availability metrics name are taken into consideration.

Output Result:

  • Charts: Table shows the Instance name, System ID, Metric Name, Value, Status
  • Logs:
    • Success (Green): All JAVA Instances are available
    • Warning (Yellow): JAVA Instance Availability can only be executed on JAVA systems
    • Error (Red): Problems with JAVA Instance availability detected
    • Error (Red): System is not configured for monitoring

Purpose: This activity plugin may be used to check JAVA System Availability from the System Monitoring metric data.

The main used case for this plugin is to allow an operator to check that the JAVA System is still not available before performing any further investigation within the guided procedure. This activity plugin can also be added at the end of the guided procedure to check if the action performed to solve the JAVA System Availability was successful.

Prerequisites:

  • This plugin works only for JAVA systems.
  • The monitoring metric cited below should be active for the current scope: 'JAVA_SYSTEM_HTTP_AVAILABILITY'

Design Time Attributes: No Design time attribute can be defined for this health check

Data Source: Data is retrieved from system monitoring. The JAVA System availability metrics name are taken into consideration.

Output Result:

  • Charts: Table shows the System ID, Metric Name, Status, Message, Timestamp collection
  • Logs:
    • Success (Green): HTTP ping to destination was successful, system is available
    • Success (Green): System <SID> is not available via HTTP due to planned downtime
    • Error (Red): System Monitoring Metric JAVA_INSTANCE_HTTP_AVAILABILITY is not configured
    • Error (Red): System <SID> not configured for monitoring.
    • Error (Red): System is not available via HTTP. HTTP ping failed.
    • Error (Red): Data collection time stamp older then 5 minutes
    • Error (Red): Could not retrieve metric details JAVA_INSTANCE_HTTP_AVAILABILITY

Purpose: To list outages recorded by Service Availability Management

Prerequisites: The managed system objects must have an active service definition in SAM.

Design Time Attributes:

  • Number of Reporting Periods: Number of former reporting periods (either months or weeks). Default 3.
  • Include current Reporting Period: Either include current reporting period or not.
  • SLA Relevant: Outage type as checkbox.
  • Not-SLA Relevant: Outage type as checkbox.
  • Confirmed: Outage type as checkbox.

Data Source:

Output Result:

  • Charts: Table shows The Outage Start, end, Duration and Reason.
  • Logs:
    • Success (Green): No outages were detected for the reporting periods from <start period> to <end period>.
    • Success (Green): No SLA relevant outages were detected for the reporting periods from <start period> to <end period>.
    • Warning (Yellow): Unconfirmed outages were detected for the reporting periods from <start period> to <end period>.
    • Error (Red): No service definition exists for <Scope ID>

Purpose: 

Display upcoming planned downtimes

Design Time Attributes: 

o            List planned downtimes for Next n weeks

o             Show Dates and Times in Time Zone: Enter the time zone that is to be used to display dates and times.

Data Source:

Work Mode Management

Result:

The result is displayed in a table that shows the start and end of the planned downtime, the duration in minutes, the category, and the reason.

Purpose

You can use this plug in to retrieve and scan log errors that are generated by the SAP ASE database in file /$SYBASE/$SYBASE_ASE/install/server_name.log. The plug in enables you to customize the location of the log file.

Prerequisites

This plug in works for systems with SAP Adaptive Server Enterprise database

Design Time Attributes

Define the following attributes for the plug in:

  • Time-Frame Source: Specify how the time frame for the evaluation is to be determined. Possible values are:
  • Read Time Frame from Alert: If the guided procedure is started from the Alert Inbox, select this option to read the time stamp from the alert.
  • Read Time Frame from GP Attributes: Select this option to read the time stamp from the guided procedure (step or guided procedure level).
  • Specify Custom Time Frame: Select this option to read the time stamp defined in the Time Frame attribute.
  • Time Frame (Only with Specify Custom Time Frame): Specify the time frame only if you have set the time-frame source to Specify Custom Time Frame. Possible values are:

-              TODAY (current day from 00:00)

-              XXm (last XX minutes)

-              XXh (last XX hours)

-              XXd (last XX days, including a full day)

-              YESTERDAY (previous full day)

-              CURRENT_WEEK (from Monday 00:00 to now)

-              LAST_WEEK (from Monday 00:00 to Sunday 23:59)

  •  Write Time Stamp as Log Message: Select this check box to include the time stamp in the guided procedure log.
  • Root Directory of Log File: Enter the root directory for the log file for example: /sybase
  • Path to Log File: Enter the relative path to the log file. Wildcard characters are supported, for example: ${SID}/ASE-*/install/${SID}.log
  • Report User Errors: Select this checkbox to include user errors in the report (with a severity between 10 and 16).
  • Report Internal Errors: Select this checkbox to include insufficient resources and internal errors in the report (with a severity between 17 and 18).
  • Report Fatal Errors: Select this checkbox to include fatal errors in the report (with a severity between 19 and 26).

Data Source

The plug performs a call to the SDA of the database host  to scan the log file(s)

Result

The result is displayed as a table containing the severity, error number, state, and message.

Purpose: To check whether the ASE Job Scheduler is running from the System Monitoring metric data.

Prerequisites: 

  • This plugin works only for ASE SYBASE DB.
  • The monitoring metric indicated below should be active for the current scope: ASE_DBCTRL_JS_STATUS

Design Time Attributes: No Design time attribute can be defined for this health check.

Data Source: Data is retrieved from system monitoring. The Job Scheduler metrics name are taken into consideration.

Output Result:

  • Charts: None
  • Logs: 
    • Success (Green): SAP ASE DB Job Scheduler Status: <Metric Text>.
    • Warning (Yellow): DBMS type of <SID> is is not ASE DB, Operation Aborted.
    • Error (Red): SAP ASE DB Job Scheduler Status: <Metric State>.
    • Error (Red): No Current monitoring Metrics for SAP ASE DB Job Scheduler Status found.

Possible Errors: SAP ASE DB Job Scheduler Status : <x>, Job Scheduler is not running

Purpose: To check long running processes of the SAP ASE Database 

 

Prerequisites:

This plugin works only for Sybase database.

The monitoring metrics cited below should be active for the current scope:

  • ASE_LONGEST_TX_SID
  • ASE_LONGEST_TX_OTHERS
  • ASE_LONGEST_TX_saptools
  • ASE_LONGEST_TX_MASTER
  • ASE_LONGEST_TX_MODEL
  • ASE_LONGEST_TX_sybmgmtdb
  • ASE_LONGEST_TX_SYBSECURITY
  • ASE_LONGEST_TX_sysbystemdb
  • ASE_LONGEST_TX_sybsystemprocs

Design Time Attributes:

  • Threshold for red rating: if runtime exceeds (seconds)
  • Timeframe
  • Last N Days: Number of days
  • Granularity: Hour / Day / Minutes
  • Select the graphic type: Bar chart / Table

Data Source: Data is retrieved from system monitoring. 

Output Result:

  • Charts: Bar chart or Table shows the Database name and Maximum Runtime
  • Logs:
    • Success (Green): No long running transactions were detected in the timeframe from <Start> to <End>
    • Warning (Yellow): DBMS type of <SID> is not ASE, Operation Aborted
    • Error (Red): Transactions running for more than <Red Threshold>, seconds were detected on databases <database names list, e.g. saptools, master, ...> in the Timeframe from <start> to <end>
    • Error (Red): No current monitoring metrics for ASE Long Running Transactions found.

Possible Errors:

Purpose: This activity plugin may be used to check the space usage of the sybase database from the System Monitoring metric data.

The main used case for this plugin is to allow an operator to check that the space usage of the Sybase database is < than 90%.

Prerequisites:

  • This plugin works only for Sybase database.
  • The Data & Log metrics cited below should be active for the current scope:
  • Data:
    • ASE_FREE_SPACE_PCT_SID
    • ASE_DB_FREE_RATIO_saptools
    • ASE_DB_FREE_RATIO_SYBSECURITY
    • ASE_DB_FREE_RATIO_MASTER
    • ASE_DB_FREE_RATIO_model
    • ASE_DB_FREE_RATIO_SYBSYSTEMPROCS
    • ASE_DB_FREE_RATIO_sybmgmtdb
    • ASE_DB_FREE_SPACE_RATIO_SybSystemDB
    • ASE_DB_FREE_RATIO_OTHERS
  • Log:
    • ASE_FREE_LOG_PCT_SID
    • ASE_FREE_LOG_PCT_GRP_OTHERS
    • ASE_FREE_LOG_PCT_MASTER
    • ASE_FREE_LOG_PCT_MODEL
    • ASE_LOG_FREE_PCT_SYBMGMTDB
    • ASE_FREE_LOG_PCT_SYBSECURITY
    • SYB_LOG_FREE_PCT_SYBSYSTEMDB
    • ASE_LOG_FREE_PCT_SYBSYSTEMPROCS
    • ASE_FREE_LOG_RATIO_SAPTOOLS

Design Time Attributes:

  • Threshold for red rating: Disk usage (%)
  • Timeframe
  • Last N Days: Number of days
  • Granularity: Hours/Days/Minutes
  • Data or Log Space Metrics

Data Source: Data is retrieved from system monitoring. The Log / Data metrics name are taken into consideration.

Output Result:

  • Charts: Graphics shows the Used Data Space (%) over the selected Timeframe
  • Logs:
    • Success: Free Data / Log space for all Databases is bellow <x> %
    • Warning (Yellow): DBMS type of <SID> is not ASE DB, Operation aborted
    • Error (Red): Free Data / Log space for at least one database is above <x> %
    • Error (Red): No Current monitoring metrics for ASE Free Data Space / ASE Log Space found.

Possible Errors: Used Database for at least one Database is above 0 %.

Purpose: To check all OS processes started by SAPControl framework for a given technical system.

Prerequisites: This plugin is only for ABAP and HANA technical systems.

Design Time Attributes: No design time parameter required..

Data Source: Data is retrieved using the SAP Control source.

Output Result:

  • Charts: Table with Instance Name, Status, PID, Process Name, Description, Elapsed time, Start time, Status
  • Logs:
    • Error (Red): No destination available for ABAP Instance <InstName>

Purpose: To display the status of Simple Diagnostics Agents belonging to system or database. This is a prerequisite for most of the following troubleshooting activities.

Prerequisites: This plug-in is for Technical Systems, Database and Hosts.

Design Time Attributes: No design time parameters required

Data Source: Data is retrieved from the Simple Diagnostics Agent.

Output Result:

  • Table Chart: Hostname (Status), Host Agent Name (Availability)
  • Bar Chart: None
  • Logs:
    • Success: All SDA are available - All SDA running on database or system instances are available.
    • Error: Problems with SDA detected - SDA are not available.

Purpose: To check the  status of specific ABAP users in managed System for all clients.

Prerequisites: This plug-in works for ABAP systems

Design Time Attributes:

  • Set Red rating if user or password expires in less than <N> days
  • Set Yellow rating if user or password expires in less than <N> days
  • List of Users (Separated by ";")

Data Source: Data is retrieved using RFC data provider

Output Result:

  • Charts: The table shows the Client, User, User Type, User End Validity, Password End Validity, Locked and Validity Status
  • Logs
    • Info (Blue): Password Validity check has not been performed as passwords will never expire (login / password_expiration_time=0)
    • Success (Green): No problem detected regarding user or password validity for the checked users.
    • Warning (Yellow): Problems detected regarding user validity for the checked users. user validity will expire for at least one checked user in less than <N> days.
    • Warning (Yellow): Problems detected regarding user or password validity for the checked users. Password will expire for at least one checked user in less than <N> days.
    • Error (Red): Problems detected regarding user validity for the checked users. User validity will expire for at least one checked user in less than 20 days.
    • Error (Red): Problems detected regarding user or password validity for the checked users. Password will expire for at least one checked user in les than <N> days.
    • Error (Red): No users provided to be checked
    • Error (Red): No metrics were selected from the design time

Release Notes

SAP Focused Run 4.0 FP02

  • New Activity Plug-in "Display Alerts"
  • New Activity Plug-in "Display OCC dashboard data for multiple systems"

SAP Focused Run 4.0 FP01

  • Enhanced "Configuration & Security Analysis" Plug-in to handle policy exemption, added sorting options and in case of composite policies show the name of the subordinate policies

SAP Focused Run 4.0 SP00

  • New Activity Plug-in "Long Running Jobs (Job & Automation Monitoring)"
  • New Activity Plug-in "ABAP Standard Jobs (Job & Automation Monitoring)"
  • New Activity "Plug-in Aborted Jobs (Job & Automation Monitoring)"
  • Enhanced "Configuration & Security Analysis" Plug-in to filter on checks in a policy

SAP Focused Run 3.0 FP03

  • New Activity Plug-in "Execute Custom Process via SAP Landscape Management"
  • New Activity Plug-in "Aborted Jobs (Job & Automation Monitoring)"
  • Enhanced "ABAP Schedule Jobs" Plug-in to schedule ABAP jobs in all client