focused run for sap solution manager - sap help portal · pdf filemaster guide document...

Master Guide

Document Version: 1.12 – 2017-11-07

CUSTOMER

Focused Run for SAP Solution Manager Feature Pack 1

2

CUSTOMER

© 2016 SAP SE or an SAP affiliate company. All rights reserved.

Focused Run for SAP Solution Manager

Typographic Conventions

Typographic Conventions

Type Style Description

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 Emphasized words or expressions.

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.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .


Document History

CUSTOMER

© 2016 SAP SE or an SAP affiliate company. All rights reserved. 3

Document History

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.

Version Date Change

1.0 2016-10-21 Initial Version for Focused Run 1.0

1.01 2016-10-31 Minor changes

1.1 2017-05-12 Update for Focused Run 1.0 FP01

1.11 2017-06-08 Minor changes

1.12 2017-11-03 Added chapter 4.1 Overview Focused Run Software Stack

Added chapter 4.7 Prepare SLD Namespace

Update chapter 4.6.6 Implementing SAP Notes

Adjusted chapter numbering for Preparing NetWeaver Basic Operation

onwards and onwards

Update chapter 5.2.6 Setup Communication with SAP Support Backbone

4

CUSTOMER



Table of Contents

Table of Contents

1 Getting Started ................................................................................................................................ 6 1.1 About this Document ............................................................................................................................ 6 1.2 Abbreviations and Terms ...................................................................................................................... 6 1.3 Focused Run Use Cases ........................................................................................................................ 7 1.4 Focused Run Implementation .............................................................................................................. 9

2 Define Implementation .................................................................................................................. 10

3 Plan Landscape .............................................................................................................................. 11 3.1 Planning Information ............................................................................................................................ 12 3.2 Further Useful Links ............................................................................................................................. 12 3.3 Related Guides ...................................................................................................................................... 13 3.4 Important SAP Notes ........................................................................................................................... 13

4 Prepare Implementation ............................................................................................................... 14 4.1 Overview Focused Run Software Stack ..............................................................................................14 4.2 Check Installed SAP HANA Revision ..................................................................................................14 4.3 Check and Prepare Your OS for SAP HANA ....................................................................................... 15 4.4 Check and Adjust SAP HANA Parameters ......................................................................................... 15 4.5 Implementing SAP NetWeaver with Focused Run Using Up-to-Date installation process ...........16 4.6 Post Installation of SAP NetWeaver ABAP Server for Focused Run Usage ....................................16

4.6.1 Create Productive client ......................................................................................................16 4.6.2 Focused Run Administration User...................................................................................... 17 4.6.3 Checking and Adjusting SAP NetWeaver ABAP Profile Parameters ............................... 17 4.6.4 Update SAP Kernel ..............................................................................................................19 4.6.5 Update of SAPUI5 Runtime Environment ..........................................................................19 4.6.6 Implementing SAP Notes ....................................................................................................19

4.7 Prepare SLD Namespace .................................................................................................................... 20

5 Implementing Focused Run 1.0 ..................................................................................................... 21 5.1.1 Preparing NetWeaver Basic Operation .............................................................................. 21 5.1.2 Configuring Usage of Web Based Front-End Application URLs ....................................... 21 5.1.3 Setup Load Balancing ......................................................................................................... 22

5.2 Configuration of Focused Run Application Foundation ................................................................... 23 5.2.1 Preparing UI Environment .................................................................................................. 23 5.2.2 Creating Technical Users for Application Foundation ..................................................... 23 5.2.3 Preparing Simple Diagnostics Agent Distribution ........................................................... 23 5.2.4 Simple System Integration................................................................................................. 24 5.2.5 Landscape Management Database ................................................................................... 26 5.2.6 Setup Communication with SAP Support Backbone ...................................................... 30 5.2.7 Setup Application Foundation Background Processing ................................................... 31 5.2.8 Data Collection Framework and Alert Calculation ........................................................... 32 5.2.9 Content Update ................................................................................................................... 32 5.2.10 Activate System Monitoring for Focused Run System .................................................... 33


Table of Contents

CUSTOMER


5.2.11 Self-Monitoring .................................................................................................................... 33

6 Business Scenarios of Focused Run ............................................................................................ 34 6.1 Advanced System Management ........................................................................................................ 34

6.1.1 Preparing Use-Case ............................................................................................................ 34 6.1.2 Setup Application Specifics................................................................................................ 34 6.1.3 Background Jobs for ASM .................................................................................................. 35

6.2 Advanced User Monitoring ................................................................................................................. 36 6.2.1 Preparing Use-Case ............................................................................................................ 36 6.2.2 Real User Monitoring Specific Setup Steps ...................................................................... 36 6.2.3 Background Jobs for AUM.................................................................................................. 36

6.3 Configuration and Security Analytics ................................................................................................ 37 6.3.1 Preparing Use-Case ............................................................................................................ 37 6.3.2 Additional Configuration for Configuration Validation .................................................... 37

6.4 Advanced Integration Monitoring ....................................................................................................... 37 6.4.1 Preparing Use-Case ............................................................................................................ 37 6.4.2 Background Jobs for AIM ................................................................................................... 38

7 Appendix ....................................................................................................................................... 39 7.1 OData and SICF services activated by STC01 task lists ................................................................... 39

7.1.1 SAP_GW_FIORI_ERP_ONE_CLNT_SETUP with Variant SAP&FRUN_INIT .................... 39 7.1.2 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_ASM ...................................... 41 7.1.3 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_AUM ...................................... 42 7.1.4 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_AEM ...................................... 43 7.1.5 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_CSA ....................................... 43 7.1.6 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_AIM ....................................... 43

6

CUSTOMER



Getting Started

1 Getting Started

1.1 About this Document

Purpose

This Master Guide is the starting point for the technical implementation of Focused Run for SAP Solution Manager

(Focused Run). It mainly contains cross-scenario implementation information.

Use the Master Guide to get an overview of Focused Run, its software units, and its scenarios from a technical

perspective. This document also guides you to design your system landscape and to define your implementation

planning. It also references related documents that include further details, like:

• Installation guides for single software units

• SAP Notes

• Configuration documentation

• SAP Library documentation

Note

You find the latest information about the technical implementation of Focused Run and the latest

installation and configuration guides on SAP Service Marketplace at

https://help.sap.com/viewer/p/FRUN.

We strongly recommend that you follow these documents. They are regularly updated.

Constraints

The primary focus of this master guide is to introduce 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.

1.2 Abbreviations and Terms

Abbreviation or short form Long form

Focused Run Focused Run for SAP Solution Manager

AUM Advanced User Monitoring

ASM Advanced System Management

CSA Configuration and Security Analytics

https://help.sap.com/viewer/p/FRUN


Getting Started

CUSTOMER


Abbreviation or short form Long form

RUM Real User Monitoring

TA Trace Analysis

SysMon System Monitoring

SysAna System Analytics

ITCal IT Calender

WMM Work Mode Management

SAM Service Availability Management

EWA SAP Early-Watch Alert

SCN SAP Community Network

CA APM CA Application Performance Management

SLD System Landscape Directory

SLDR SLD Data Router

SDA Simple Diagnostics Agent

JRE Java Runtime Environment

SSI Simple System Integration

LMDB Landscape Management Database

1.3 Focused Run Use Cases

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:

Use Case Description

Advanced User Monitoring (AUM) Monitoring of user experience across system and

technology stacks. In this use case the functionality

of Real User Monitoring (RUM) and Trace Analysis

