Frun Guide
Frun Guide
Frun Guide
Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when they
are surrounded by body text, for example, SELECT and INCLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as
they appear in the documentation.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system.
Caution
Before you start the implementation, make sure that you have the latest version of this document that is
available at https://help.sap.com/viewer/p/FRUN.
7 Appendix ........................................................................................................................................ 55
7.1 OData and SICF services activated by STC01 task lists ................................................................... 55
7.1.1 SAP_GW_FIORI_ERP_ONE_CLNT_SETUP with variant SAP&FRUN_INIT .................... 55
7.1.2 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_ASM ...................................... 58
7.1.3 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_AUM ...................................... 59
7.1.4 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_AEM ..................................... 60
7.1.5 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_CSA ....................................... 61
7.1.6 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_AIM ....................................... 61
7.2 Automatic scheduled Background Jobs ............................................................................................62
Purpose
This master guide is the starting point for the technical implementation of Focused Run for SAP Solution Manager
(Focused Run; also: FRUN). It mainly contains cross-scenario implementation information.
Note
You find the latest information about the technical implementation of Focused Run at
https://help.sap.com/viewer/p/FRUN
As a reminder, always download the master and security guide from this location. They are subject to
regular updates.
Finally, make sure to strictly and precisely follow this document to design your system landscape, to
define your implementation planning, and above all, to complete the configuration with the mandatory
settings, in the required order.
The master guide references related documents that include further details, like:
• Installation guides for single software units
• SAP Notes
• Further configuration documentation
Constraints
The primary focus of this master guide is to describe the overall technical implementation of Focused Run, rather
than to deeply explain every single component. This means that additional software dependencies might exist
without being mentioned explicitly in this document. You can find more information on component-specific
software dependencies in the corresponding installation guides.
ITCal IT Calendar
TA Trace Analysis
Focused Run provides improved solution operations features relevant for the run phase of a managed system
landscape.
The main use cases of Focused Run and their corresponding key areas are as follows:
Advanced User Monitoring (AUM) Monitoring of user experience across system and
technology stacks. In this use case, the functionality
Advanced System Management (ASM) Effectively and efficiently manages many systems,
databases and hosts. Focus is on functionality such
as:
• System Monitoring (SysMon)
• Metric Forecasting and System Anomaly
Analysis
• IT Calendar (ITCal)
• Work Mode Management (WMM)
• Service Availability Management (SAM)
• System Health Check
• SAP EarlyWatch Alert (EWA)
• License & Maintenance Certificate Management
• Guided Procedures including the Automated
System Health Check for ABAP Systems
It covers the complete scope of managed system
types based on SAP and non-SAP technologies.
Advanced Configuration Monitoring (ACM) Analyzes configuration and security settings across
systems and technologies. Enables you to browse
and investigate high volumes of configuration items
in complex system landscapes. Validates technical
and security configuration settings against customer-
specific target configuration templates. Supports
configuration settings of system, database, and host.
Advanced Event and Alert Management (AEM) Provides enhanced management capabilities for
events and alerts based on monitoring use cases as
Advanced User Monitoring or Advanced System
Monitoring. Comes with efficient and mass volume
enabled alert dashboards, alert inbox and alert detail
displays. Provides the possibility to trigger alert
reaction procedures that help you to analyze and
Advanced Integration Monitoring (AIM) Monitoring of data exchange across system and
technology stack. It includes:
• Monitoring of single interface calls / messages
for orchestrated and non-orchestrated on-
premise and cloud environments
• Monitoring of single exceptions for on-premise
and cloud environments
• Monitoring of SAP PI-related issues (single PI
channels, single PI messages)
• Monitoring of hybrid scenarios containing loud
and on-premise components
• Monitoring of connections between on-premise
and cloud components
Advanced Root Cause Analysis (ARA) Deep detailed root cause analysis capabilities tailored
to your needs. It includes:
• System Analysis
• Trace Analysis
• File System Browser
More Information
Find all information about Focused Run 2.0 use cases in the following:
• SAP Help Portal
SAP Help Portal bundles access to SAP product documentation and related information, such as SAP Notes,
product availability information, and community content.
For Focused Run 2.0 information, access the help portal at: https://help.sap.com/viewer/p/FRUN
• SAP Support Portal)
The SAP Support Portal provides access to task-driven support resources in an intuitive interface. On the
products pages, customer can find information such as SAP Knowledge Base Articles, SAP Community
questions and blogs, Guided Answers, and product documentation, as well as additional featured content
straight from product experts at SAP.
You access the SAP Support Portal at:
https://support.sap.com/en/alm/focused-solutions/focused-run.html
The implementation of Focused Run requires you to address the following items, described in detail in the next
chapters:
1. Define implementation (such as scope, hardware and software requirements, release restrictions)
2. Plan landscape (for the relevant use cases)
3. Check installed SAP HANA revision
4. Install and prepare the SAP NetWeaver ABAP system (including Focused Run add-on)
5. Configure the Focused Run Application Foundation
6. Configure the relevant Focused Run use cases
IMPORTANT NOTICE: The sapadm password defined while installing the SAP Host Agent in the managed
landscape is required to be able to perform the Focused Run configuration.
During an implementation project, take the following aspects into account to make the right decisions. Here the
major aspects:
Scope and Requirements Determine the scope of your For more information see Focused
Focused Run implementation Run Use Cases [page 8]
Hardware and Software Check the required minimum SAP SAP Note 2354930
Prerequisites NetWeaver ABAP version
Security Planning Plan the user management and For more information see Focused
infrastructure security Run Security Guide
For more information about planning topics, not covered in this guide, refer to the following content:
Performance https://www.sap.com/about/benchmark.html
* Note
Focused Run for SAP Solution Manager is priced based on used SAP HANA memory in Gigabyte (“GB”)
with volume tiers. SAP provides customers with the SAP HANA used memory calculation as well as with
the hardware sizing for the Focused Run project as a follow up of the Focused Run positioning workshop.
For more information, see https://support.sap.com/en/alm/focused-solutions/focused-run.html -> Get
Focused Run.
The following table lists further useful links on SAP Service Marketplace:
You can find more information about the prerequisite components in the following documents:
Title Location
Read the following SAP Notes before you start the installation. These SAP Notes contain the most recent
information on the installation, as well as corrections to documentation.
Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Support Portal at
http://support.sap.com/notes.
2354930 Release strategy for the ABAP add-on Focused Release and Installation Information
Run for Focused Run 2.0
2708866 Release Information Note for Focused Run 2.0 Note: These notes might get
SP00 (contains list of use-case specific updated on a regular basis. They
collective notes) contain critical information that shall
be considered, not only when initially
2641304 SAP Focused Run System Preparation Tool for
implementing Focused Run, but also
Managed System Preparation
when operating it.
2369401 Release Information Note for Simple
Diagnostics Agent 1.0
2729276 [Only relevant in case of FRUN System update] Relevant in case you update your
Focused Run 2.0 Delta Information for system from Focused Run 1.0 to
Upgrade from Focused Run 1.0 to Focused Run Focused Run 2.0 SP00
2.0 SP00
SAP HANA
Refer to chapter 4.2 Check Installed SAP HANA Revision
Kernel
Refer to chapter 4.6.4 Update SAP Kernel
Note
Make sure to follow the implementation recommendations provided in chapter 4.5 Implementing SAP
NetWeaver with Focused Run Using Up-to-Date Installation Process.
CA APM
The CA APM releases 9.7, 10.1 and 10.5 are supported.
You can check the version using one of the following tools:
• SAP HANA Cockpit (https://help.sap.com/viewer/product/SAP_HANA_PLATFORM/en-US)
• SAP HANA Studio (https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.03/en-
US/bd23f2d8bb57101480b0eedc2bf5fcce.html)
For more information on HANA Revision and Maintenance Strategy see SAP Note 2378962.
Ensure that the recommendations of SAP Note 2131662 - "Transparent Huge Pages (THP) on SAP-HANA-
servers" are applied to all SAP HANA database servers.
Also, to optimize the operating system environment for high performance environment, apply the parameters as
described in SAP Note 2382421 - " Optimizing the Network Configuration on SAP HANA- and OS-Level for SPS10
and Higher".
On UNIX, check the number of logical cores, or the number of cores per socket. Check this number as defined on
your SAP HANA system, using the OS command lscpu as explained here:
https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.00/en-
US/1b3599dd8ba441c99f3118ca90c94364.html
Use these numbers to maintain the following SAP HANA parameters in the relevant files, as described here:
https://help.sap.com/viewer/6b94445c94ae495c83a19646e7c3fd56/2.0.00/en-
US/3f1a6a7dc31049409e1a9f9108d73d51.html
Alternatively, use the SAP HANA Administration Console to adjust the following parameters, by navigating to the
tab Configuration and:
global.ini
[execution]
default_statement_concurrency _limit = <number of logical cores on SAP HANA server / 2>
max_concurrency = <number of logical cores on SAP HANA server / 2> (only for HANA 2.0 Revision
lower than 30 (Release <200.030.00)
max_concurrency_hint = <number shall be lower or equal to the number of cores per socket>
[persistence]
max_gc_parallelity = <number of logical cores on SAP HANA server / 2>
Using the up-to-date installation process, you can easily install your SAP ABAP FND 1709 SP 02 system (on SAP
HANA), including the necessary Focused Run add-ons.
Plan the desired installation target by using the maintenance planner at
https://apps.support.sap.com/sap/support/mp. Install the SAP NetWeaver ABAP system along with a required
support package stack and ABAP add-ons in one implementation execution.
All details can be found in the guide corresponding to your operating system, which you can find on the Software-
Logistics-Tools page.
Note
For the database, select SAP HANA and for the technical stack, select ABAP.
During the installation of Focused Run 2.0 SP00, select the following:
• Select ABAP FND 1709 with Support Package 2
• Choose Install or maintain Add-on
• Select Focused Run 2.0 SPS 00
IMPORTANT NOTICE: In the screen Select OS/DB dependent files, select User Interface Technology 752
(SAP_UI 752 SP05).
• Select your OS combination with SAP HANA database-dependent files. Follow SAP NetWeaver current
installation instructions to download and install the system based on the files selected in the maintenance
planner.
Before proceeding with the Focused Run configuration, perform a client copy as described below. Detailed
information about client copies is available at:
https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/7.5.6/en-
US/4d7ce15219a00f88e10000000a42189b.html.
Activities
Create a new production client and perform a local client copy, as following:
Note
Make sure to select the SAP_CUST profile. If you select another profile, you cannot complete the Focused
Run configuration (Business Partners creation).
8. If needed, create a ddic user in this new client (transaction SU01).
9. Finally, delete again the profile parameter: login/no_automatic_user_sapstar
10. Change Client Role of the new client to Production.
Note
Proceed with the next configuration activities, using this created production client. Therefore, make sure
to maintain the profile parameter login/system_client, as proposed later, in chapter 4.6.3 Checking and
Adjusting SAP NetWeaver ABAP Profile Parameters.
Perform the initial configuration of your Focused Run system with a user having administrator privileges. Details
are provided in security guide. See the chapter titled Roles for Setup Admin and Dev Support.
Information on how to maintain SAP NetWeaver ABAP profile parameters can be found at:
https://help.sap.com/viewer/b17bd20044a44edb9aa7830ee52ffac3/7.5.9/en-
US/5a860a509ece466ce10000000a423f68.html
Maintain the parameter names and values specified below by using transaction RZ10. These parameters are the
minimum requirement for the Focused Run installation. All recommendations are valid for usage of zero
administration memory management (SAP Note 2085980 - New features in memory management as of kernel
release 7.40).
Note
The parameter recommendations are a starting point for a midsize Focused Run installation. Based on
your individual scenarios, a larger scaling of the parametrization might be necessary.
icm/server_port_X Typical values: Set up one HTTP, HTTPS and SMTP port
• icm/server_port_0 =
PROT=HTTPS, PORT=443,
TIMEOUT=300,
PROCTIMEOUT=300
• icm/server_port_1 =
PROT=HTTP, PORT=80,
TIMEOUT=300,
PROCTIMEOUT=300
• icm/server_port_2 =
PROT=SMTP,PORT=25000,
TIMEOUT=180
abap/shared_objects_size_MB >=1025
abap/buffersize 8000000
rdisp/elem_per_queue 4000
rdisp/max_wprun_time 3600
rdisp/tm_max_no >=8000
rsdb/ntab/entrycount 1500000
rsdb/cua/buffersize 70000
rsdb/obj/max_objects 80000
rsdb/esm/buffersize_kb 8192
rsdb/otr/max_objects 5000
rsdb/otr/buffersize_kb 8192
sap/bufdir_entries 15000
zcsa/second_language E
http/security_context_cache_size 8000
It is required to use a kernel release 7.53 64-BIT UNICODE. The kernel Support Package (or, Patch Level) must be
at least 300.
As a mandatory requirement, follow precisely the solutions documented in the below listed SAP Notes. Also,
when implementing in your Focused Run system any automatic correction, using transaction SNOTE, taking care
of any mentioned manual activity and any subsequently referenced SAP Notes. (For further information about
Note Assistant (SNOTE transaction), refer to
https://help.sap.com/viewer/9d6aa238582042678952ab3b4aa5cc71/7.5.13/en-
US/48b41a66fc096ff4e10000000a42189b.html )
• 2708866 - Release Information Note for Focused Run 2.0 SP00.
• 2369401 - Release Information Note for Simple Diagnostics Agent.
• 2090746 - WD ABAP: Unified Rendering Update with TCI - Instructions and Related SAP Notes (Focused Run)
Note
Implement the latest Unified Rendering relevant for SAP_UI release that is installed on your system
(expected release is 7.52), using the Transport-based Correction Instruction (TCI). Remind to follow the
documentation attached to SAP Note 2187425, providing details on the prerequisites and any required
permission. If you need information, on how to download and apply TCIs, refer to KBA 2498908.
In case of error messages regarding incomplete included notes during installation please refer to SAP
Note 2627665.
Caution
These SAP Notes are updated on a regular basis. They contain critical information that need to be
considered, not only when initially implementing Focused Run, but also when operating it.
If not already performed, as part of the SAP NetWeaver installation procedure (See 4.5 Implementing SAP
NetWeaver with Focused Run Using Up-to-Date Installation Process [page 18]), make sure that you completed the
relevant automated initial setup, using the task list SAP_BASIS_SETUP_INITIAL_CONFIG, in client 000, as
described in https://help.sap.com/doc/ec180e1ef0e8414896c13522d39f613f/1.0/en-
US/Installation__Automated_Initial_SetupE.PDF .
Note
You can cross check previous task list executions, using transaction STC02.
As Focused Run applications generate a high volume of logs, ensure that a proper housekeeping for the
application logs is in place. SAP Note 195157 contains the required information about the necessary steps to
achieve this. For Focused Run, it is sufficient to delete entries already due.
Focused Run offers an in-application help (Web Assistant) for the end user interfaces. We strongly recommend
to enable this in-application help, because this is the future proof distribution channel for help in SAPUI5. The help
texts and the help framework for the in-application help are loaded from the HANA cloud by the SAP Web
Dispatcher when receiving an end-user request. This requires that the user request for the Fiori launchpad and all
tiles are sent to a SAP Web Dispatcher. The SAP NetWeaver ABAP generates the needed URL's automatically
with the parameters maintained in the HTTPURLLOC (see below section HTTPURLLOC).
To prepare you SAP Web Dispatcher to load the help content and help frame work you need to proceed certain
tasks:
1. Configure the HANA Cloud URL in the profile of the Web Dispatcher: The dispatcher needs access to the
internet through a proxy
2. Configure the rewriting rules to be applied for this URLs in a dedicated file
3. Set a parameter to allow the Web Dispatcher to treat requested URI’ s correctly
4. Import the HANA cloud server certificate into the Web Dispatcher SAPSSLC.PSE
5. Configure HTTPURLLOC.
For more information on how to prepare the SAP Web Dispatcher, see the next sections.
Note
The FR0 and FR1 of wdisp/system_0 and wdisp/system_1 do not exist. The FRP is the real SID of the
Focus Run (please set it to the correct selecton criteria values). The selection criteria PROXY =
proxy:8080 is also an example please set your proxy host and port.
# Back-end system configuration
wdisp/system_0 = SID=FR0, EXTSRV=https://cp.hana.ondemand.com, SRCURL=/sap/dfa/help/, SRCSRV=*:*,
PROXY=proxy:8080, STANDARD_COOKIE_FILTER=OFF
wdisp/system_1 = SID=FR1, EXTSRV=https://xray.hana.ondemand.com, SRCURL=/resources/sap/dfa/help/,
SRCSRV=*:*, PROXY= proxy:8080, STANDARD_COOKIE_FILTER=OFF
wdisp/system_2 = SID=FRP, MSHOST=XXXX, MSPORT=8340, MSSPORT=XXXX, SSL_ENCRYPT=1, SRCURL=/
The parameter is icm/HTTP/mod_<nr> . You need to create a file redirect.tx in your profile directory
Example:
icm/HTTP/mod_0 = PREFIX=/, FILE=$(DIR_PROFILE)/redirect.txt
The file redirect.txt contains rules to be applied for the modification of user requests. With the non-existing SID
from above it looks like this:
# User Assistance Content Platform - rewrite rule
if %{SID} = FR0
begin
SetHeader HOST cp.hana.ondemand.com
RegRewriteRawUrl ^/sap/dfa/help/(.*) /dps/$1
end
# Script Server - rewrite rule
if %{SID} = FR1
begin
SetHeader HOST xray.hana.ondemand.com
RegRewriteRawUrl ^/resources/sap/dfa/help/(.*)/xRayControls/resources/sap/dfa/help/$1
end
By setting multiple wdisp/system_<Nr> URI resolution conflicts might occur. This can be resolved by setting the
parameter:
wdisp/system_conflict_resolution = 1
For system selections, refer to the following documentation: SAP Web Dispatcher for Multiple Systems.
The system selection is performed in the sequence of the wdisp/system_<xx> parameters (using the parameter
index <xx>). As soon as the first system that matches the inbound request is found, the request is sent to this
system. This is “first match” semantics.
Make sure that all URLs generated by the Focused Run system are using the hostname and port of the SAP Web
Dispatcher by editing the HTTPURLLOC table (via transaction SE16). More details are available here: URL
Generation in an AS-ABAP - Web Dispatcher Configuration.
See below for typical entries in the HTTPURLLOC table:
• Client: Production client
• SORT_KEY: 0100
• PROTOCOL: HTTPS
• APPLICATION: *
• HOST: FQDN of SAP Web Dispatcher / Load Balancer
• PORT: HTTPS of SAP Web Dispatcher / Load Balancer
In Focused Run, you operate applications, including batch processing. At the same time, web service calls will
consume extensive resources from the ABAP applications servers. You shall therefore implement a separation of
the individual workloads. NetWeaver ABAP comes with various built-in load balancing mechanisms, which shall be
set up as explained below:
• Logon Groups: For distribution of dialog workload.
Dialog users can explicitly be directed to an individual server or logon group once they enter the system.
Logon groups are defined in transaction SMLG.
• Job Server Group (maintained in ABAP transaction SM61): For distribution of batch workload
background jobs.
Batch jobs can be scheduled using dedicated execution server groups to avoid resource conflicts via
transaction SM61. In the job scheduling UI, the server group can be entered as Execution Target.
• RFC Server Groups: For distribution of parallel processing activities.
The execution of high volume processing jobs is distributed via asynchronous RFC calls. The RFC server
groups can be defined in transaction RZ12.
In Focused Run, consider putting in place the following workload split:
• Dialog and occasional background processing (designated as Reoccurring load)
• Continuous high-frequency processing (designated as Continuous load)
Activities
Log in to your Focused Run ABAP system on the production client, and define the logon groups, job server
groups and RFC server groups on your Focused Run system, using the above-mentioned transactions, with the
below proposed values. This will split the load into two different groups of application servers.
Workload Types Application Server Instance Logon Groups Job Server Groups RFC Server Groups
(*) For all jobs scheduled manually later in this guide, use as execution target FRN_JOB_PUBLIC.
Note
High frequency background jobs are automatically scheduled by the Focused Run system.
For production usage of Focused Run, we recommend providing at least two application server instances for
each of the above-mentioned workload types to ensure a high availability of the processing resources for each
of them. This means you operate in total four application server instances.
To make sure to have all inbound data streaming ICF endpoints in Focused Run, use the Logon Group
STREAMING only. This can either be achieved in your hardware load balancer configuration, or in your SAP Web
Dispatcher by assigning the Logon Group STREAMING to all ICF services mentioned as Inbound data streaming
channels services in section 5.2.1 Preparing UI Environment.
Activities
1. Log in to your Focused Run ABAP system on the production client.
2. Start transaction STC01.
3. On the Task Manager for Technical Configuration screen, insert SAP_GW_FIORI_ERP_ONE_CLNT_SETUP in
the Task List field.
4. Choose Generate Task List Run with Variant (CTRL+F8).
5. Choose the variant SAP&FRUN_INIT.
6. Choose Start/Resume Task List Run in Dialog (or in Background).
Once the task list run has been finished successfully, green lights appear in the Status column. In case of
errors, perform an error analysis using the task documentation provided for each task.
Further details about this task list, are available here:
https://help.sap.com/viewer/d71464d9f3204ea8be1144d62acd9ac3/7.52/en-
US/bfd1b053a647e842e10000000a4450e5.html
Note
The OData and SICF services activated by this step are listed in the appendix.
Protect your system against clickjacking (or UI redressing) attacks. This type of attack tricks the user into
triggering actions within an application by hijacking mouse clicks. This requires activation of the ICF node
/sap/public/bc/uics/whitelist.
Activities
1. Go to your Focused Run system.
2. Open transaction SICF_INST
3. Select the technical name UICS_BASIC
4. Execute
To distribute the Simple Diagnostics Agent (SDA) automatically to all hosts connected to Focused Run, provide
the latest binaries of the OS specific Simple Diagnostics Agent and SAP JRE 8.1 to the Focused Run central
system.
Activities
1. Download the latest version of the binaries SDA and SAP JRE (which stands for Java Runtime Environment)
from SAP Support Portal as follows:
o Open the SAP Software download center (https://launchpad.support.sap.com/#/softwarecenter)
o Select tab Support Packages & Patches
o By Category
o SAP Technology Components
o Focused Run
o Focused Run 2.0
o Downloads
o Comprised Software Component Versions
o Each time select the SDA and SAP JRE for the operating systems being supported in the managed
system landscape (including the Focused Run system itself).
Currently the following platforms are supported:
o IBM AIX
o HP-UX on IA64
o Linux on Power BE & LE
o Linux x86_64
o Oracle Solaris SPARC
o Oracle Solaris x86
o Microsoft Windows Server on x86_64
2. Log in to your Focused Run ABAP system on the production client
Note
At the time a new SDA version is released on the SAP Support Portal, repeat the above described
procedure for all operating systems relevant in your landscape. In addition, trigger an SDA update for
already installed SDAs, using the Agent Administration UI (available in the launchpad). The current
version of the binaries uploaded to your Focused Run can be determined by running the report
SRSM_AMA_UPLOAD_BINARY and selecting option Display Content only.
Before you continue with the next steps, refer to the security guide, chapter Technical User Creation in Central
Focused Run to create all required technical users on the Focused Run system:
• Template users (named like TPL_FRN*)
• Background processing users (named like FRN_BTC*)
Note
We recommend creating the technical users by following naming conventions provided in the security
guide.
For user management of communication users in Focused Run, two different approaches are available.
1. Integrate with a customer user management solution that handles the user creation and update process and
provides to Focused Run the active passwords for the relevant users only. Process all user handling and
configuration in the user management solution, and in Focused Run the BAdI enhancement spots used for
integration purposes.
2. If no appropriate user management solution is available, use the Focused Run built-in solution in Simple
System Integration (SSI). To enable this approach, perform the following steps:
Note
Only users having a PFCG role with permission S_RFC_ADM will be able to maintain this RFC destination.
o Using transaction SA38, execute report P_SSI_PREPARATION with the following parameters.
Then choose Save as shown in the below screenshot.
Ensure that the latest content is available in Focused Run. Therefore, perform the content update as described in
SAP Note 2695734, each time new content is available.
Note
Please make sure that note 2716980 is implemented before the content is updated.
Activities
Note
Focused Run includes a SAP CIM model and SAP CR content. The update of this SAP CIM model and CR
content is ongoing: At least every 3 months (by executing again the transaction LMDB_SETUP and read
the report documentation for details).
To install that delivered SAP CIM model and SAP CR content, start the Landscape Management Database (LMDB)
setup, using transaction LMDB_SETUP. This transaction automatically detects whether the included SAP CIM
model and SAP CR content are outdated. Therefore:
• In case you are not notified about any outdated model, simply execute the initial setup, by pressing Execute.
This is importing the SAP CIM model, synchronously. The SAP CR content gets imported by the scheduled
background job SAP_LMDB_IMPORT. Check the job log of this job, which runs for several hours. You do not
need to wait until the job finishes.
Check whether the job is running without errors for longer than 5 minutes, before proceeding with the
next configuration steps.
If the job aborts due to parallel system operations (like a system reboot), repeat the import process
using transaction LMDB_SETUP.
• In case you are notified that the delivered content is already outdated, upload the latest SAP CIM model and
SAP CR content manually into LMDB, as described in SAP Note 669669 - Update of SAP System Component
Repository, using transaction LMDB_SETUP.
Prerequisite
The template users have been created, as recommended in the security guide.
Activities
1. Start the application Global Settings & Network Configuration in the Group: Infrastructure Administration via
the Focused Run launchpad.
2. If you plan to enable a set of use cases only for a set of customer networks, first navigate to page Network
Settings. Select one by one the relevant Customer Networks, and each time mark the check Override Global
Use-Case Settings. Select the expected use cases to be enabled and choose Save.
3. Navigate to the page Global Settings and mark the use cases you would like to enable for all customer
networks for which no use cases specific setting was done (see above item 2). Then choose Save.
Troubleshooting
4. Use transaction SLG1 / Object: AI_SSI to follow-up the background activities performed after having adjusted
the use case settings.
LMDB namespaces are used to group all systems belonging to one logical network. As prerequisite for all
applications the Focused Run system itself must be known. Therefore, the above mentioned LMDB set up is
creating a default namespace, named LOCALNETWORK. This local network can be used for all use cases of
Focused Run, where specific security or data separation requirements are not necessary.
Note
Handling of customer networks is similar to the local network. The specifics of the local network are the following:
• Namespace to represent the local network is created at the time of initial setup of LMDB with the fixed name
LOCALNETWORK.
• Communication from managed systems to Focused Run system does not require proxy or reverse proxy.
Therefore, for this specific network no inbound fencing string is used.
Activities
To be able to use the LOCALNETWORK namespace, some additional input is required. To maintain the data:
1. Log in to your Focused Run ABAP system on the production client.
2. Start report RLMDB_CUSTOMER_NETWORK_TOOLS, using transaction SA38.
3. Remove the mark of the Prohibit saving of any changes and then execute.
4. Edit the network LOCALNETWORK, and maintain the following values:
o Caption: meaningful description for the local admin network e.g. Local Network
o Customer Name: 3-character CID for the Focused Run system itself
o Data Center 1: up to 4-character ID for the data center the Focused Run system itself is running
o Proxy to Admin: Host: hostname of load balancer for the Focused Run system
o Proxy to Admin: Port: port of https or http load balancer for the Focused Run system
o Secure (Proxy to Admin): Set this flag if https is used for communication
o Other fields: Leave them empty (do not use proxy or fencing in local network)
5. Again, using transaction SA38, execute report SSI_ADMIN_NETWORK_INITIALIZE. As parameters, provide:
LOCALNETWORK and the unique password of the sapadm OS users. These OS users, which shall have all
the same password on all hosts, running the Focused Run system and the HANA database. Then choose the
Initialize Admin Network button, as shown here:
Note
Do not simply use transaction SU01. Refer to the security guide for additional details.
o FRN_LDDS_<CID>
User on Focused Run system to authenticate data suppliers sending SLD payloads directly to LMDB.
o FRN_LDSR_<CID>
User on Focused Run system to authenticate the SLDRs, which are forwarding received SLD payloads.
o FRN_EWA_<CID>
Therefore, proceed as follow for the above-mentioned users:
o Start transaction SA38.
o Run the RSSI_CHANGE_NETWORK_PASSWORD.
o Select the type of User, as mentioned above.
o Select the Customer ID.
o Provide a New password.
Note
Pay attention to avoid typos, since you enter the password only once.
o Choose Change Password.
In Focused Run, each system has a direct relationship to one business partner in the customer relationship role.
For all systems registered in the local network, you must create such a business partner. In addition, the external
identification to local network must be provided to allow a matching of maintained Customer IDs (CID) with the
corresponding business partners.
Send all relevant System, Instance, Host and Database data to the LMDB of the Focused Run System.
Note
Remember to double check the SAP Host Agent version.
Make sure that SAP Note 2734864 was implemented on the FRUN System
1. To send data to Focused Run ABAP Stack, maintain the SLD Data Supplier for the following (please refer to
managed system preparation guide for detailed information):
o ABAP (RZ70, use HTTP(s) destination to send general system data,
See Preparing Managed System Guide for details
o SAPStartSRV (sldreg): sending data for technical instances
See Preparing Managed System Guide for details.
o SAP HANA (sldreg + HDBLCM): sending Database information
See Preparing Databases Guide for details.
2. Perform the outside discovery for all hosts of Focused Run system and the associated database, as
described in the Preparing Outside Discovery Guide.
3. Open transaction LMDB and check the data supplier completeness for the Focused Run ABAP system. Do not
continue if the check is not successful (missing or outdated data suppliers are reported).
For troubleshooting you can user report RLMDB_DS_DISPLAY_TRACES (see SAP Note 2196245 for details).
In Focused Run, data exchange with SAP support portal is used for system data and license management in these
two scenarios:
• All systems, managed by Focused Run, belong to the same customer number, or belong to customers of a
single Customer Competence Center (CCC). In this case, set up a single connection for that customer or
CCC, as described below.
• The systems, managed by Focused Run, belong to multiple independent customers. In this case, the multiple
connection setup shall be performed, as described later, and this for each customer number of the respective
managed systems.
Activities
1. Execute the task list SAP_SUPPORT_HUB_CONFIG to setup the connectivity to SAP.
Note
The task list contains automatic and manual activities
o Log in to your Focused Run ABAP system on the production client.
o Start transaction STC01.
Schedule the following background jobs, using transaction SM36, and select as Target, the previously created Job
Server Group FRN_JOB_PUBLIC.
With FRUN 2.0 SP00 a new mass setup tool for 'Multiple individual Connections for each Customer for
Communication with SAP Support' was introduced. To setup multiple connections perform the following
activities:
Activities
1. Activation of the multiple connection BADI:
o Log in to your Focused Run ABAP system on the production client.
o Start transaction SE19.
o Choose enhancement implementation: AI_SDK_SP_RFC_RP.
o Edit the enhancement implementation and mark the flag Implementation is active.
Schedule the following background jobs, using transaction SM36, and select as Target, the previously created Job
Server Group FRN_JOB_PUBLIC.
Schedule the above background jobs, using transaction SM36, and select as Target, the previously created Job
Server Group FRN_JOB_PUBLIC.
Background
With the Simple System Integration (SSI) System Monitoring will be activated on the managed System.
Launch the tile Simple System Integration in the Group Infrastructure Administration in the Focused Run
launchpad. Execute the actions Edit Configuration and Configure Automatically within the Simple System
Integration for the Focused Run ABAP system itself, to ensure that the infrastructure can be used for central
monitoring.
Prerequisite
You have created the user SDAGENT with all roles as described in the managed system preparation guide
Activities
1. Start application Simple System Integration in the Group: Infrastructure Administration via the Focused Run
launchpad
2. Search for the FRUN system.
3. Mark the line with the FRUN system.
4. Click on Edit Configuration
5. Provide user credential for SDAAGENT user on managed system
6. Choose Save.
7. Select Configure Automatically (This starts the SSI)
5.2.14 Self-Monitoring
Configure Self-Monitoring.
Activities
1. Log in to your Focused Run ABAP system on the production client.
2. Start transaction MAI_TOOLS.
3. Choose Activate Expert Mode.
4. Select Configuration / Configure Central Components.
You should get a message that the Monitoring Scenario was configured successfully.
Refer to SAP Note 455140 to configure the e-mail and optionally SMS servers. Finally, enter the name of the SMS
server, using Infrastructure Administration -> Central Notification Management -> links -> Configure SMS Server
If you plan to schedule automated guided procedures in background, either in the context of ASM (via Guided
Procedure Planning Management), or AEM (Alert reaction procedures), then specify the user name.
The expected user is FRN_BTC_GPA, or any other user having the required permissions. Therefore, perform the
following:
Activities
1. Log in to your Focused Run ABAP system on the production client.
2. Start transaction SA38.
3. Run the PR_CONF_GP_ARP_BTC.
4. Adapt the default user FRN_BTC_GPA, if required.
5. Choose Execute.
Execute the task list SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_ASM to enable the UI environment
specific to this use case.
Activities
1. Log in to your Focused Run ABAP system on the production client.
2. Start transaction STC01.
3. On the Task Manager for Technical Configuration screen, insert SAP_FRUN_SETUP_USECASE in the Task List
field.
4. Choose Generate Task List Run with Variant (CTRL+F8).
5. Choose the variant SAP&FRUN_ASM.
6. Choose the Change Parameters icon for the task Activate HTTP Services (SICF), to add the following missing
services:
/sap/bc/ui5_ui5/sap/frsh
7. Choose: Save.
8. Choose: Back (F3).
9. Choose Start/Resume Task List Run in Dialog (or in Background).
Once the task list run has been finished successfully, green lights appear in the status column. In case of
errors, perform an error analysis using the task documentation provided for each task.
Note
The OData and SICF services activated by this step are listed in the appendix.
Prerequisite
Before configuring SAP EarlyWatch Alert (EWA), the following prerequisites must be met:
• Minimum ST-PI 740 SP09 must be implemented in the Focused Run system
Activities
Activate the processing of EWA data
1. Log in to your Focused Run ABAP system on the production client.
2. Start transaction SDCCN.
3. Go to Utilities and choose Activate.
4. Click Continue, on question if SDCCN should be activated in local system.
General Remark
Metric Forecasting is part of System Anomaly Prediction and can also be used separately in the Metric Monitor.
Prerequisite
The predictive analytics for System Analysis and System Monitoring, requires that you install the Application
Function Library (AFL) and the SAP HANA Automated Predictive Library (APL).
Note
For the following references to documentation on the SAP Help Portal, always select your SAP HANA
release in the top right corner of the relevant SAP Help Portal page.
1. See the SAP HANA Predictive Analysis Library (PAL) documentation to install AFL.
2. See the Installing SAP HANA APL section in the SAP HANA Automated Predictive Library Reference Guide to
install APL.
3. Roles and Authorization:
The role SAP_FRN_APP_PAS_DISP contains the display authorizations for Metric Forecasting.
Please refer to the Checking the Installation section in the SAP HANA Automated Predictive Library Reference
Guide to check that the APL installation is working.
For forecasting calculations, choose the number of days, for which data is to be calculated. The data store is
selected automatically: either the System Monitoring data store, the System Analysis aggregated store (if
aggregation is enabled), or both based on the relevant application configuration. You can also enter the number of
forecast points in various increments of minutes or hours. To configure this, use the SM30 view of
PAS_SM_DP_CONFIG.
The default settings mentioned below are maintained automatically based on the granularity during preparation.
When the forecast API is called the first time, these values are entered automatically. They are not available by
default before that.
MIN
• Number of days, for which data is to be read from the System Monitoring data store: 5
• Read from Aggregation Store: No
• Number of forecast points to be shown: 12
5MIN
• Number of days, for which data is to be read from the System Monitoring data store: 15
• Read from Aggregation Store: No
• Number of forecast points to be shown: 6
15MIN
• Number of days, for which data is to be read from the System Monitoring data store: 15
• Read from Aggregation Store: No
• Number of forecast points to be shown: 4
1HOUR
• Number of days, for which data is to be read from the System Monitoring data store: 30
• Read from Aggregation Store: Yes
• Number of forecast points to be shown: 2
DAY
• Number of days, for which data is to be read from the System Monitoring data store: 30
• Read from Aggregation Store: Yes
• Number of forecast points to be shown: 2
Optional:
Execute the report PAS_SAVE_EXCEPTION by using transaction SE38. By default, APL is used as the algorithm.
The user can adjust the algorithm to “FS” (PAL’s Forecast Smoothing) for metrics by saving the metric ID and
hash metric path (if applicable). Maintain exceptions only if you want to use PAL’s Forecast Smoothing. The
default behavior is that all forecasts happen using APL. The default algorithm is APL.
Optional:
Maintain FORECAST_CONFIDENCE by using the SM30 view of PAS_SM_GEN_CONFI: Confidence Interval for APL
Auto Regression algorithm. The other acceptable values are 99 and 90. When the forecast API is called for the
first time, the value mentioned below is entered automatically. It is not available by default before that.
• Param Name: FORECAST_CONFIDENCE
• Param Count: 1
• Param Value: 95
Note
This option is applicable only for APL as of Focused Run 1.0 FP03. The default value is 95%.
Optional:
Maintain NULL_VALUE_EXIT_PC using the SM30 view of PAS_SM_GEN_CONFI: The percentage of null values
acceptable for forecasting. If there are more null values, forecasting will be aborted. When the forecast API is
called for the first time, the value mentioned below is entered automatically. It is not available by default before
that.
• Param Name: NULL_VALUE_EXIT_PC
• Param Count: 1
• Param Value: 40
Note
The default value is 40%.
Important Information
System Anomaly Prediction is a new optional Focused Run feature in an early rollout phase.
The preparation of the Linux compilation environment for R with the various dependencies will requires that you
install various SDK packages in your Linux environment. These SDK packages are usually not installed on server
hosts running SAP software and therefore are not part of your standard repositories for Linux installations with
distributions like “SuSe SLES for SAP” or “Red Hat for Enterprise”, etc. You might need to register additional
Linux software repositories on your designated R host
We recommend to prepare the compilation environment and the R runtime on dedicated hosts following your
company security policies.
Preparation
The System Anomaly Prediction requires you to install. R For more information, see the SAP HANA R Integration
Guide for System Anomaly Prediction at SAP HANA R Integration Guide for System Anomaly Prediction at the
Focused Run Expert Portal.
Note
The guide is currently valid for SuSe SLES and Red Hat only.
6.1.2.3.1 Activities
The configuration can be done in System Monitoring application only. System Monitoring:
• System Anomaly Prediction Configuration
o SAP_FRN_AAD_MOAL_ALL - All authorizations for System Monitoring & Alert Management
Administration/Configuration
• System Anomaly Prediction Display
o SAP_FRN_APP_MOAL_DISP - Display authorizations for System Monitoring & Alert Management
o SAP_FRN_APP_MOAL_ALL - All authorizations for System Monitoring & Alert Management
System Analysis:
• System Anomaly Prediction Display
o SAP_FRN_APP_SYA_ALL - All Authorizations for the System Analysis application (end user)
Schedule the following background jobs, using transaction SM36, and select as Target, the previously created Job
Server Group FRN_JOB_PUBLIC.
For more information about the scheduling, see the master guide in step 6.1.3. Background Jobs for ASM.
Description: User with authorization to run System Anomaly Prediction anomaly engine job and housekeeping.
If you as an administrator have the roles for System Anomaly Prediction Configuration, you can activate and
maintain models for prediction scenario. The concept of variant is not available from FRUN 2.0 onwards. You need
to run the migration report “PAS_CONF_MIGRATION” to migrate from variant based configuration to system-
based configuration. If you do not run this report program, you will not see the systems which were activated for
prediction in FRUN 1.0 FP03 now in the new FRUN 2.0.
Activities
1. Start application System Analysis Configuration via the Focused Run launchpad, or via the URL:
https://<host>:<port>/sap/bc/webdynpro/sap/sysana_config
2. Upon first launch, you will get a popup dialog to create an aggregation task for system analysis. Fill the dialog
with appropriate values and choose OK. To review the task settings at a later point in time choose Edit Task in
the top right.
Example values:
1. Choose Schedule Period
2. Collect from: 02:00:00
3. Schedule period (in minutes): 1440
4. Log store data (in days): 5
3. (Optional) Create a variant to activate aggregation of selected metrics for specific system types.
Schedule the following background jobs, using transaction SM36, and select as Target, the previously created Job
Server Group FRN_JOB_PUBLIC.
Execute the task list SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_AUM to enable the UI environment
specific to this use case.
Activities
1. Log in to your Focused Run ABAP system on the production client
2. Start transaction STC01
3. On the Task Manager for Technical Configuration screen, insert SAP_FRUN_SETUP_USECASE in the Task List
field.
4. Choose Generate Task List Run with Variant (CTRL+F8)
5. Choose the variant SAP&FRUN_AUM
6. Choose Start/Resume Task List Run in Dialog (or in Background)
Once the task list run has been finished successfully, green lights appear in the status column. In case of
errors, perform an error analysis using the task documentation provided for each task.
Note
The OData and SICF services activated by this step are listed in the Appendix.
Schedule the following background jobs, using transaction SM36, and select as Target, the previously created Job
Server Group FRN_JOB_PUBLIC.
Execute the task list SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_CSA to enable the UI environment
specific to this use case.
Activities
1. Log in to your Focused Run ABAP system on the production client
2. Start transaction STC01
3. On the Task Manager for Technical Configuration screen, insert SAP_FRUN_SETUP_USECASE in the Task List
field.
4. Choose Generate Task List Run with Variant (CTRL+F8)
5. Choose the variant SAP&FRUN_CSA
6. Choose Start/Resume Task List Run in Dialog (or in Background)
Once the task list run has been finished successfully, green lights appear in the status column. In case of
errors, perform an error analysis using the task documentation provided for each task.
Note
The OData and SICF services activated by this step are listed in the appendix.
Execute the task list SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_AIM to enable the UI environment
specific to this use case.
Note
If you install Focused Run or apply a new support package for Focused Run, execute the report
/IMA/AFTER_UPDATE to perform required initialization or migration activities.
Note
The OData and SICF services activated by this step are listed in the appendix.
Schedule the following background jobs, using transaction SM36, and select as Target, the previously created Job
Server Group FRN_JOB_PUBLIC.
Execute the task list SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_AEM to enable the UI environment
specific to this use case.
Activities
1. Log in to your Focused Run ABAP system on the production client
2. Start transaction STC01
3. On the Task Manager for Technical Configuration screen, insert SAP_FRUN_SETUP_USECASE in the Task List
field.
4. Choose Generate Task List Run with Variant (CTRL+F8)
5. Choose the variant SAP&FRUN_AEM
Note
The OData and SICF services activated by this step are listed in the appendix.
Schedule the following background jobs, using transaction SM36, and select as Target, the previously created job
server group FRN_JOB_PUBLIC.
Self-Monitoring SFM_STATUS_ODATA_SERVICE
SFMDASHBOARD_SRV
Self-Monitoring /sap/bc/ui5_ui5/sap/metric_moni_sfm
/sap/bc/webdynpro/sap/solman_self_monitoring_app
/sap/bc/ui5_ui5/sap/selfmondash
(*) The technical user who executes the AEM Inbound Connector oData service should have the
role SAP_FRN_AEM_UMD_ALR.
During setup and configuration of Focused Run, some jobs are automatically scheduled. Some of them are
periodic jobs, some are event based. The following tables contain the list of these jobs for reference.
Remark: Some jobs are started as Daemon jobs. This means that they are restarted automatically after a specific
period.