Preparing Focused Run Applications

SAP EarlyWatch Alert (EWA) for ABAP

Task Actions
Prerequisites on the Focused Run system
  • ST-PI SP07 or higher must be implemented
  • Technical User FRN_EWA_<CID> should exist with known password
  • Check Security Guide from the "Technical Users" Section "Technical Users to Authenticate Data Send Requests to the Focused Run System (ABAP)"
  • Job SAP_FRN_EWA_SEND_REPORT should be scheduled as described in the Master Guide.
  • For FP2 implement SAP Note 2524363

Configuration on the Focused Run system

  • To have also an EarlyWatch Alert created for the Focused Run system itself, please setup the data transfer following SAP Note 207223.
  • You must make sure, that the user controlling SDCCN ( i.e. running the step of job /BDL/TASK_PROCESSOR ) is user FRN_BTC_EWA (this user is supplied with the FRUN specific authorizations).
Prerequisites on the managed system
  • EarlyWatch Alert reports are designed for production systems, therefore an automated rescheduled data collection by SDCCN in the managed system is only supported for ABAP systems with a client role “Production”.
  • At minimum ST-PI 2008_1_7xx SP14, ST-PI 740 SP4 or higher shall be implemented (general recommendation is to have latest available implemented)
  • Note: For ST-PI 740 SP4 or ST-PI 2008_1 _7xx SP14 the Collective Correction note must be implemented: SAP Note 2309642
Configuration on the managed system
  • The FRUN Technical User FRN_EWA_<CID> credentials must be known at this step. Refer to the Security Guide.
  • Implement and process the SAP Note 2359359
  • Check created Destination: Open SDCCN Transaction -> Goto -> Settings -> Task Specific -> RFC Destination: you can test the destination here. For the new created destination, the columns "Active" and "to SAP" must be flagged.
Find EWA Reports
  • SAP Note 2319793 - How to check service messages in SAP ONE Support Launchpad
  • When the EWA report is missing in service channel, open a ticket on XX-SER-SAPSMP-IBX
Troubleshooting
  • In case the EWA service data was sent successfully to SAP (check logs of Job SAP_FRN_EWA_SEND_REPORT, or check in Transaction SDCCN on the "done" tab, the log of the corresponding SDCC task), but no report is available in ONE Support Launchpad after 24 hours please open a ticket on SV-FRN-APP-SDD.
  • For managed systems with a poor network connection to Focused Run or for large managed systems, a change of the block size will stabilize the data transfer to Focused Run: implement the SAP Note 2569086 on the managed system.

SAP EarlyWatch Alert (EWA) for Java

Task Actions
Prerequisites on the Focused Run system
  • ST-PI SP07 or higher must be implemented.
  • If ST-PI SP07 could not be implemented, process SAP Note 2507320
Prerequisites on the Focused Run system
  • 'Delete and Replace Service Definitions' (in transaction SDCCN -> Utilities -> Maintain Service Defninitions).
  • Implement SAP Note 2524363   Correct SDCCN for Focused Run
  • Test destination SDCCN_OSS in SDCCN -> Goto -> Settings -> Task Specific -> RFC Destinations. Recreate the destination if required.
  • Job SAP_FRN_EWA_SEND_REPORT should be scheduled as described in the Master Guide.
Configuration on the Focused Run system
  • Set your Java system to "Production System" in LMDB (Attribute “IT-Admin Role”)
  • Execute the Simple System Integration on the Focused Run system for your Java Managed system to finalize the EWA.
Prerequisites on the managed system
  • The CA APM Enterprise Manager Byte Code Injection Agent (BCIA) should be deployed successful in the Java stack and send data to Focused Run over CA APM Enterprise Manager. The managed systems must be successfully setup for system monitoring.
  • Make sure in System Monitoring all metrics are collected

Manual Checks (Optional)

  • The SSI execution adds the non-ABAP system to table FRUNEWANONABAP.
  • Job SAP_FRN_EWA_NON_ABAP reads the table and creates tasks in SDCCN. Therefore, this table can be checked for successful planning of non-ABAP EWAs in Focused Run.
  • The success of the program FRUN_COLLECT_NON_ABAP (Job SAP_FRN_EWA_NON_ABAP) can be checked in transaction SDCCN under tab "To Do" or "Done". In the job log of the program FRUN_DOWNLOADS_REPORT you can check which data has been sent to SAP.
Find EWA Reports
  • SAP Note 2319793 - How to check service messages in SAP ONE Support Launchpad
  • When the EWA report is missing in service channel, open a ticket on XX-SER-SAPSMP-IBX
Troubleshooting

FP02 only:

Issue: in transaction SDCCN, the log for and EWA for a Java system shows the error „No valid service EWALERT FRUN. Reason: You have applied the procedures of SAP Note 2359359 - SDCC Enhancement for ABAP Systems Connecting to Focused Run on the Focused Run system itself.