(TA) is bundled. With RUM, you can monitor real user

requests across systems and technologies. It

provides correlation and assembling of different

server side measured data to end-to-end user

scenarios. Data is provided by SAPGUI and SAPUI5

clients, SAP Gateway and SAP ABAP Systems. RUM

covers performance as well as utilization

measurement also called Web Analytics. The TA

application is also part of this use case to support

8

CUSTOMER



Getting Started

Use Case Description

root cause analysis for performance and exception

issues in end-user scenarios.

Advanced System Management (ASM) Effectively and efficiently manages many systems,

databases and hosts. Focus is on functionality such

as:

• System Monitoring (SysMon)

• System Analytics (SysAna)

• IT Calendar (ITCal)

• Work Mode Management (WMM)

• Service Availability Management (SAM) and

• SAP Early-Watch Alert (EWA)

It covers the complete scope of managed system

types based on SAP and non-SAP technologies.

Configuration and Security Analytics (CSA) Analytics of configuration and security settings

across systems and technologies. Allows to browse

and investigate high volumes of configuration items

in complex system landscapes. Allows to validate

technical and security configuration settings against

customer-specific target configuration templates. It

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 and/or Advanced System

Monitoring. Comes with efficient and mass volume

enabled Alert Dashboards, Alert Inbox and Alert

Detail displays.

More Information

Find all information about Focused Run 1.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, as well as community content.

For Focused Run 1.0 you can access the Help Portal at http://help.sap.com/

• SAP Community Network (SCN)

The SCN is organized into more than 300 “spaces”, which support small, self-contained communities. These

communities are typically focused around a topic, an SAP product, or an industry. Each space contains a

complete set of social networking tools including a discussion forum, a blogging area, and an area where you

can collaborate on documents and publish them.

As a logged-on member, you can go to any space in the SCN landscape. You can also visit and follow a

particular set of spaces that reflect your particular range of interests, where members who share your

interests are likely to contribute.

SCN spaces are where you get the latest news from SAP and the community, interact with your peers, earn

http://help.sap.com/


Getting Started

CUSTOMER


points for your contributions, and establish reputation as being an expert on certain topics

You access the SCN at http://scn.sap.com/

1.4 Focused Run Implementation

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

http://scn.sap.com/

10

CUSTOMER



Define Implementation

2 Define Implementation

During an implementation project, take several aspects into account to make the informed decisions. Here the

major aspects:

Aspect Description Further Information

Scope and Requirements You determine the scope of your

Focused Run implementation

For more information see Focused

Run Use Cases [page 7]

Landscape Planning You determine the system

landscape and consider the

landscape-relevant aspects

concerning your required use

case.

Hardware and Software

Prerequisites

Check the required minimum SAP

NetWeaver ABAP version

SAP Note 2354930

Check the required minimum

revision of the installed SAP HANA

For more information see Check

Installed SAP HANA Revision

[page 14]

Check the hardware sizing

required for your Focused Run

implementation

The recommended hardware

sizing will be provided by your

implementation partner as part of

the license proposal

Security Planning You plan the user management

and infrastructure security

For more information see Focused

Run Security Guide

Release Restrictions Check SAP Notes for any release

restrictions


Plan Landscape

CUSTOMER


3 Plan Landscape

A Focused Run landscape consists of components as shown in following picture.

The following components are deployed in the landscape

• Focused Run System (running on SAP NetWeaver ABAP on SAP HANA)

• (optional) Load Balancer to distribute http(s) traffic between multiple processing instances. The usage of a

load balancer is strongly recommended for productive usage. The traffic consists of inbound data streams

and/or end-user communication.

• (optional) HTTP Proxy to forward data from the administration network to managed system network, the

proxy is not required if direct communication from Focused Run system to all host agents on hosts in the

managed system network on physical / virtual hostname and port 1128 (http) or 1129 (https) is possible.

• (optional) HTTP Reverse Proxy for sending data from (unsecure and/or untrusted) managed system network

areas to Focused Run system. The reverse proxy is required to separate the network segments with a high

security level and also for the data separation in Focused Run. A Focused Run end-user data access

authorization concept is only possible if the metrics are sent by different Reverse Proxy servers.

• (optional) Customer Management Server with the following components deployed:

o (optional) CA Application Performance Management (CA APM) is a 3rd party product. The software

component is not part of the Focused Run installation, but is available for all customers with a valid SAP

maintenance contract as part of the SAP Solution Manager installation. In Focused Run CA APM is only

utilized to collect available Bytecode Injection Metrics (such as for JRE engines or .NET runtime). In

networks without components utilizing CA APM native instrumentation, this component is not required.

o (optional) SLD Data Router (SLDR) is used to forward the SLD data supplier content to multiple target

systems (e.g. SLD server in SAP NetWeaver Java or LMDB in Focused Run). If the landscape data is only

collected for Focused Run, without the need to supply any SAP Solution Manager, SAP NetWeaver PI or

other components utilizing SLD data, the SLD data supplier of all systems can be connected directly to

the reverse proxy or load balancer of the Focused Run System

• SAP Host Agent is part of each SAP system installation and must be deployed on each host, which should be

managed by Focused Run.

12

CUSTOMER



Plan Landscape

• Simple Diagnostics Agent is installed as add-on to the SAP Host Agent, during the connection process to the

Focused Run system. With the help of the Simple Diagnostics Agent most of the data needed for Focus Run

use cases is collected and streamed to the Focused Run system.

• Managed Systems and Managed Databases are not part of the Focused Run installation or deployment

scenario, but as those are in scope and relevant as objects, for which Focused Run provides operations

capabilities, the distribution of those systems within the defined customer network areas is of importance and

shall be planned.

• Focused Run does perform data exchange with SAP Support Portal for various use cases, therefore a

connection to SAP Support Portal is needed.

• The LMDB component within Focused Run always require an operational SLD, in order to perform a CR

content synchronization. In other words, in case the SLD data supplier information is only relevant towards

Focused Run, the SLD data suppliers shall report to LMDB in Focused Run, Nevertheless, you have to operate

an SLD server (in a NetWeaver Java system), to achieve the CR content synchronization.

3.1 Planning Information

For more information about planning topics, not covered in this guide, refer to the following content:

Content Location on SAP Service Marketplace

Latest versions of Focused Run

guides


Released platforms and technology-

related topics such as maintenance

strategies and language support

https://service.sap.com/platforms

To access the Platform Availability Matrix directly, enter

https://support.sap.com/pam

Performance https://www.sap.com/solution/benchmark/sizing/performance.html

Information about Support Package

Stacks, latest software versions and

patch level requirements

https://support.sap.com/sp-stacks

Information about Unicode

technology

https://go.sap.com/community/topic/internationalization-and-

unicode.html

3.2 Further Useful Links

The following table lists further useful links on SAP Service Marketplace:


Information about creating error messages https://support.sap.com/incident

SAP Notes search https://support.sap.com/notes


https://service.sap.com/platforms

https://support.sap.com/pam

https://www.sap.com/solution/benchmark/sizing/performance.html

https://support.sap.com/sp-stacks

https://go.sap.com/community/topic/internationalization-and-unicode.html

https://go.sap.com/community/topic/internationalization-and-unicode.html

https://support.sap.com/incident

https://support.sap.com/notes


Plan Landscape

CUSTOMER



SAP Software Distribution Center (software

download and ordering of software)

https://support.sap.com/swdc

3.3 Related Guides

