Activating early watch report (EWA) for JAVA managed systems in SAP Focused Run

EWAs in Focused Run

In a SAP Focused Run environment, EWAs are not generated on the Focused Run system, but rather at SAP side. Only data from managed systems is collected at the Focused Run side and then forwarded to SAP. And then the EWA is then available in Service Messages at SAP. For accessing the EWAs you can navigate from the launchpad using the EWA Workspace tile. For more details click here.

In the previous blog, it is explained how to setup EWA reporting for SAP ABAP managed systems that connect to SAP Focused Run system. In this blog it will be explained how EWA can be setup for SAP Java based managed systems.

Activating EWA for JAVA Systems

Goto Launchpad and click on the SAP Early Watch Alert Status tile.

In the EWA Status Application first you need to select scope to include all java systems as shown below.

To activate EWA, change under Active column from NO to YES for the respective system.

After Activation status changes as shown below. Refresh after 5 minutes to ensure that the first circle is Green.

To Ensure the EWA activation is properly completed, goto transaction SDCCN on the FRUN system and ensure that the EWA session for respective Java system is registered.

When EWA Data is sent to FRUN and processed, you will see all circles in Green for the respective JAVA system as shown below.

Activating early watch report (EWA) for ABAP managed systems in SAP Focused Run

EWAs in Focused Run

When you have performed Simple System Integration (SSI) for the connected managed system on the Focused Run system, by default SSI itself activates the SAP early watch (EWA) reporting for a managed system, provided the managed system has IT Admin Role defined as Production system. For more information on how to set IT Admin Role read this blog.

For non productive systems you can also manually activate EWA.

Additionally for all ABAP systems (Production and Non-production), you will need to configure SDCCN in managed system so that EWA data is sent to the Focused Run system.

Note: In an Focused Run environment, EWAs are not generated on the Focused Run system, but rather at SAP side. Only data is collected at the Focused Run side and the EWA is then available in Service Messages at SAP. For accessing the EWAs you can navigate from the launchpad using the EWA Workspace tile. For more details click here or here.

Steps for activating EWA for ABAP Systems

STEP 1: Activate EWA on Focused run System

Goto Launchpad and click on the SAP Early Watch Alert Status tile.

In the EWA Status Application first you need to select scope to include all ABAP systems as shown below.

To activate EWA, change under Active column from NO to YES for the respective system.

After Activation status changes as shown below. Refresh after 5 minutes to ensure that the first circle is Green.

STEP 2: Configure SDCCN on Managed System

Once EWA session for an ABAP system is activated, the SDCCN of the respective ABAP system must read the EWA session data from Focused Run system. For more details read OSS note 2359359 – SDCC Enhancement for ABAP Systems Connecting to Focused Run.

  1. For this first create a HTTP destination from the managed ABAP system to Focused Run system using report /BDL/CREATE_HTTP . Provide the following input and execute the report.
    1. HTTP Destination: By default, it shows as SDCC_SID, you’d better change the SID to the real target system id. This is the suggestion, but you can specify any name if you want.
    2. SSL Status(HTTPS): This checkbox means whether you want to use HTTPS for the communication. By default, it will only use HTTP.
    3. Path Prefix: By default, the service used by SDCCN is /sap/bc/sdf/sdcc/. You cannot change this unless you mark the checkbox “Force Mode”.
    4. User Name: FRN_EWA_<FRUN SID> which you have created during the initial setup of FRUN system.
  2. Run report /BDL/CONFIGURE_SDCCN_HTTP to activate SDCCN. Provide the HTTP destination that created in step 2 and change the job user. Only the first check box must be  selected (only on FRUN 1.0 both check boxes must be selected).
    1. The job user must have authorization SAP_SDCCN_ALL

After running this report with above parameters, the SDCC_OSS RFC will be removed from RFC destinations, and the new HTTP destination will be added to RFC destinations.

STEP 3: Create Maintenance Package on SDCCN in Managed System

Now you need to create a maintenance package in transaction SDCCN of managed system.

To Ensure the EWA activation is properly completed, goto transaction SDCCN on the managed system and ensure that the EWA sessions for the managed system is registered.

When EWA Data is sent to Focused Run and processed at the SAP side, you will see all circles in Green for the respective ABAP system as shown below.

Relevant OSS notes

OSS notes:

SAP Focused Run Rule Based Template Assignment

Introduction

When we perform Simple System Integration (SSI) on a managed system , it automatically activates the SAP default monitoring template on the managed system. However, in most of the SAP Focused Run (FRUN) implementation scenarios, we create customer defined monitoring templates (Custom Templates), which we then manually assign/activate on the managed system.

Rule Based Template Assignment is a feature in FRUN by which we can define based on managed system category which custom monitoring template to be assigned and activated directly when we perform SSI on the managed system.

Defining Rule Based Template Assignment

For Rule Based Template Assignment navigate to the FIORI tile Individual Maintenance in the Advanced System Management section of FIORI launch-pad.

In the Individual Maintenance App navigate to the Rule Maintenance by clicking on the button as shown below.

In the Rule Rule Based Assignment Screen, on the left hand side panel, select the specific Managed Object type for which you want to define the Rule Based Template Assignment.

In this blog we take the example of defining a Rule Based Template Assignment for managed system of type SAP ABAP BASIS 7.10 and higher and specify the custom template for System Level monitoring template. So we select Technical Systems upon which the right side panel now gives a list of all product types. In the right side panel we scroll down and select SAP ABAP BASIS 7.10 and higher.

Now we need to define the Rule based on which the Custom Defined Template to be defined. In this blog we take the example that we have defined 2 custom templates one for Production Systems and one for Non Production Systems. So we will need to define rule to assign template based on filters System Type ABAP and IT Admin role defined in LMDB. For more information on this function read this blog.

In the subsequent screen select Maintain Rules.

In the Maintain Rule screen we select the following filters.

Name your Rule and Save.

Similarly you can create Rule ABAP Non production, just ensure to select the following IT Admin Roles.

Now back in the main screen select the Rule you created from the drop down.

And for Template select the custom template you want to select for the assignment.

Add the assignment.

Now click in Continue with Next Step button till you come to the Reconfiguration tab and then close. This will allow you to save your Rule Assignment.

Once you have assigned the ABAP Production and ABAP Non production rules in the main screen you will see the following assignments listed.

After the assignments done, the next time SSI performed on any ABAP system will take up the custom monitoring template as defined in these rules.

In Individual Maintenance system list you can also see whether current assignment is SAP default or Rule Based Template Assignment.