Workaround:

  1. Transaction SDCCN -> Goto -> Settings -> Task-specific -> RFC Destination -> Settings:
    • Switch to Change Mode
    • For the WebService Destination, uncheck the "Active" column.
    • Choose the Green Hook Continue (Enter) to save your entry
  2. Transaction SDCCN -> utilities -> Maintain Service Definitions: Choose "Delete and Replace Definitions" and continue with "Enter"  and confirm the pop-ups.
  3. Transaction SDCCN -> ToDo Tab:
    • Mark the row of the "Maintenance Package" and Delete it.
    • Choose Create F6.
    • Choose the "Maintenance Package" task and confirm all pop-ups.

 

SAP EarlyWatch Alert (EWA) for BOBJ and Data Services

Task Actions
Prerequisites on the Focused Run system
Prerequisites on the Focused Run system
  • Feature Pack 03 is mandatory for BOBJ and Data Services EarlyWatch Alert generation
  • SAP Note 2653349 - "FRUN Simple System Integration EWA support for SAP BusinessObjects" has to be implemented
  • Test destination SDCCN_OSS in SDCCN -> Goto -> Settings -> Task Specific -> RFC Destinations. Recreate the destination if required.
  • Job SAP_FRN_EWA_SEND_REPORT should be scheduled as described in the Master Guide.
Configuration on the Focused Run system
  • Set your BOBJ and Data Services system to "Production System" in LMDB (Attribute “IT-Admin Role”)
  • You must enter the system number of the SAP Business Objects system in LMDB. You can look up the system number on the “SAP ONE Support Launchpad” in the “System Data” app. In the app, you must display the SAP Business Objects system. The system number is displayed in header section. 
    In LMDB, you need to edit the technical system. In the overview screen, you navigate to the “Support Portal” tab. Choosing “Edit Installation Number and System Number” you can maintain the system number.
    This applies both to Business Objects systems of type SAP Business Objects Cluster and to Data Services systems of type Unspecific Cluster System.
    If you want to include data of the Apache Tomcat Server in the EWA of the Business Objects system, you need to enter in LMDB the system number of the Business Objects system also for the Apache Tomcat Server (although the Apache Tomcat Server does not have a system number). The system number is used by the EWA to identify systems belonging together.
  • Execute the Simple System Integration on the Focused Run system for your Managed system to finalize the EWA.
Prerequisites on the managed system
  • The CA APM Enterprise Manager Byte Code Injection Agent (BCIA) should be deployed successful in the Java stack and send data to Focused Run over CA APM Enterprise Manager. The managed systems must be successfully setup for system monitoring.
  • Make sure in System Monitoring all metrics are collected
Manual Checks (Optional)
  • The SSI execution adds the non-ABAP system to table FRUNEWANONABAP.
  • Job SAP_FRN_EWA_NON_ABAP reads the table and creates tasks in SDCCN. Therefore, this table can be checked for successful planning of non-ABAP EWAs in Focused Run.
  • The success of the program FRUN_COLLECT_NON_ABAP (Job SAP_FRN_EWA_NON_ABAP) can be checked in transaction SDCCN under tab "To Do" or "Done". In the job log of the program FRUN_DOWNLOADS_REPORT you can check which data has been sent to SAP.
Find EWA Reports
  • SAP Note 2319793 - How to check service messages in SAP ONE Support Launchpad
  • When the EWA report is missing in service channel, open a ticket on XX-SER-SAPSMP-IBX

SAP EarlyWatch Alert (EWA) for HANA (only)

Task Action Actions
Prerequisites on the Focused Run system
Prerequisites on the Focused Run system
  • Test destination SDCCN_OSS in SDCCN -> Goto -> Settings -> Task Specific -> RFC Destinations. Recreate the destination if required.
  • Job SAP_FRN_EWA_SEND_REPORT should be scheduled as described in the Master Guide.
Configuration on the Focused Run system
  • Set your HANA system to "Production System" in LMDB (Attribute “IT-Admin Role”)
  • Execute the Simple System Integration on the Focused Run system for your HANA system to finalize the EWA.
Prerequisites on the managed system
  • Newest templates of CCDB should be in place
Manual Checks (Optional)
  • The SSI execution adds the HANA system to table FRUNEWANONABAP.
  • Job SAP_FRN_EWA_NON_ABAP reads the table and creates tasks in SDCCN. Therefore, this table can be checked for successful planning of non-ABAP EWAs in Focused Run.
  • The success of the program FRUN_COLLECT_NON_ABAP (Job SAP_FRN_EWA_NON_ABAP) can be checked in transaction SDCCN under tab "To Do" or "Done". In the job log of the program FRUN_DOWNLOADS_REPORT you can check which data has been sent to SAP.