You can find more information about the prerequisite components in the following documents:

Title Location

Guides for SAP NetWeaver 7.5 https://help.sap.com/viewer/p/SAP_NETWEAVER_750

End- to-End Implementation

Roadmap for SAP NetWeaver AS

ABAP

https://service.sap.com/~sapidb/011000358700000488912013E.pdf

Technical Operations Guide for

SAP NetWeaver

http://help.sap.com/saphelp_nw75/helpdata/en/48/0dd91ad6013d1b

e10000000a42189d/frameset.htm

3.4 Important SAP Notes

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 the installation 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.

SAP Note Number Title Description

2354930 Release strategy for the ABAP add-on Focused

Run

Release and Installation Information

for Focused Run 100

2369217 Release restrictions for Focused Run 1.0 Overview on limitations

2381861 Release Information Note for Focused Run 1.0

for Solution Manager

Recent important observations and

corrections to be implemented.

https://support.sap.com/swdc

https://help.sap.com/viewer/p/SAP_NETWEAVER_750

https://service.sap.com/~sapidb/011000358700000488912013E.pdf

http://help.sap.com/saphelp_nw75/helpdata/en/48/0dd91ad6013d1be10000000a42189d/frameset.htm

http://help.sap.com/saphelp_nw75/helpdata/en/48/0dd91ad6013d1be10000000a42189d/frameset.htm

https://support.sap.com/notes

14

CUSTOMER



Prepare Implementation

4 Prepare Implementation

4.1 Overview Focused Run Software Stack

SAP HANA

• SAP HANA SPS12 with Revision 122.05 or higher

SAP Netweaver ABAP - Software Components

Component Release Req. min. SP Level Component Description

SAP_BASIS 750 0006 SAP Basis Component

SAP_ABA 750 0006 Cross-Application

Component

SAP_GWFND 750 0006 SAP Gateway Foundation

SAP_UI 751 0001 User Interface

Technology

ST-PI 740 0006 SAP Solution Tools Plug-

In

SAP_BW 750 0006 SAP Business Warehouse

MDG_FND 749 0006 MDG Foundation

SAP_BS_FND 748 0005 SAP Business Suite

Foundation

WEBCUIF 748 0005 SAP Web UI Framework

FRUN 100 0001 SAP Focus RUN Tool

ST-A/PI 01S_731 0002 Servicetools for SAP

Basis 731

SAP Netweaver ABAP - UI5 Runtime

• SAPUI5 Library 1.44.7 or higher

4.2 Check Installed SAP HANA Revision

The SAP HANA System is considered as a prerequisite.



CUSTOMER


Make sure that your implement HANA SPS12 Revision 122.05 or higher (>=1.00.122.05), using one of the

following:

• HANA Cockpit

(https://help.sap.com/saphelp_hanaplatform/helpdata/en/73/c37822444344f3973e0e976b77958e/cont

ent.htm)

• HANA Studio

(https://help.sap.com/saphelp_hanaplatform/helpdata/en/bd/23f2d8bb57101480b0eedc2bf5fcce/conten

t.htm)

4.3 Check and Prepare Your OS for SAP HANA

Please ensure, that the recommendation of note 2131662 - "Transparent Huge Pages (THP) on SAP-HANA-

servers" are applied to all HANA database servers.

To optimize the operating system environment for high performance environment, apply the parameters as

described in note 2382421 - " Optimizing the Network Configuration on HANA- and OS-Level for SPS10 and

Higher"

4.4 Check and Adjust SAP HANA Parameters

On UNIX, you can find out the number of logical cores, or the number of cores per socket, defined on your HANA

system, using the OS command lscpu, like explained here:

https://help.sap.com/saphelp_hanaplatform/helpdata/en/1b/3599dd8ba441c99f3118ca90c94364/content.ht

m

Use these numbers to maintain the following HANA parameters in the relevant files, as described here:

https://help.sap.com/saphelp_hanaplatform/helpdata/en/3f/1a6a7dc31049409e1a9f9108d73d51/content.htm

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 HANA server / 2>

max_concurrency = <number of logical cores on HANA server / 2>

max_concurrency_hint = <number shall be lower or equal to the number of cores per socket>

[parallel]

num_cores = <same value as max_concurrency_hint>

[persistence]

max_gc_parallelity = <number of logical cores on HANA server / 2>

Note: Adjusting this values, requires a restart.

https://help.sap.com/saphelp_hanaplatform/helpdata/en/73/c37822444344f3973e0e976b77958e/content.htm

https://help.sap.com/saphelp_hanaplatform/helpdata/en/73/c37822444344f3973e0e976b77958e/content.htm

https://help.sap.com/saphelp_hanaplatform/helpdata/en/bd/23f2d8bb57101480b0eedc2bf5fcce/content.htm

https://help.sap.com/saphelp_hanaplatform/helpdata/en/bd/23f2d8bb57101480b0eedc2bf5fcce/content.htm

https://launchpad.support.sap.com/#/notes/0002131662


https://help.sap.com/saphelp_hanaplatform/helpdata/en/1b/3599dd8ba441c99f3118ca90c94364/content.htm

https://help.sap.com/saphelp_hanaplatform/helpdata/en/1b/3599dd8ba441c99f3118ca90c94364/content.htm



16

CUSTOMER




4.5 Implementing SAP NetWeaver with Focused Run Using Up-to-Date installation process

Using the up-to-date installation process, you can easily install the SAP NetWeaver ABAP 7.5 system (on SAP

HANA), including the necessary add-ons.

Plan the desired installation target using the maintenance planner at

https://apps.support.sap.com/sap/support/mp, to install the SAP NetWeaver ABAP system along with a

required Support Package stack and the ABAP Add-Ons in one implementation run.

All details can be found in the guide appropriate to your operating system, which you can find on this download

page. Note: Take care to select SAP HANA as Database and ABAP as Technical Stack.

During Installation of Focused Run 1.0 FP01 the following must be selected:

• Select NetWeaver 7.5 with Support Package 6

• Choose "Install or maintain Add-on"

• Select Focused Run 1.0

• Select your OS combination with SAP HANA database depended files. Follow the SAP NetWeaver and current

installation instructions to download and install the system based on the files selected in Maintenance

Planner.

4.6 Post Installation of SAP NetWeaver ABAP Server for Focused Run Usage

4.6.1 Create Productive client

The use of client 001 is not supported in Focused Run. Therefore, before proceeding with the Focused Run

configuration below, Detailed information regarding client copy is available at

https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/7.5.6/en-

US/4d7ce15219a00f88e10000000a42189b.html.

Create a new productive client and perform a local client copy as following:

• Add following profile parameter in RZ11: login/no_automatic_user_sapstar = 0

• Restart the Focused Run ABAP instances

• Login into the Focused Run system and create new client using transaction SCC4

• Login into the created client, using user: SAP*, and standard password: PASS

• Perform a copy into this new client, using transaction SCCL, and profile SAP_CUST, from source client 000

• Delete profile parameter login/no_automatic_user_sapstar

Proceed with the next configuration activities, using this created production client.

https://apps.support.sap.com/sap/support/mp

http://service.sap.com/~sapidb/011000358700000828172012E

http://service.sap.com/~sapidb/011000358700000828172012E

https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/7.5.6/en-US/4d7ce15219a00f88e10000000a42189b.html

https://help.sap.com/viewer/4a368c163b08418890a406d413933ba7/7.5.6/en-US/4d7ce15219a00f88e10000000a42189b.html



CUSTOMER


