Focused Run for SAP Solution Manager

Master Guide

Document Version: 1.0 – 2016-10-21

CUSTOMER

Focused Run for SAP Solution Manager

2

CUSTOMER

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


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 on SAP Service Marketplace at http://service.sap.com/instguides.

Version Date Change

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

4

CUSTOMER



Table of Contents

Table of Contents

1 Getting Started .............................................................................................................................. 6 1.1 About this Document ............................................................................................................................ 6 1.2 Acronyms 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 Implementing Focused Run 1.0 ................................................................................................. 15 4.1 Check installed SAP HANA revision .................................................................................................... 15 4.2 Check and adjust SAP HANA parameters .......................................................................................... 15 4.3 Implementing SAP NetWeaver with Focused Run Using Up-to-Date installation process ........... 15 4.4 Post Installation of SAP NetWeaver ABAP Server for Focused Run Usage ....................................16

4.4.1 Create productive client ......................................................................................................16 4.4.2 Focused Run administration user ......................................................................................16 4.4.3 Checking and Adjusting SAP NetWeaver ABAP Profile Parameters ...............................16 4.4.4 Update of SAPUI5 Runtime Environment ..........................................................................18 4.4.5 Implementing Notes ............................................................................................................18 4.4.6 Preparing NetWeaver Basic Operation ..............................................................................19 4.4.7 Configuring Usage of Load Balancer ..................................................................................19 4.4.8 Setup Load Balancing ..........................................................................................................19

4.5 Configuration of Focused Run Application Foundation ................................................................... 20 4.5.1 Preparing UI Environment .................................................................................................. 20 4.5.2 Creating Technical Users for Application Foundation ...................................................... 21 4.5.3 Preparing Simple Diagnostics Agent Distribution ............................................................ 21 4.5.4 Simple System Integration................................................................................................. 22 4.5.5 Landscape Management Database ................................................................................... 23 4.5.6 Setup Application Foundation Background Processing .................................................. 26 4.5.7 Data Collection Framework and Alert Calculation ........................................................... 27 4.5.8 Content Update ................................................................................................................... 27 4.5.9 Self-Monitoring.................................................................................................................... 27

5 Business Scenarios of Focused Run ......................................................................................... 28 5.1 Advanced System Management ........................................................................................................ 28

5.1.1 Preparing Use-Case ............................................................................................................ 28 5.1.2 Background Jobs ................................................................................................................ 28 5.1.3 Setup Application Specifics ............................................................................................... 29

5.2 Advanced User Monitoring ................................................................................................................. 30


Table of Contents

CUSTOMER


5.2.1 Preparing Use-Case ........................................................................................................... 30 5.2.2 Real User Monitoring Specific Setup Steps ...................................................................... 31 5.2.3 Background Jobs ................................................................................................................. 32

5.3 Advanced Event and Alert Management ........................................................................................... 32 5.3.1 Preparing Use-Case ............................................................................................................ 32 5.3.2 Apply Notes for Alert Management ................................................................................... 32

5.4 Configuration and Security Analytics ................................................................................................ 33 5.4.1 Preparing Use-Case ............................................................................................................ 33 5.4.2 Additional Configuration ..................................................................................................... 33

6 Appendix ...................................................................................................................................... 34 6.1 oData and SICF services activated by STC01 task lists ................................................................... 34

6.1.1 SAP_GW_FIORI_ERP_ONE_CLNT_SETUP with Variant SAP&FRUN_INIT .................... 34 6.1.2 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_ASM ...................................... 36 6.1.3 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_AUM ...................................... 37 6.1.4 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_CSA ....................................... 37

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://service.sap.com/instguides.

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 Acronyms and terms

Acronyms 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://service.sap.com/instguides


Getting Started

CUSTOMER


Acronyms or short form Long form

RUM Real User Monitoring

TA Trace Analysis

SysMon System Monitoring

SysAna System Analysis

ITCal IT Calender

WMM Work Mode Management

SAM Service Availability Management

EWA 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) Effective and efficient management of many

systems, databases and hosts. Focus is on

functionality such as

System Monitoring (SysMon)

System Analysis (SysAna)

IT Calendar (ITCal)

Work Mode Management (WMM)

Service Availability Management (SAM) and

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

You find all information about the use cases with regard to Focused Run 1.0 in the SAP Help Portal and in SAP

Community Network (SCN):

SAP Help Portal

SAP Help Portal bundles access to SAP product documentation and also 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 but it’s likely that you will be

interested in visiting and following a particular set of spaces that reflect your particular range of interests and

where members who share your interests are likely 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 require to address the following items, like 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, you shall take several aspects into account to take the right 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

15]

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 on the SAP

Support Portal:

Content Location on SAP Service Marketplace

Latest versions of installation and upgrade

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

