Automated System Health Check

The automated system health check performs several health checks on 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.

With Focused Run FP2 SAP delivers a predefined health check guided procedure with the name "Regular System Health Check for ABAP Systems".

It covers ABAP availability, performance, exceptions as well as host checks. It can be executed as is or easily customized and enhanced by other activities which are available in the plug-in repository. For example, you could add HANA database checks or include measured system availability and outages from Service Availability Management into the health check.

The automated system health check has been implemented using the capabilities of the guided procedure framework.

Guided Procedure Framework Overview

The guided procedure framework in Focused Run provides an easy way to document and optionally automate reoccurring operational activities in guided procedures. These guided procedures help the user to execute reoccurring administrative activities or alert reaction procedures in a guided and reproducible way. In addition, it is possible to automate the activities inside guided procedures and to execute them automatically without or minimal manual involvement.

Guided procedures help to reduce TCO and improve IT operations quality through:

  • Step-by-step execution
  • Detailed activity description
  • Central access to required managed system functions
  • Automation
  • Logging of every activity
  • Predefined content that can be customized

A guided procedure consists out of 1 or several steps. Each step has 1 or multiple activities. The following different activity types are supported:

  • Manual activities consist out of a description, a documentation text that describes detailed what the user must do and optionally a context sensitive navigation link into the relevant application in Focused Run or the managed system. The user processing manual activities can read the documentation, open the navigation link to jump into the relevant application to execute the activity. Once the activity is executed the user needs to document this by changing the status and optionally writing a comment.
  • Automated or Plug-In activities. Automated activities execute certain predefined tasks automatically in background. Once executed they return a log message indicating success or failure of the activity and optionally a table, or other graphics with more details. Automatic activities can be triggered by a user. Guided procedures with automatic activities can be executed fully automatic in background. SAP delivers a set of plug in activities that can be customized and plugged into customer defined guided procedures. It is also possible to develop customer specific automated activities in ABAP and plug them into own guided procedures
  • Custom step activities or Plug-in Step activities are Webdynpro applications that can be reused in guided procedures to execute complex tasks which require user input. Currently no custom step activities or Plug-in step activities are delivered with Focused Run FP2 but it is possible to define customer specific custom steps.

The result of a guided procedure execution can be exported into a HTML result report and sent via e mail.

Guided Procedures for Advanced System Management (ASM)

Guided Procedures for Advanced System Management allow to define and automate regular administrative tasks.

One example for this is the "Regular System Health Check for ABAP Systems" guided procedure in Focused Run FP2. It performs several health checks on 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.

 The "Regular System Health Check for ABAP Systems" covers ABAP availability, performance, exceptions as well as host checks. It can be executed as -is or easily customized and enhanced by other activities which are available in the guided procedure plug-in repository. For example, you could add HANA database checks or include measured system availability and outages from Service Availability Management into the health check.

Guided Procedures for Advanced Event & Alert Management (AEM)

Guided Procedures for Alert Management allow to define and automate alert reactions in Focused Run FP2.  They usually consist out of problem context collection activities and out of manual activities that guide you through the resolution of the alert. The problem context collection activities can be triggered automatically as soon as the alert was raised. They collect information like alert status, system and database status details. You can easily add custom operations that check for example database connectivity, the availability of certain processes on OS level or execute SQL statements for analysis. The results of the problem context collection are available in a result report directly accessible from the related alert in alert inbox. 

The manual activities guided you through the analysis and resolution of the problem. For example, they provide a navigation link to the file system browser that allows to analyze the relevant log and trace files of the managed system without OS level access. Focused Run FP2 provides alert reaction procedures for ABAP and Java instance availability alerts. They can be used out of the box or enhanced with customer specific activities.

 

Automatic System Health Check

The "System Health Check for ABAP Systems" is a guided procedure that is delivered with Focused Run. It performs several health checks on 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.

The "System Health Check for ABAP Systems" covers ABAP availability, performance, exceptions as well as host checks. It can be executed as-is or easily customized and enhanced by other activities which are available in the guided procedure plug-in repository. For example, you could add HANA database checks, or include measured system availability and outages from Service Availability Management.

The following section describes how to schedule the health check so that it runs automatically in background and how to edit it's content.

How to plan the automatic execution of guided procedures (e.g. System health Check) automatically in background.

(This section is valid as of FRUN 1.0 FP03.  For FRUN 1.0 FP02 please refer to the section below)

Guided procedures with automatic activities like the " System Health Check for ABAP Systems " can be executed automatically in regular intervals. After the execution, a result report is sent out to defined receivers.