4.6.2 Focused Run Administration User

Please perform initial configuration of Focused Run with an administration user. The necessary privileges are

described in Security Guide chapter Proposal for Setup User.

4.6.3 Checking and Adjusting SAP NetWeaver ABAP Profile Parameters

Information on how to maintain SAP NetWeaver ABAP parameters can be found at:

https://help.sap.com/saphelp_nw75/helpdata/en/5a/860a509ece466ce10000000a423f68/content.htm

The parameter values specified below are minimum requirements 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 the

individual scenarios a larger scaling of the parametrization might be necessary.

Adjust the amount of Dialog and Batch Work Processes on each ABAP instance. Recommendation is to operate at

least 50 DIA and 25 BTC work processes per instance. Further details about work process configuration, number

of work processes and dependencies, refer to SAP notes 2190597, 39412 and 9942.

Finally restart the Focused Run ABAP system, in case you adjusted some parameters.

Parameter Recommendation Remark

icm/host_name_full Set to full qualified hostname of the

application server. See also

http://help.sap.com/saphelp_nw70ehp2

/helpdata/en/48/3c5d3df7e771b9e1000

0000a421937/frameset.htm

icm/server_port_X Typical values:

• icm/server_port_0 =

PROT=HTTPS, PORT=443,

TIMEOUT=300,

PROCTIMEOUT=300


PROT=HTTP, PORT=80,

TIMEOUT=300,

PROCTIMEOUT=300


PROT=SMTP,PORT=25000,

TIMEOUT=180

Set up one HTTP, HTTPS and SMTP port

icm/max_conn 8.000 SAP note 2007212

login/system_client <productive client number> Provide the productive client number. See

chapter 4.5.1 Create Productive client.

https://help.sap.com/saphelp_nw75/helpdata/en/5a/860a509ece466ce10000000a423f68/content.htm





http://help.sap.com/saphelp_nw70ehp2/helpdata/en/48/3c5d3df7e771b9e10000000a421937/frameset.htm




18

CUSTOMER




Parameter Recommendation Remark

PHYS_MEMSIZE >= 20.480 SAP Note 2085980

The profile parameter PHYS_MEMSIZE

determines how much of the entire main

memory is to be used by the SAP system.

The parameter is entered during

installation in accordance with the entry.

The standard value for PHYS_MEMSIZE is

the size of the main memory [RAM].

abap/shared_objects_size_MB

>=1.025

abap/buffersize 8.000.000

rdisp/elem_per_queue 4.000

rdisp/max_wprun_time 3.600

rdisp/tm_max_no >=8.000

rsdb/prefer_join_with_fda 0 Disable fast data access for HANA to

avoid inconsistencies. See SAP Note

2037385

dbs/hdb/deferred_lob_writing 0 Add this parameter to disable the

deferred LOB writing

rsdb/ntab/entrycount 1.500.000

rsdb/cua/buffersize 70.000

rsdb/obj/max_objects 80.000

rsdb/esm/buffersize_kb 8.192

rsdb/otr/max_objects 5.000

rsdb/otr/buffersize_kb 8.192

sap/bufdir_entries 15.000

zcsa/system_language E Only English is supported as logon

language for Focused Run

zcsa/second_language E

http/security_context_cache_size 8.000

ssl/client_ciphersuites 902 More details about ciphersuites can be

found in Note 510007






CUSTOMER


4.6.4 Update SAP Kernel

Kernel 7.45 64-BIT UNICODE SP320

4.6.5 Update of SAPUI5 Runtime Environment

Install SAPUI5 1.44.7 as described in SAP Notes 2424070.

Note:

You can look-up under (Version: 1.44) the full version of the currently installed SAPUI5 component, by opening the

following URL on your Focused Run system: http(s)://<fqdn-

hostname>:<port>/sap/public/bc/ui5_ui5/index.html

To display this URL page, first activate the associated service, by:

1. Logon to your SAP ABAP system

2. Start transaction SICF

3. In the filter screen provide as Service Name ui5_ui5

4. Press Execute (F8)

5. Search for /sap/public/bc/ui5_ui5/

6. Right click on the service name and select "Activate Service". Confirm the activation by click on "Yes" in

confirmation dialog.

4.6.6 Implementing SAP Notes

Please implement the following SAP Notes in your Focused Run system using transaction SNOTE (see

http://help.sap.com/saphelp_nw75/helpdata/en/48/b41a66fc096ff4e10000000a42189b/frameset.htm for

background information).

• 2401534 - FilterBarValueHelp: Support EXIT via closing window

• 2380644 - Performance metric not working in FRUN (Attention: manual post-activity needed)

• 2477938 - MAI Configuration fails with: "Error An exception has occurred that was not caught. when retrieving

results from parallel task

• 2478062 - Correct link to Advanced Monitoring in Fiori Launch Pad

• 2471053 - Advanced Integration Monitoring (FRUN FP01) - General corrections

• 2478067 - Fiori Setup: Activate odata services for identical service names

• 2460338 - Correction for Unified Rendering SAP_UI NW751 TCI 005

• 2481546 - No Agent Configuration generated for Introscope metrics

• 2414364 - Focused Run Solution Manager - RCD - The Manual Content Upload is not working

• 2486584 - Fehler im Report SRSM_AMA_UPLOAD_BINARY bei Ausführung des externen Kommando

SAPCAR

• 2490246 - Problem with deleted metrics/events/alerts


http://help.sap.com/saphelp_nw75/helpdata/en/48/b41a66fc096ff4e10000000a42189b/frameset.htm












20

CUSTOMER




• 2506476 - Blue and Black metric in system monitoring

• 2503569 - RCSU_MANUAL_UPLOAD error message FRUN

• 2509512 - Self Monitoring: System view gives a dump when all systems are displayed

• 2520332 - Global alert consumer settings not configured correctly

• 2524385 - Activity "Activate System" within automatic system configuration does not show termination

message

• 2485500 - System Analytics: Corrections for FRUN FP01

• 2548713 - Wrong date format displays in Alert List Table

4.7 Prepare SLD Namespace

Before enabling the landscape management database (LMDB), you must provide the latest CIM Model and SAP

CR Content from SAP Support Portal in an empty SAP Netweaver Java SLD system. You can use any existing

SLD, elsewise there is no need a dedicated SLD. Important is, that the namespace used in the SLD system must

not contain any data sent by SLD data suppliers, therefore it is recommended to create a new namespace in the

desired SLD (e.g. "crref") and update the CIM Model and CR Content to the latest available version inside this

namespace.

The update of this is described in SAP Note "669669 - Update of SAP System Component Repository in SLD".

Updating the CIM Model and CR Content in this SLD namespace is a continuous task, which must be performed at

least every 3 months.









Implementing Focused Run 1.0

CUSTOMER


5 Implementing Focused Run 1.0

5.1.1 Preparing NetWeaver Basic Operation

If not already performed, as part of the SAP NetWeaver installation procedure (See 4.4 Implementing SAP

NetWeaver with Focused Run Using Up-to-Date installation process), make sure to have completed the

Automated Initial Setup, with the task list SAP_BASIS_SETUP_INITIAL_CONFIG, as described in

https://websmp103.sap-ag.de/~sapidb/012002523100010638182014E.

Aditionally to what is needed for any other SAP NetWeaver ABAP system, in the context of Focused Run you need

to run the following task. Therefore:

1. Log on to your SAP ABAP system.

2. Start transaction: STC01