Find EWA Reports
  • SAP Note 2319793 - How to check service messages in SAP ONE Support Launchpad
  • When the EWA report is missing in service channel, open a ticket on XX-SER-SAPSMP-IBX

Trace Analysis (TA)

Task Actions

Set the HTTP Logging parameter for Trace Analysis

In this manual activity, you maintain a parameter to perform end-to-end root cause analysis of the logs written by Internet Communication Manager (ICM).

  • Add the Following parameter in RZ10 (ABAP) or DEFAULT.PFL (Java): icm/HTTP/logging_0: set to PREFIX=/, LOGFILE=icmhttph.log, FILTER=SAPSMD, LOGFORMAT=SAPSMD2, MAXSIZEKB=10240, FILEWRAP=on, SWITCHTF=month
  • The system can have multiple log files. This is indicated by multiple parameters named icm/HTTP/logging_X, where X is a number starting from 0. Instead of "SWITCHTF=month" you may also configure "SWITCHTF=day". With this setting the icmhttph.log file will be reset every day, instead of once per month, and thus the file size will be kept smaller.
  • Save and activate the profile. Restart the ICM service in transaction SMICM to activate the profile parameter modification.
  • Note: The restart has a business impact and must be scheduled carefully, as ongoing user connections are closed.
  • For more information see SAP Note 1252944

Real User Monitoring (RUM)

Task Actions

Set SAPUI5 parameters for Gateway systems

This task needs only to be executed for Gateway systems

  • SAPUI5 version 1.38.5 or higher
  • Set Parameter icf/accept_front_end_statistic = 1
  • SAP Note 2332545 must be implemented (only if SAP_UI is on 7.50 SP04 or below)

Create RUM user

User FRN_RUM<CID> needs to be created for each network

  • The new user and password needs to be send for each managed system by report /RUM/SEND_PROP2AGENT (FP00) or via RUM Configuration (since FP01).

 

Set HTTP logging for HANA XS

This task needs to be set only for HANA in case XS accesses should be monitored.

  • Start SAP HANA Administration Console -> Configuration -> add the following parameter to the webdispatcher.ini in the profile:
  • icm/HTTP/logging_0 = PREFIX=/, LOGFORMAT=%t %h %u - "%r2" %s %b %L epp[%{sap-passport}i] fesr[%{SAP-Perf-FESRec}i] fesropt[%{SAP-Perf-FESRec-opt}i],  LOGFILE=$(DIR_INSTANCE)/trace/http_fe.log, MAXSIZEKB=25000, SWITCHTF=day, FILEWRAP=on

Advanced Event & Alert Management (AEM)

Task Actions
Create the Background Job  SAP_AEM_METRIC_AGGREGATE_JOB Create and schedule a Background Job using transaction SM36 for the below details to maintain metric aggregate in AEM:
  • Background Job name : SAP_AEM_METRIC_AGGREGATE_JOB

  • Report Program name: AEM_MAINTAIN_METRIC_AGGREGATE (no variant)

  • Background user FRN_BTC_AEM who executes this job should have the role SAP_FRN_BTC_AEM.

  • Start Time: 0:0 am
  • Recurrence interval: 4 hours
Activate the OData Service service /sap/opu/odata/SAP/INBOUNDCONNECTOR/

Activate an oData service in transaction IWFND/MAINT_SERVICES:

  • Select Technical Service Name: INBOUNDCONNECTOR
  • Select ICF Node, select Activate
  • System Aliases, select Add System Aliases
  • Virtual Host: DEFAULT_HOST

- Identifier: INBOUNDCONNECTOR_0001 (F4)
- SAP System Alias: LOCAL
- Select Default System

Note: Technical user who executes the above oData service should have role SAP_FRN_AEM_UMD_ALR.

Application License Management (ALM)

Task Actions
Check ST-PI Prerequisites
  • Ensure that the SP Level for ST-PI is >= Release of May 2017

Integration & Cloud Monitoring

Task Action
Troubleshooting
  • Issue: Advanced Integration Monitoring metrics collected from on premise systems by the Simple Diagnostics Agent (SDA) are not visible. The logs of the SDA show the following error: "com.sap.solman.agent.cfwk.collect.AbstractCollector unexpected exception for collector FMP.EXM_ABAP_DPAPAR_000_ABAP_JOBS com.sap.solman.agent.cfwk.PushException: HTTP POST request failed: 500"
  • Reason: The user FRN_EXM_<CID> – generated by SSI on the FRun system – is missing an assignment of the profile for PFCG role SAP_FRN_EXM.
  • Workaround: Make sure to follow the security guide. Especially cross-check that the relevant user (like FRN_EXM_<CID>) has the expected role assigned, and that in PFCG transaction everything is fine role SAP_FRN_EXM