Prerequisites:

  • Apply SAP Note 2566836 in Focused Run.
  • The managed ABAP systems for which the guided procedures are scheduled should be on ST-PI 740 SP4 /5 + SAP Note 2434114 or ST-PI 740 SP6.
  • Create service user FRN_BTC_GPA or similar per Focused Run security guide. The user needs to have a valid e mail address to be able to send out e mails. Define that user FRN_BTC_GPA should be used for guided procedure background processing as explained in the Focused Run Master Guide. This activity needs to be carried out only once.
  • The guided procedure that is running in automatically in background needs to consist primarily out of automatic activities. Manual activities or Custom UIs will not be executed. The guided procedure must be active.
  • Define recipient lists in Central Notification Management. The recipient lists shall contain the e mail ids or FRUN user ids of the recipients who shall receive the guided procedure execution reports

To plan the automatic execution of a guided procedure in background, proceed as follows:

  1. Open the Focused Run Launchpad.
  2. Select Advanced System Management, then Guided Procedure Catalogue
  3. Select the guided procedure to be planned. (for example, “System Health Check for ABAP Systems”)
  4. Select "Create Plan à Background Schedule (Simple) if you want to schedule the execution of a guided procedure for some systems and do not need to define e mail templates.
    Select "Create Plan à Background Schedule (Expert) if you want to
    • schedule the execution of a guided procedure for a high number of systems and want to control the job runtime and how many child jobs shall run in parallel
    • define specific e mail templates
    • use a customer specific customization class that reformats the e mail body in rich text format and allows to do advanced receiver determination
  5. Enter the following data in Background Schedule (Simple) mode:
    • Overwrite optionally the default plan name or add a description
    • Overwrite optionally the default job name
    • Choose whether the batch job should be executed immediately or at a certain start date and time and if the job should run once or recurrently.
    • The section “Scope Details” allows to determine the systems for which the guided procedures shall run. The parameters act as a filter that filter out relevant systems. Fill the section as follows: 
      • Customers and data center: If you want to restrict the execution of the guided procedures to systems assigned to certain customers and data centers, fill the data accordingly. If this restriction is not required, leave customer network and data center empty.
      • Extended System ID:  If the guided procedure shall be executed only for certain systems, and the systems cannot be filtered otherwise, enter the system ids of these systems here. Otherwise you can keep this entry empty.
      • IT Admin Lifecycle Statuses: Here you can restrict on systems that have a certain life cycle status. For example, choose Active if you want to schedule the guided procedure only for active systems.
      • IT Admin priorities: Here you can restrict on systems that have a certain priority. For example, choose “Very High” if you want to schedule the guided procedure only for systems with priority “Very High”.
      • IT Admin Roles: Here you can restrict on systems that have a certain role. For example, choose “Production System” if you want to schedule the guided procedure only for production systems and not for QA and Dev.
  • Press button “Show systems” if you want to get a preview of the systems, for which the guided procedure will be scheduled. 
  • Select the corresponding receiver recipient list containing the e mail recipients that should receive the e mail with the guided procedure result report. Recipients in “Customer independent” recipient lists will receive the e mail in all cases. Recipients in “Customer Network specific” recipient lists will receive the e mail only for systems which are assigned to the same customer network.
  • Select the corresponding admin recipient list containing the e mail recipients that should receive an e mail in case the guided procedure background processing jobs fail. Recipients in “Customer independent” recipient lists will receive the e mail in all cases. Recipients in “Customer Network specific” recipient lists will receive the e mail only for systems which are assigned to the same customer network.
  • Press button “Preview” if you want to get a preview of the guided procedure processing jobs that will be scheduled and the respective managed system.
  • Press button “OK” to create a new guided procedure background processing plan and schedule the relevant jobs.
    •  System Type: Choose the system type that fits to the guided procedure. Example: If you want to schedule the guided procedure “System Health Check for ABAP Systems”, choose system type ABAP.
    • Database Type: If required, choose the database type so that the guided procedure shall be scheduled only for systems with a specific DBMS type.
  1. In Background Schedule (Expert) mode you can additionally define the following data:
    • Customization Class: Select a customization class if you have the following needs:
      • The e mail body of the result e mail should be generated in HTML format and contain graphical elements
      • You need to determine the recipients for the result e-mails per custom rules
        SAP delivers the customization class “CL_CUSTOM_EMAIL_BODY” that overwrites the e mail body with a preview of the guided procedure activities and their status.  Using this customization class, you can see the status of the different activities directly in the e mail and need to open the attached result report only if you are interested in the details.
        With ABAP knowledge you can also create your own customization class. It needs to inherit from class CL_GPA_PLAN_CUSTOMIZATION. You need to redefine method “GET_EMAIL” if the guided procedure e mail with the result reports attached must contain special html content like graphics, tables, logos.
        You need to redefine method GET_RECIPIENTS_FOR_SCOPE if you have advanced needs to determine the right recipients for guided procedure reports for specific systems.
  •  Job Control: Here you can define advanced settings to control the background execution of guided procedures.