3. On the Task Manager for Technical Configuration screen, insert SAP_BASIS_SETUP_INITIAL_CONFIG in the

Task List field.

4. Press Generate Task List Run (F8)

5. Press Skip All Tasks (F7)

6. Enable task: BGRFC - Create bgRFC Supervisor Destination (SBGRFCCONF)

7. Press 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.

As Focused Run applications makes high volume usage of application log, ensure, that a proper housekeeping for

the application log 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.

5.1.2 Configuring Usage of Web Based Front-End Application URLs

For the usage of web based applications in Focused Run, the URLs to jump between applications or to jump from

SAPGUI to browser are generated automatically (see

http://help.sap.com/saphelp_nw75/helpdata/en/48/6a82a684f4350ce10000000a42189d/content.htm for

background information).

To ensure that all URLs are using the correct hostname and port (ICM or SAP Web Dispatcher) the following

configuration must be entered in table HTTPURLLOC (via transaction SE16). More detailed information is

provided at

http://help.sap.com/saphelp_nw75/helpdata/en/48/6b380633f0350ce10000000a42189d/frameset.htm

o Client: productive client

o SORT_KEY: 0100

o PROTOCOL: HTTPS

https://websmp103.sap-ag.de/~sapidb/012002523100010638182014E


http://help.sap.com/saphelp_nw75/helpdata/en/48/6a82a684f4350ce10000000a42189d/content.htm

http://help.sap.com/saphelp_nw75/helpdata/en/48/6b380633f0350ce10000000a42189d/frameset.htm

22

CUSTOMER




o APPLICATION: *

o HOST: FQDN of load balancer or central application server ICM,

o PORT: HTTPS port of load balancer or central application server ICM

5.1.3 Setup Load Balancing

In Focused Run we have several applications (including batch processing) and web services requiring resources of

the ABAP applications servers. To support separation of individual workloads, different types of load balancing for

the NetWeaver ABAP stack and even beyond are used:

• Logon Groups: for distribution of dialog workload

Dialog users can explicitly state an individual server or logon group once they enter the system. Logon groups

are defined in transaction SMLG.

• RFC Server Groups: for distribution of parallel processing activities

During execution of Focused Run high volume processing jobs, the execution is distributed via asynchronous

RFC calls. The RFC server groups can be defined in transaction RZ12

• Job Server Group (maintained in ABAP transaction SM61): for distribution of batch workload

background jobs can be scheduled using dedicated execution server groups to avoid resource conflicts using

transaction SM61. In the job scheduling UI the server group can be entered as Execution Target.

In Focused Run we differentiate the following types of workload:

• Dialog and occasional background processing (Reoccurring load)

• Continuous high frequency processing (Repetitive load)

For initial setup it is recommended to split the load across two different application server groups as follows:

Instance types Logon Groups Job Server Groups RFC Server Groups

Repetitive load STREAMING FRN_JOB_INBOUND FRN_RFC_MAI

FRN_RFC_CF

Reoccurring load PUBLIC FRN_JOB_PUBLIC (*) FRN_RFC_SDA

FRN_RFC_SSI

FRN_RFC_SRAF

(*) all jobs scheduled manually in this guide should use execution target FRN_JOB_PUBLIC. Note: The high

frequency background jobs are scheduled via API.

For productive usage of Focused Run it is recommended to provide at least two instances for each instance type

to ensure high availability of processing resources for each instance type.

Next ensure that all inbound data streaming ICF endpoints in Focused Run only use the logon group STREAMING.

This can either be done in the hardware load balancer configuration or in case of SAP Web dispatcher by assigning

the logon group streaming to all ICF services mentioned as " Inbound data streaming channels" services in section

Preparing UI Environment [20].



CUSTOMER


5.2 Configuration of Focused Run Application Foundation

5.2.1 Preparing UI Environment

Execute task list SAP_GW_FIORI_ERP_ONE_CLNT_SETUP with Variant SAP&FRUN_INIT to prepare the UI

environment and the common used data streaming services for all Application Foundation components, by

activating OData and SICF service,

Procedure


9. Start transaction: STC01

10. On the Task Manager for Technical Configuration screen, insert SAP_GW_FIORI_ERP_ONE_CLNT_SETUP in

the Task List field.

11. Press Generate Task List Run with Variant (CTRL+F8)

12. Choose the variant SAP&FRUN_INIT

13. Press 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:

http://help.sap.com/fiori_bs2013/helpdata/en/bf/d1b053a647e842e10000000a4450e5/frameset.htm

Note: The OData and SICF services activated by this step are listed in the Appendix.

5.2.2 Creating Technical Users for Application Foundation

Before you continue with the next steps, refer to the security guide, chapter "Technical Users", in order to create

the required technical users on the Focused Run system, including:

• Template users (named like TPL_FRN*)

• Background processing users (named like FRN_BTC*)

5.2.3 Preparing Simple Diagnostics Agent Distribution

To distribute the Simple Diagnostics Agent (SDA) automatically to all hosts connected to Focused Run, provide

the binaries of the latest Simple Diagnostics Agent version and OS relevant SAP JRE 8.1 to the Focused Run

central system. The current version of the binaries can be retrieved from SAP Support Portal as follows.

• 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

http://help.sap.com/fiori_bs2013/helpdata/en/bf/d1b053a647e842e10000000a4450e5/frameset.htm

https://launchpad.support.sap.com/#/softwarecenter

24

CUSTOMER




o Focused Run

o Focused Run 1.0

o Downloads

o Comprised Software Component Versions

Download the latest available SDA (Simple Diagnostics Agent) and SAP JRE (Java Runtime Environment) for any

other OS, which is operated and supported in managed system landscape (including the Focused Run system

itself).

Currently the following platforms are supported:

• IBM AIX

• HP-UX on IA64

• Linux on Power BE & LE

• Linux x86_64

• Oracle Solaris SPARC

• Oracle Solaris x86

• Microsoft Windows Server on x86_64

To upload the binaries to Focused Run, run report: SRSM_AMA_UPLOAD_BINARY using transaction SA38.

1. Select Batch Upload

2. In the Pop-up select the folder, where you have downloaded all SDA and JRE files

3. Press Execute (F8)

4. After the upload of all files is finished a complete list of all SDA and JRE versions uploaded to focused Run is

displayed.

Note: At the time a new SDA version is released on the SAP Support Portal, repeat the above described procedure

for all supported OS platforms, and this before triggering a Simple Diagnostics Agent update, using the Agent

Administration application (available in the Launchpad). The current version of agent binaries uploaded in

Focused Run can be determined by running report: SRSM_AMA_UPLOAD_BINARY with option Display Content

only.

5.2.4 Simple System Integration

5.2.4.1 Enabling User Management for Back Destination Users

For user management of communication users in Focused Run, two different approaches are available.



CUSTOMER


1. Integration with a customer user management solution, handling the user creation/update process and

returns to Focused Run only the active passwords for the created users. All user handling and configuration in

such cases shall be done in the user management solution, and in Focused Run the BAdI enhancement spots

are available for integration purposes.

2. If no appropriate user management solution is available, use the build-in solution in Simple System

Integration. To enable this solution perform the following steps:

o If not already done, create the technical user FRN_IADM_SSI, in the Focused Run system. This user has

privileges to create/change and delete users. Refer to the security guide for further details.

o Create the RFC Destination SSI_USER_ADMIN_CONNECTION to the Focused Run system itself, using the