Security and User Guide https://service.sap.com/securityguide

Performance https://service.sap.com/performance

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


https://service.sap.com/platforms

https://support.sap.com/pam

https://service.sap.com/securityguide

https://service.sap.com/performance

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


Plan Landscape

CUSTOMER



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

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

Installation

Guide for

SAP

Netweaver

7.5

https://service.sap.com/instguidesnw75

Master Guide

for SAP

NetWeaver

7.5

https://service.sap.com/~sapidb/012002523100015815162015E

End- to-End

Implementati

on 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/0dd91ad6013d1be10000000a42189

d/frameset.htm

3.4 Important SAP Notes

You must 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.

https://support.sap.com/notes


https://service.sap.com/instguidesnw75

https://service.sap.com/~sapidb/012002523100015815162015E

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



Plan Landscape

SAP Note Number Title Description

2354930 Release strategy for the ABAP

add-on FRUN

Release and Installation

Information for FRUN 100

2369217 Release restrictions for

Focused Run 1.0

Overview on limitations


Implementing Focused Run 1.0

CUSTOMER


4 Implementing Focused Run 1.0

4.1 Check installed SAP HANA revision

The SAP HANA System is considered as a prerequisite.

Make sure that your implement HANA SPS12 Revision 122.00 or higher (>=1.00.122.00), using

HANA Cockpit

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

ent.htm) or

HANA Studio

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

t.htm) to check the currently installed revision.

If you are using HANA revision lower than 122.03 please implement note 2370160 to avoid data inconsistencies.

4.2 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]

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

max_concurrency_hint = <number shall be lower than the number of cores per socket>

[persistence]

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

Note: Adjusting this values, requires a restart.

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

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/2370160

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




You therefore need to plan the desired installation target using the maintenance planner at

https://apps.support.sap.com/sap/support/mp, in order 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 the following must be selected:

Select NetWeaver 7.5 with Support Package 3

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.4 Post Installation of SAP NetWeaver ABAP Server for Focused Run Usage

4.4.1 Create productive client

Please create a production client for usage of Focused Run applications as copy of SAP delivered client 000.

Please do not use client 000 or client 001 delivered by SAP directly for Focused Run applications (NetWeaver

Basis Administration can be done directly in client 000).

4.4.2 Focused Run administration user

Please perform initial configuration of Focused Run with an administration user having SAP_ALL privileges (e.g.

copy of user DDIC).

4.4.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:

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

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

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

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




CUSTOMER


The parameter recommendation provided is a starting point for a midsize Focused Run installation. Based on the

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

Remind to restart the 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

icm/server_port_1 =

PROT=HTTP, PORT=80,

TIMEOUT=300,

PROCTIMEOUT=300

icm/server_port_2 =

PROT=SMTP,PORT=25000,

TIMEOUT=180

Set up one HTTP, HTTPS and SMTP port

icm/max_conn 8.000 SAP note 2007212

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

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






18

CUSTOMER




Parameter Recommendation Remark

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

zcsa/second_language E

http/security_context_cache_size 8.000

Number of work processes

Please configure at least 50 DIA and 25 BTC work processes for each ABAP server. For Background information

regarding work process configuration, number of work processes and dependencies please refer to SAP notes

2190597, 39412 and 9942.

Note: please restart your ABAP system after profile parameter changes.

4.4.4 Update of SAPUI5 Runtime Environment

Install SAPUI5 1.38.5 (or higher) as described in SAP Notes 2333321 - "SAPUI5 upgrade to version 1.38.6".

Note: Currently installed SAPUI5 version can be found by opening the following URL on your Focused Run system:

Error! Hyperlink reference not valid.

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

2296256 - Syntax Error when Entity Type and Function Import has same name

2318977 - Fiori Setup: Improve ICF Service Activation

2338920 - SPI: Free text messages without MSGID and MSGNR are not displayed

[relevant for RUM only] 2207387 - Unified rendering for SAP_UI 750

2361342 - FRUN: ST-PI Extensions For Service Operations

2361675 - Page is cutoff in the middle





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

https://launchpad.support.sap.com/#/notes/2296256/E








CUSTOMER


4.4.6 Preparing NetWeaver Basic Operation

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

NetWeaver with Focused Run Using Up-to-Date installation process), make sur 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.

For Focused Run specifications the following changes to the default configuration of the task list are required

(enable/disable some steps):

Deselect all tasks

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

4.4.7 Configuring Usage of Load Balancer

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


To ensure that all URLs are using the load balancer (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

o APPLICATION: *

o HOST: load balancer - FQDN,

o PORT: load balancer HTTPS port

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

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

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

20

CUSTOMER




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

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

Afterwards please 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].

4.5 Configuration of Focused Run Application Foundation

4.5.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 also the common used data streaming services for all Application Foundation components.