How-To Guide

How to schedule the system health check guided procedure(s) automatically in background (only relevant for FRUN 1.0 FP02)

Prerequisites:

  • Create user FRN_BTC_GPA as per security guide
  • Apply SAP Note 2566836 in Focused Run FP02
  • Managed ABAP systems subject to health check should be on ST-PI 740 SP4 /5 + SAP Note 2434114 or ST-PI 740 SP6

Guided procedures with automatic activities like the "Regular System Health Check for ABAP Systems" can be executed automatically in regular intervals. After the execution, a result report is sent out to defined receivers.

To achieve the automatic execution of guided procedure in background you must define a variant for the ABAP report "PR_GPA_EXEC_PLANNER" and schedule this report with the variant in regular intervals.

How to define the variant

Call transaction SE38. Enter report "PR_GPA_EXEC_PLANNER". Select Execute.

Fill the parameters as follows:

  • Guided procedure ID: Select the guided procedure to be executed automatically.
  • Customers and data center: If you want to restrict the execution of the guided procedures to systems assigned to certain customers and data centers fill the data accordingly. If not leave customer network and data center empty.
  • Long SIDs:  If the guided procedure shall be executed for certain system ids, enter the system ids of the system here. Otherwise leave empty.
  • System type:  Enter the system type of the systems for which you want to execute the guided procedure. Choose the system type which fits to the contents of the guided procedure. For example, the "Regular System Health Check for ABAP Systems" can be executed only for ABAP systems and it does not make sense to schedule it for JAVA systems.
  • IT Admin attributes: whether the guided procedures shall be executed only for production systems, test systems etc.
  • Types of database: Here you can define whether the GP shall be executed only for systems with certain system database DBMS types (e.g.  systems with HANA Database or systems with SAP ASE Database)
  • The email parameters allow to define recipients of the result report and recipients in case the report execution failed. You can also define which Se61 texts to be used as e mail templates.
  • The background job control parameters define how many child jobs can be processed in parallel, how many systems per job and the maximum permitted duration after which unprocessed child jobs are canceled. You can normally keep the default settings here.

Save the variant.

Execute the report online with flag "Simulation mode" checked. It will provide an overview about for how many systems the health check will be processed   and how many child jobs will be scheduled.

 

How to define the guided procedure execution job

Call transaction SM36. Create a new job with report   "PR_GPA_EXEC_PLANNER" and the previously created variant. The job should run under user "FRN_BTC_GPA".  Schedule the job with the required periodicity.

 

How to define the variant

Call transaction SE38. Enter report "PR_GPA_EXEC_PLANNER". Select Execute.

Fill the parameters as follows:

  • Guided procedure ID: Select the guided procedure to be executed automatically.
  • Customers and data center: If you want to restrict the execution of the guided procedures to systems assigned to certain customers and data centers fill the data accordingly. If not leave customer network and data center empty.
  • Long SIDs:  If the guided procedure shall be executed for certain system ids, enter the system ids of the system here. Otherwise leave empty.
  • System type:  Enter the system type of the systems for which you want to execute the guided procedure. Choose the system type which fits to the contents of the guided procedure. For example, the "Regular System Health Check for ABAP Systems" can be executed only for ABAP systems and it does not make sense to schedule it for JAVA systems.
  • IT Admin attributes: whether the guided procedures shall be executed only for production systems, test systems etc.
  • Types of database: Here you can define whether the GP shall be executed only for systems with certain system database DBMS types (e.g.  systems with HANA Database or systems with SAP ASE Database)
  • The email parameters allow to define recipients of the result report and recipients in case the report execution failed. You can also define which Se61 texts to be used as e mail templates.
  • The background job control parameters define how many child jobs can be processed in parallel, how many systems per job and the maximum permitted duration after which unprocessed child jobs are canceled. You can normally keep the default settings here.

Save the variant.

Execute the report online with flag "Simulation mode" checked. It will provide an overview about for how many systems the health check will be processed   and how many child jobs will be scheduled.

Make sure that the flag "Simulation Mode" is disabled in the report variant  that is used by the batch job

How to define the guided procedure execution job

Call transaction SM36. Create a new job with report   "PR_GPA_EXEC_PLANNER" and the previously created variant. The job should run under user "FRN_BTC_GPA".  Schedule the job with the required periodicity.

Result: The guided procedure execution job will run at the right time for the defined guided procedures

 

How to edit the contents of the system health check

You can customize the content of the health check per your needs. For example, you could add HANA database checks or include measured system availability and outages from Service Availability Management into the health check. For some health check plug-ins, you can change their behavior for example if they should check for the last day instead of last 3 or that the result should be displayed as a bar chart instead of a table.

 