above-created user. (Details about handling RFC destinations is available in the SAP NetWeaver

Operations guide at

http://help.sap.com/saphelp_nw75/helpdata/en/48/8965b484b84e6fe10000000a421937/content.ht

m). The following parameters must be maintained:

o Connection Type: 3

o Leave the Target Host empty

o Language: EN

o Client: <Productive Focused Run client>

o User: FRN_IADM_SSI

o Password: <Password of user FRN_IADM_SSI>

o Provide for the field Authorization for Destination the value SSI_CONF

Note: Only users with permission S_RFC_ADM will be able to maintain this RFC destination.

o Run Report P_SSI_PREPARATION in SA38 with the following parameters

http://help.sap.com/saphelp_nw75/helpdata/en/48/8965b484b84e6fe10000000a421937/content.htm

http://help.sap.com/saphelp_nw75/helpdata/en/48/8965b484b84e6fe10000000a421937/content.htm

26

CUSTOMER




5.2.5 Landscape Management Database

Prerequisite

A SLD namespace for Focused Run CIM Model and CR Content must be prepared as described in chapter 4.6

"Prepare SLD Namespace" of this document.

Activities

Start Setup using transaction LMDB_SETUP.

• In Step 1 maintain the SLD Parameters:

o Object Server: LMDB_<SID>_<hostname of central server>

o URL: Hostname of your SLD Server

o Namespace: the namespace in SLD where the CRContent and CIM Model should be synchronized from,

please make sure, that this namespace does not contain data for Managed Systems and also that no SLD

data supplier can report to this namespace.

o User: pleas provide a user with credentials for SLD Content Sync privileges on the SLD server

• Run transaction LMDB_SETUP again. A new window will open. Go to the LMDB synchronization step. If the

content synchronization that was created before has inactive status, select it and choose Activate. A message

about CIM model version comparison will appear. Choose Yes to confirm.



CUSTOMER


• Note: A new job SAP_LMDB_LDB_<number> is scheduled by this activity. Check the job log of the scheduled

job. If the job runs fine without errors for longer than 5 minutes, the configuration can continue.

5.2.5.1 Local Network Setup

LMDB namespaces are used to group all systems belonging to one logical network. As prerequisite for all

applications the Focused Run Managing system must be also available. Therefore, during setup of LMDB a default

namespace "LOCALNETWORK" is created. The local network can be fully utilized 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,

please start report RLMDB_CUSTOMER_NETWORK_TOOLS using transaction SA38 and provide the following

input.

1. Edit network LOCALNETWORK, and maintain the following values

o Caption: meaningful description for the local admin network e.g. Local Network

o Customer ID: 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 Other fields: Leave them empty (do not use proxy or fencing in local network)

2. Now, activate the network LOCALNETWORK shall be activated by running the following reports in transaction

SA38 with the parameters shown below. The sapadm password provided must the password used for OS

user sapadm on all hosts of the Focused Run system.

o Run Report SSI_ADMIN_NETWORK_INITIALIZE

o Run Report SSI_ADMIN_NETWORK_ACTIVATE

28

CUSTOMER




3. Finally, remind to specify once the password of the following technical users, being generated by the SSI

Configuration of the Focused Run system. 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_SLDS_<CID>, also known as SLD_DS in the below report

User on SLDR to authenticate Data Suppliers sending SLD payloads, which are then forwarded to

maintained outbound connections.

o FRN_EWA_<CID>

Therefore, proceed as follow:

o Start SA38 transaction

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, as you type-in the password only once.

5.2.5.2 Creating Business Partner for Local Network

In Focused Run, each system has a direct relationship to one business partner in the relationship role "Customer".

Therefore also for all systems registered in the local network such a business partner must be created. In addition,

the external identification to local network must be provided to allow matching of maintained Customer IDs (CID)

to dedicated business partners.



CUSTOMER


Activities

1. Create a new Organization using transaction BP in BP Role "Business Partner (gen.)"

2. Maintain name in tab address data.

3. Identification Numbers in tab identification

o IDType: FRUN01 (CID-Customer ID)

o Identifcation Number: 3 character CID (as maintained in step "Local Network" [24])

5.2.5.3 Registering Focused Run System in LMDB

1. Perform the Outside Discovery for all hosts of Focused Run system itself, as described in the managed

system preparation guide.

Note: Remind to also double check the SAP Host Agent version.

2. To send data to Focused Run ABAP Stack, maintain the SLD Data Supplier for the following (please refer to

Managed System Configuration Guide for detailed information):

o ABAP (RZ70, use HTTP(s) destination to send data),

o SAPStartSRV (sldreg)

o HANA (sldreg + HDBLCM)

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).

30

CUSTOMER




5.2.6 Setup Communication with SAP Support Backbone

In Focused Run, data exchange with SAP support portal is used for system data and license management. There

are two situations:

• 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.

Single Connection for Communication with SAP Support Backbone

Creation of RFC destination SAP-OSS:

• Using transaction SM59, find RFC destination SAPOSS and perform a connection test. If it fails, adjust the

destination as required. See SAP note 33135.

• Create a S-User in the SAP support portal for the SAP customer number of the Focused Run System. Note:

The S-user requires the following authorizations:

o Maintain System Data

o Request License Keys

o Software Download

• Again, in transaction SM59, create the RFC destination SAP-OSS, by copying the previously verified SAPOSS

destination, and perform the following adjustments in this SAP-OSS RFC destination:

o Enter in “Logon & Security” the name and password of your S-user created as described above

o Check that the load distribution group of both destinations is 1_PUBLIC

o Save your changes

o Check and test the new RFC connection

• With transaction SE38, run report AI_SC_REFRESH_READ_ONLY_DATA

• Finally, using transaction AISUSER, create an entry for Focused Run user FRN_BTC_SMP and any relevant

dialog user.

Multiple individual Connections for each Customer for Communication with SAP Support Backbone

Activation of the multiple connection BADI:

• Go to transaction SE19

• Choose Enhancement Implementation: AI_SDK_SP_RFC_RP

• Edit the Enhancement Implementation and mark the flag "Implementation is active"



CUSTOMER


• If asked provide the SSCR registration key for the object

• Active the Enhancement Implementation

Creation of RFC destinations:

• Using transaction SM59, find RFC destination SAPOSS and perform a connection test. If it fails, adjust the

destination as required. See SAP note 33135.

• Create one S-User in the SAP support portal each customer number of the systems being managed by

Focused Run. Note: The S-users require the following authorizations:

o Maintain System Data

o Request License Keys

o Software Download

• Again, in transaction SM59, create per relevant customer number, one RFC destination, by copying the

previously verified SAPOSS destination. These RFC destinations shall be named, like:

SM_SP_<Customer_Number_on_10_digits>. Each time perform also the following adjustments in these new

RFC destinations:

o Enter in “Logon & Security” the name and password of the S-user corresponding to the customer number

from the RFC destination name

o Check that the load distribution group of both destinations is 1_PUBLIC

o Save your changes

o Check and test the new RFC connection

• Finally, using transaction AISUSER, create an entry for Focused Run user FRN_BTC_SMP and any relevant

dialog user.

5.2.7 Setup Application Foundation Background Processing

Schedule the following background jobs

32

CUSTOMER




Jobname ABAP Programs(s) Step User Start Time Frequency

SAP_FRN_WMM_TRIGGER WMM_TRIGGER FRN_BTC_WMM immediately every

minute

SAP_FRN_WMM_CONSTITENT

S

WMM_GENERATE_CONSTITUE

NTS

FRN_BTC_WMM 0:10 am daily