Procedure

1. Log on to your SAP ABAP system.

2. Call the following transaction:

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

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.

The activities performed to activate the Fiori runtime are described at

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.

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



CUSTOMER


4.5.2 Creating Technical Users for Application Foundation

Before you continue with the next steps, you shall create the technical users (FRN_BTC*) to run background

processes in Focused Run, like mentioned in the security guide section "Technical User for Batch Processing in

Focused Run ABAP".

Additionally, to enable the Focused Run integrated user management, also create the template users (TPL_FRN*)

as described in the security guide section "Technical User to Authenticate Data and Send Requests to the Central

Focused Run ABAP Stack". The system uses these template users to automatically create the technical users

relevant for receiving data of different customer namespaces. These template users must be created of type

"Reference" with the roles mentioned in the security guide.

4.5.3 Preparing Simple Diagnostics Agent Distribution

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

binaries of the current SDA version and also the JRE must be provided to 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://support.sap.com/swdc)

o Software Downloads

o By Category

o SAP Technology Components

o Focused Run

o Focused Run 1.0

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

Perform the following steps for all platforms in your system landscape.

1. Upload the SDA binary (Select SDA and the Platform type)

2. After pressing execute (F8), a file selection dialog appears, where the SDA SAR archive must be selected

3. Repeat the procedure for the Java Runtime Environment (Select JRA and the Platform type)

4. The procedure must be repeated for every platform in the managed system landscape to be supported and

the platform of the Focused Run system

The following platforms are supported by Focused Run:

Linux on Power (linuxppc64)

Linux x86_64 (linuxx86_64)

Windows Server (ntamd64)

IBM AIX (rs6000_64)

Oracle Solaris SPARC (sun_64)

Oracle Solaris x86 (sunx86_64)


22

CUSTOMER




Note: After a new release of the SDA, the procedure above must be repeated for all supported platforms before an

agent update can be triggered via the Agent Administration application (accessible via Focused Run Launchpad).

4.5.4 Simple System Integration

4.5.4.1 Enabling User Management for Back Destination Users

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

1. Integration with a customer user management solution, which manages the full user handling process and

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

such cases must be done in the user management solution and in Focused Run BAdI enhancement spots are

available for integration purposes.

2. Handling of the back communication users locally in Focused Run is available in case there is no suitable user

management solution available and the management of the users should be done by the Simple System

Integration. To enable this solution the following must be performed:

o A User (FRN_IADM_SSI) with privileges to create/change and delete users must be created in the

Focused Run System. (the detailed explanation of this user and which SAP standard roles are available

for this user is provided in the security guide)

o Create an RFC Destination SSI_USER_ADMIN_CONNECTION to FRUN system using the user created in