How to Create a customer specific health check Guided Procedure

Create a customer specific Health Check guided procedure:

  1. Open the Focused Run Launchpad.
  2. Select Advanced System Management, then Guided Procedure Catalogue
  3. Select the guided procedure "Regular Health Check for ABAP Systems"
  4. Optionally: Set the "Hidden" flag if the SAP delivered template should not be used any more.
  5. Select "Create by Copy"
  6. Enter the following data:
  • Specify a meaningful name and description for the GP or keep the existing one
  • Specify a customer-specific ABAP package with the right transport layer if you want to transport the guided procedure from Focused Run development system to QA and production system. The package is required to know in which transport route the GP will be released. If you don't want to transport the guided procedure, you can choose "Temporary Package".
  • Set "Productive" flag, if the guided procedure is to be transported to a production system. If the GP is for testing purposes on the local system, or will be imported into a test system manually, do not set the flag.
  • Select OK

How to Edit a customer specific health check Guided Procedure

Edit a customer specific Health Check guided procedure:

  • Open the Focused Run Launchpad.
  • Select Advanced System Management, then Guided Procedure Catalogue.
  • Select the Guided Procedure, then select the "Edit" Button

Add a step: To add a step, click on New, and select the step type in the menu, as shown below. You can also reuse an existing step. A new step will be inserted below the selected step, in the Steps tree. Step types can be standard, parent, plug-in or complete. For the automated health check use case only standard steps are relevant.

Create Help text:

The step help text provides detailed information about each step, such as what is checked, and what will happen in the background. The "New" button in the help text section opens the "Create New Document" Pop up, which allows you to define documentation for a step or an activity. You can create a new HTML document or upload a PDF. If the HTML result report needs to show also the documentation in line, choose HTML.

Add Complete Step: The Complete step is the last step in the guided procedure, which provides an overview of the execution status of the previous steps. If the guided procedure is being executed manually, the HTML result can be generated only from the complete step. If you guided procedure does not have a complete step yet, add it.

Remove a Step: Select the step and click on Remove to remove obsolete steps.

 

Add an Automatic Activity:

  • Select the relevant Standard Step.
  • Select "Automatic Activity", select "New".
  • Choose "Select a Plug-in" and select the required plug-in from the value help.
  • Rename the activity
  • Maintain the plug-in attributes per your requirements
  • Select "OK"
  • While the new activity is selected, select "Help Text" and "New"
  • Enter a name for the documentation
  • Enter a suitable documentation text
  • Select "Save"
  • Use the buttons "Move up or Move down" to change the order of activities in the help

The following activity types are supported by Guided Procedure Framework, however only Plug-ins should be used in the automatic health check:

 

Type Description
Manual Simple manual activities consist of a description and either no navigation link, or a navigation link to a UI in Focused Run, in the managed system, or an external link. The navigation link can be configured.
Custom UIs Some tasks to be carried out in the step of a guided procedure require input values and a more complex logic in the backend. Such steps usually need their own user interface for the user to input values. These tasks can be performed by custom steps. A custom step in a guided procedure is a step that contains its own user interface and own logic which is implemented in a backend web dynpro component.
Automatic Automatic activities are activities that can be carried out in a Guided Procedure without user interaction or manual steps. If you have developed a suitable automatic activity, you can include it in the health check.
Plugins Plug-ins are automatic activities that can be customized during Guided Procedure creation time. SAP delivers many health check Plugins to that can be easily customized and included into the health check Guided Procedure.

Remove Activity: Select the relevant activity and select "Remove" to remove the relevant activity if it is obsolete.

Change Activity: Select the relevant activity and select "Edit". Change the plug in attributes per your requirements.

Set the Guided Procedure HTML Report Configuration:

  • In the Guided Procedure Maintenance UI, Select the "Report Configuration" button.
  • Here you define which options are visible to the end user when creating the HTML report, and you define which options are selected by default: GP Structure, Include Step and Activity Status Information, Include Help Documentation, Include Navigation Links, Include Log Messages, Include Summary and Statistics.
  • Select "OK" and "Save"

How to Activate a customer specific health check Guided Procedure

  • Select button "Check". Fix errors reported by the check.
  • Select button. "Activate"

 

How to test the customer specific health check Guided Procedure:

  • Test the guided procedure against a test system using ABAP report "PR_GPA_EXEC_PLANNER" as explained above.
  • Verify that you receive an email with the HTML report attached.
  • Check the content of the HTML report

How to transport the customer specific health check Guided Procedure

If the health check guided procedure was edited in a development system and needs to be transported to QA and production systems :

  • Press button "Transport".
  • Include the guided procedure into a new transport request or choose an existing.
  • Release and import the requests per your transport rules.