SAP_FRN_COLLECT_USAGE_D

ATA

FRUN_USAGE_UPDATE FRN_BTC_SMP 1:00am daily

SAP_FRN_SYNC_SUPPORT_P

ORTAL

Multipe Step Job with the

following steps:

1:

AI_SC_REFRESH_READ_ONLY_

DATA

2:

AI_SC_UPLOAD_SYSTEM_DAT

A

FRN_BTC_SMP 0:30am daily

SAP_FRN_CNM_NOTIFICATIO

N

CNM_SCHEDULED_NOTIFICAT

ION

FRN_BTC_CNM Immediately Hourly

SAP_FRN_AF_SCHEDULER SRAF_SCHEDULER FRN_BTC_SRA immediately Every

minute

SAP_FRN_AF_HOUSEKEEPER SRAF_LOG_HOUSEKEEPING FRN_BTC_SRA 00:30 Every day

SAP_FRN_AEM_HOUSEKEEPI

NG

AEM_DIRECTORY_HOUSEKEE

PING

FRN_BTC_AEM 01:30 daily

5.2.8 Data Collection Framework and Alert Calculation

1. Call Setup transaction MAI_TOOLS, activate the expert mode, and then go to the Administration tab.

2. Call "Maintain Configuration Parameters" and maintain the following parameters and values:

o DIRDESTGRP: FRN_RFC_MAI (RFC group to be used by DIR for configuration)

o DIRMAXPERC: 20 (Maximum percentage of available DIA WPs used by DIR)

o ECEDESTGRP: FRN_RFC_MAI (RFC group to be used by ECE for calculation)

o MAXWPSERC: 40 (Maximum percentage of available DIA WPs used by ECE)

3. Call "Schedule all MAI jobs with default variant"

4. To activate the default Work Mode settings, run Report ACR_SET_DEFAULT_GLOBAL_WM once.

5.2.9 Content Update

To ensure latest content is available in Focused Run please perform the content update as described in SAP Note

2369335 if new content is available.




CUSTOMER


5.2.10 Activate System Monitoring for Focused Run System

Please execute the "Simple System configuration" for the Focused Run ABAP System to ensure the infrastructure

can be used for central monitoring.

5.2.11 Self-Monitoring

Configure Self-Monitoring: start mai_tools (expert mode).

Configuration: Select “Configure Central Components”

34

CUSTOMER



Business Scenarios of Focused Run

6 Business Scenarios of Focused Run

6.1 Advanced System Management

6.1.1 Preparing Use-Case

To prepare the UI environment for this use case, execute the task list SAP_FRUN_SETUP_USECASE with variant

SAP&FRUN_ASM in transaction STC01.

Procedure


2. Call the following transaction:

Transaction Code 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). And choose variant SAP&FRUN_ASM

5. 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 error analysis using the task

documentation provided for each task.


6.1.2 Setup Application Specifics

6.1.2.1 SAP Early Watch Alert

Prerequisites:

Before configuring SAP Early Watch Alert (EWA), the following prerequisites must be met:

• ST-PI 740 SP4 or higher must be implemented in Focused Run

• In Managed System ST-PI 740 SP4 or ST-PI 2008_1_7xx SP14 or higher must be implemented

• Destination SAPOSS is maintained (for details please refer to SAP Note 812386 - RFC connection to the

SAPNet R/3 front end)




CUSTOMER


Procedure:

Activate the processing of EWA data

1. Start transaction SDCCN

2. Go to ‚Utilities‘ and choose ‘activate’

3. Click "Continue" on question if SDCCN should be activated in local system

4. Accept to create RFC destination SDCC_OSS

6.1.2.2 System Analytics Setup

Configure the Data Aggregation for System Analytics.

Procedure:

1. Start transaction SE38

2. Run Report SYSANA_CONFIGURATION with default settings

6.1.3 Background Jobs for ASM

Schedule the following background jobs using transaction SM36

JOBNAME REPORT Step User Start Time Recurrenc

e interval

SAP_FRN_SAM_UTILITY SAM_CREATE_AP_CMP FRN_BTC_SA

M

0:30 am daily

SAP_FRN_EWA_SEND_REPO

RT

FRUN_DOWNLOADS_REPORT FRN_BTC_EW

A

Immediatel

y

Hourly

SAP_FRN_LIC_DISTRIBUTIO

N

RAGS_MAINT_KEY_COLLECTO

R

FRN_BTC_SM

P

01:30 daily

SAP_FRN_SA_HOUSEKEEPE

R

WEA_AGG_STORE_PARTITIONI

NG

FRN_BTC_AS

M

02:00 Every day

SAP_FRN_ESM_SCHEDULER SRAF_SCHEDULER FRN_BTC_SR

A

immediatel

y

Every

minute

36

CUSTOMER




6.2 Advanced User Monitoring



SAP&FRUN_AUM in transaction STC01.

Procedure





List field.

4. Choose Generate Task List Run with Variant (CTRL+F8). And choose variant SAP&FRUN_AUM





6.2.2 Real User Monitoring Specific Setup Steps

Real User Monitoring table partitioning & batch job scheduling

Check if user <FRN_BTC_RUM> has been created according to security guide. Afterwards run Report

/RUM/SETUP using transaction SA38 to initialize Real User Monitoring

6.2.3 Background Jobs for AUM


JOBNAME REPORT Step User Start Time Recurrence

interval

SAP_FRN_TRACE_HK E2E_TRACE_DELETE FRN_BTC_TA 1:00 am daily



CUSTOMER


6.3 Configuration and Security Analytics



SAP&FRUN_CSA in transaction STC01.

Procedure





List field.

4. Choose Generate Task List Run with Variant (CTRL+F8) and choose variant SAP&FRUN_CSA





6.3.2 Additional Configuration for Configuration Validation

Execute Report COF_SETUP using transaction SA38

6.4 Advanced Integration Monitoring



SAP&FRUN_AIM in transaction STC01.

Procedure



38

CUSTOMER






List field.

9. Choose Generate Task List Run with Variant (CTRL+F8) and choose variant SAP&FRUN_AIM





6.4.2 Background Jobs for AIM


JOBNAME REPORT Step User Start Time Recurrence

interval

SAP_FRN_AIM_HOUSEKEEPING /IMA/HOUSEKEEPING FRN_BTC_AIM 1:00 am daily


Appendix

CUSTOMER


7 Appendix

7.1 OData and SICF services activated by STC01 task lists

7.1.1 SAP_GW_FIORI_ERP_ONE_CLNT_SETUP with Variant SAP&FRUN_INIT

OData Services for Focused Run Application Foundation

Application Area OData Services

Focused Run UI runtime UI5LIB_SRV

TECHMON_UI5_TABS_SRV

LMDB_FILTERBAR_SRV

SOLMAN_COMMONS_SRV

Self-Monitoring SFM_STATUS_ODATA_SERVICE

Simple System Integration SSI_CONFIGURATION_SRV

Alert Inbox ACC

ALERTTICKER_SRSM_SRV

IT Calendar and Workmode

Management

WMM_DATA_SRV

IT_CALENDAR

Notification Management CNM_SRV

SICF Services for Focused Run Application Foundation

Webdynpro Runtime /sap/bc/webdynpro

/sap/public/ping

/sap/public/bc/ur

/sap/public/bc/icons

/sap/public/bc/icons_rtl

/sap/public/bc/webicons

/sap/public/bc/pictograms

/sap/public/bc/webdynpro/mimes