the step before (background information on 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 Target Host und Ports: <empty>

o Language: EN

o Client: <productive FRUN client>

o User: FRN_IADM_SSI

o Password: <password for user FRN_IADM_SSI >

o Authorization for Destination: SSI_CONF

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

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



CUSTOMER


o Run Report P_SSI_PREPARATION in SA38 with the following parameters

4.5.5 Landscape Management Database

Prerequisite

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

CR Content from SAP Support Portal. The update of this is described in SAP Note "669669 - Update of SAP

System Component Repository in SLD". The CIM Model and SAP CR Content must be imported into a separate

namespace in the SLD, e.g. “crref”. You can use any existing SLD, elsewise there is no need a dedicated 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.

Activities

Start Setup using transaction LMDB_SETUP.

In Step 1 maintain the SLD Parameters:

24

CUSTOMER




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

Note: a new job SAP_LMDB_LDB_<number> is scheduled by this activity. Please check the job log of the

scheduled job. If the job is running fine without errors since longer than 5 minutes, the configuration can

continue.

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

Edit network 'LOCALNETWORK', and maintain the following values

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

Customer ID: 3 character CID for the FRUN system itself

Data Center ID: 3 character ID for the data center the FRUN system itself is running

Proxy to Admin: Host: hostname of http load balancer for the Focused Run system



CUSTOMER


Proxy to Admin: Port: port of http load balancer for the Focused Run system

Secure (Proxy to Admin): false

After the configuration is complete, the network 'LOCALNETWORK' can be activated to be used by running the

following reports in transaction SA38 with the parameters shown below:

Run Report SSI_ADMIN_NETWORK_INITIALIZE

Run Report SSI_ADMIN_NETWORK_ACTIVATE

The sapadm password provided must the password used for OS user sapadm on all Focused Run servers.

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

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

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

26

CUSTOMER




4.5.5.3 Registering Focused Run System in LMDB

1. Configure the Outside Discovery for all hosts of Focused Run system (Webservice Call or saphostexec cmd

line), details are described in the managed system configuration guidelines.

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

4.5.6 Setup Application Foundation Background Processing

Schedule the following background jobs

Jobname ABAP Programs(s) Step User Start Time Frequency

SAP_FRN_WMM_TRIGGER WMM_TRIGGER FRN_BTC_WMM immediately every

minute



CUSTOMER


Jobname ABAP Programs(s) Step User Start Time Frequency

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

4.5.7 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"

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

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

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

o MAXWSPERC (Maximum percentage of available DIA WPs used by ECE)

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

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

4.5.8 Content Update

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

2369335.

4.5.9 Self-Monitoring

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

Configuration: Press Button “Configure Central Components”


28

CUSTOMER



Business Scenarios of Focused Run

5 Business Scenarios of Focused Run

5.1 Advanced System Management

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




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.1.2 Background Jobs

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_REPOR

T

FRUN_DOWNLOADS_REPOR

T

FRN_BTC_EW

A

Immediatel

y

hourly



CUSTOMER


5.1.3 Setup Application Specifics

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

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

5.1.3.2 System Monitoring

Activate the ICF service for System Monitoring application

5. Logon to your SAP ABAP system


Transaction Code SICF

7. In the filter screen search for Service Name = 'sr_sysmon'


30

CUSTOMER




8. Press Execute (F8)

9. Search for /sap/bc/bsp/sap/sr_sysmon

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

confirmation dialog.

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







CUSTOMER


5.2.2 Real User Monitoring Specific Setup Steps

Real User Monitoring table partitioning & batch job scheduling

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

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

Activate the ICF service for Real User Monitoring application

1. Logon to your SAP ABAP system


Transaction Code SICF

3. In the filter screen search for Service Name = 'e2erum'

4. Press Execute (F8)

5. Search for /sap/bc/ui5_ui5/RUM/E2ERUM

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

confirmation dialog.

32

CUSTOMER




5.2.3 Background Jobs

Schedule the following background jobs using transaction SM36

JOBNAME REPORT Step User Start Time Recurrence

interval

SAP_FRN_TRACE_HK E2E_TRACE_DELETE FRN_BTC_TA 1:00 am daily

5.3 Advanced Event and Alert Management



SAP&FRUN_AEM in transaction STC01.

Procedure





List field.

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





5.3.2 Apply Notes for Alert Management

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


2296256 - Syntax Error when Entity Type and Function Import has same name

2379819 - Alert Management show logs popup is empty when show logs button is clicked

2379856 - Alert Management launch from System Monitoring shows different Worst time of alert compared

to last updated time

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






CUSTOMER


2380022 - Rating chart is not displayed in Alert Detail page

5.4 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





5.4.2 Additional Configuration

Execute Report COF_SETUP using transaction SA38


34

CUSTOMER



Appendix

6 Appendix

6.1 oData and SICF services activated by STC01 task lists

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


Appendix

CUSTOMER


/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

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

/sap/bc/webdynpro/sap/wdc_transport_templates

36

CUSTOMER



Appendix

/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/webdynpro/sap/dswp_na_grp_powl

/sap/bc/webdynpro/sap/dswp_na_maintain_recipientlist

/sap/bc/webdynpro/sap/dswp_na_generic_notif

/sap/bc/webdynpro/sap/dswp_na_rlist_settings

/sap/bc/webdynpro/sap/dswp_na_configure_servers

6.1.2 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_ASM



System Monitoring AI_SYSMON_SRV

AI_SYSMON_OVERVIEW_SRV

System Analysis WEA_SRV

Service Availability Management SAM_SRV


Appendix

CUSTOMER



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

/sap/bc/ui5_ui5/sap/metricmonitor

/sap/bc/webdynpro/sap/troubleshoot

System Analysis /sap/bc/ui5_ui5/sap/wea

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

6.1.3 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_AUM



Real User Monitoring /RUM/UI5_SRV

Trace Analysis E2E_TRACE_UI_SRV


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

/sap/bc/ui5_ui5/RUM/E2ERUM

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

/sap/bc/ui5_ui5/sap/tracejslib

/sap/srsm/E2E_trace_upl

6.1.4 SAP_FRUN_SETUP_USECASE with variant SAP&FRUN_CSA



Configuration Validation CONFIG_VALIDATION_SRV

COF_ODATA_SRV

38

CUSTOMER



Appendix


System Monitoring /sap/bc/ui5_ui5/sap/srsm_config_val

/sap/bc/ui5_ui5/sap/cof_lv

/sap/bc/webdynpro/sap/WD_CCDB_SCI

/sap/bc/webdynpro/sap/WD_COVA_TAR_MAINT

/sap/bc/ui5_ui5/sap/cof_admin_comp

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

Date post:	09-Dec-2016
Category:	Documents
Upload:	trananh
View:	471 times
Download:	10 times

Focused Run for SAP Solution Manager

Documents