/sap/public/bc/webdynpro/ssr

/sap/bc/webdynpro/sap/wdhc_help_center

Webgui and NetWeaver services /sap/bc/gui/sap/its/webgui

40

CUSTOMER



Appendix

/sap/public/myssocntl

/sap/bc/srt/wsdl

/sap/public/opu

Focused Run UI runtime /sap/bc/ui5_ui5/sap/frunui5lib

/sap/bc/bsp/sap/ai_tools_dnld

/sap/bc/ui5_ui5/sap/lmdbfilterbar

/sap/bc/webdynpro/sap/urlapi_application_manager

/sap/url/go

/sap/bc/webdynpro/sap/documentation/

/sap/bc/ui5_ui5/sap/bsp_sise_rm_ui5

/sap/bc/ui5_ui5/sap/bsp_ags_ui5_doc

Landscape Management Database /sap/bc/cim/ds

/sap/bc/cim/cimom

/sap/bc/cim/sync

/sap/bc/webdynpro/sap/lmdb_simple_setup

/sap/bc/webdynpro/sap/LMDB_WDA_EXPL_OIF

/sap/bc/webdynpro/sap/LMDB_WDA_GENB_OIF

/sap/bc/webdynpro/sap/LMDB_WDA_EXPL_HELP

/sap/bc/webdynpro/sap/LMDB_FPM_OVP_COMPONENT

Simple System Integration /sap/bc/webdynpro/sap/msc_ts_search_fpm_app

/sap/bc/ui5_ui5/sap/ssi_config

Simple Diagnostics Agent /sap/bc/webdynpro/sap/srsm_host_search_fpm_app

/sap/srsm_sda

/sap/bc/webdynpro/sap/srsm_agent_mass_update_app

Self-Monitoring /sap/bc/ui5_ui5/sap/metric_moni_sfm

/sap/bc/webdynpro/sap/solman_self_monitoring_app

Inbound data streaming channels /sap/srsm_mai/push_metrics

/sap/bc/sdf/sdcc/

/sap/bc/rest/E2E_TA_COL

/sap/bc/rest/cof

/sap/bc/rest/rumdataservice

/sap/bc/rest/statraggdatasrv

Monitoring Infrastructure /sap/bc/webdynpro/sap/fpm_dpc_role_assignment

/sap/bc/webdynpro/sap/wda_default_settings

/sap/bc/webdynpro/sap/wda_config_wizard

/sap/bc/webdynpro/sap/wda_consumer_variant

/sap/bc/webdynpro/sap/wda_threshold_information


Appendix

CUSTOMER


/sap/bc/webdynpro/sap/wdc_transport_templates

/sap/bc/webdynpro/sap/maintenance_tool

/sap/bc/webdynpro/sap/wda_mai_rep_html

/sap/bc/webdynpro/sap/WDA_AC_DIR_BROWSER

/sap/bc/webdynpro/sap/wda_sise_update_content

Alert Inbox /sap/bc/ui5_ui5/sap/alertdetail

/sap/bc/ui5_ui5/sap/alertinboxapp

/sap/bc/apc/sap/alert_ticker_srsm

Guided Procedures Framework /sap/bc/webdynpro/sap/ags_gpa_browser

/sap/bc/webdynpro/sap/ags_gpa_gp

/sap/bc/webdynpro/sap/ags_gpa_logbook

/sap/bc/webdynpro/sap/wd_sise_fwk_wizard

/sap/bc/webdynpro/sap/ags_gpa_plugin_mngt

IT Calendar and Workmode

Management

/sap/bc/ui5_ui5/sap/itcalendar

/sap/bc/ui5_ui5/sap/workmode_app

Notification Management /sap/bc/ui5_ui5/sap/instant_notif

/sap/bc/ui5_ui5/sap/cnm_repository

/sap/bc/ui5_ui5/sap/notif_templ_app

/sap/bc/ui5_ui5/sap/notif_config

/sap/bc/ui5_ui5/sap/notif_schedule

/sap/bc/ui5_ui5/sap/notif_rec_list

/sap/bc/webdynpro/sap/dswp_na_grp_powl

/sap/bc/webdynpro/sap/dswp_na_generic_notif

/sap/bc/webdynpro/sap/dswp_na_configure_servers

Scheduling Management /sap/bc/webdynpro/sap/wd_sraf_admin_portal

7.1.2 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_ASM

OData Services for Focused Run ASM


System Monitoring AI_SYSMON_SRV

AI_SYSMON_OVERVIEW_SRV

System Analytics WEA_SRV

42

CUSTOMER



Appendix


Service Availability Management SAM_SRV

SICF Services for Focused Run ASM

System Monitoring /sap/bc/ui5_ui5/sap/sr_sysmon

/sap/bc/ui5_ui5/sap/metricmonitor

/sap/bc/webdynpro/sap/troubleshoot

Advanced Monitoring /sap/bc/webdynpro/sap/advmon

System Analytics /sap/bc/ui5_ui5/sap/wea

/sap/bc/webdynpro/sap/wea_expert_configuration

Statistics Aggregate /sap/bc/webdynpro/sap/wd_statragg_cockpit

Service Availability Management /sap/bc/ui5_ui5/sap/sam_appl

License Management /sap/bc/webdynpro/sap/WD_AGS_MK_LIC_MNGT

7.1.3 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_AUM

OData Services for Focused Run AUM


Real User Monitoring /RUM/UI5_SRV

Trace Analysis E2E_TRACE_UI_SRV

SICF Services for Focused Run AUM

Real User Monitoring /sap/bc/webdynpro/rum/WDA_COCKPIT

/sap/bc/ui5_ui5/RUM/E2ERUM

/sap/bc/webdynpro/rum/wd_alerting

Trace Analysis /sap/bc/ui5_ui5/sap/trace

/sap/bc/ui5_ui5/sap/tracejslib

/sap/bc/ui5_ui5/sap/TraceExt

/sap/srsm/E2E_trace_upl


Appendix

CUSTOMER


7.1.4 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_AEM

SICF Services for Focused Run AEM

Inbound Connector /sap/bc/srt/rfc/sap/sap_aem_inbound_connector

7.1.5 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_CSA

OData Services for Focused Run CSA


Configuration Validation CONFIG_VALIDATION_SRV

COF_ODATA_SRV

SICF Services for Focused Run CSA

Configuration Validation /sap/bc/ui5_ui5/sap/srsm_config_val

/sap/bc/webdynpro/sap/WD_CCDB_SCI

/sap/bc/webdynpro/sap/WD_COVA_TAR_MAINT

/sap/bc/ui5_ui5/sap/cof_admin_comp

7.1.6 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_AIM

OData Services for Focused Run AIM


Integration Monitoring /IMA/UI5_SRV

Exception Management EXM_UI_SRV

44

CUSTOMER



Appendix

SICF Services for Focused Run AIM

Integration Monitoring /sap/bc/ui5_ui5/ima/app

/sap/bc/webdynpro/sap/wda_s2c_cs_overview

www.sap.com/contactsap


No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP SE

or an SAP affiliate company

SAP and other SAP products and services mentioned herein as well

as their respective logos are trademarks or registered trademarks of

SAP SE (or an SAP affiliate company) in Germany and other

countries. All other product and service names mentioned are the

trademarks of their respective companies. Please see

www.sap.com/corporate-en/legal/copyright/index.epx#trademark

for additional trademark information and notices.

Material Number:

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

focused run for sap solution manager - sap help portal · pdf filemaster guide document...

Documents