egi basic configuration 71 day4

Expert Guided Implementation

Basic Configuration of SAP Solution Manager

Day 4

Name of Speaker

2012 SAP AG. All rights reserved. 2

1. Day one

Expert Guided Implementation Methodology Motivation Check of prerequisites System Preparation (1)

2. Day two

System Preparation (2)

3. Day three

Basic Configuration

4. Day four

Managed System Configuration (1)

5. Day five

Managed System Configuration (2) Best Practices

Agenda


Managed System Configuration Steps in detail

Managed System Configuration

Select Product

Check Prerequisites

Connect Managed System (ABAP only)

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Create Logical Component

Check Configuration


Managed System Configuration Send system information from managed systems

Before you can start with the Managed System Configuration you need to transfer the

information about the managed systems into the SLD. From there it will be copied to LMDB

automatically.

At first please check if your system data is already available in the runtime SLD (e.g. in a PI

system). To build up a bridge from a local SLD (e.g. in a Portal system) please refer to

https://www.sdn.sap.com/irj/sdn/nw-sld.

In this demo we will show how to link the TAE ABAP system and the J2E JAVA system to the

Solution Manager SLD that we use as runtime SLD.


To send system information from an ABAP system to the SLD you have to enter connection

data in transaction RZ70 on the ABAP managed system.

Managed System Configuration Send system information from an ABAP managed system

1. Enter the host and service of the SLD server

2. Activate configuration

3. Start data collection and job scheduling

2 3

1


Managed System Configuration Send system information from a Java managed system

1. Start Visual Administrator by executing the file go or go.bat at

/usr/sap///j2ee/admin

2. In the Visual Administrator, choose Cluster Server Services SLD Data Supplier Runtime HTTP Settings

Please be careful

while changing

parameters in Visual

Administrator of

productive systems.

Use local SLD only (if

exists) as target for

data transfer.

Otherwise your

applications might not

work afterwards.


3. Enter the required data for the HTTP connection from the SLD Data Supplier service to

the SLD server:

Managed System Configuration Send system information from a Java managed system

In the Host field, enter the name of the host where the corresponding SLD runs.

In the Port field, specify the HTTP standard access port of the SLD

In the User field, specify the J2EE user (e.g. SLDDSUSER)

In the Password field, enter the user password.

In case your Java system has an own SLD (Enterprise Portal in our case), register

the system at this SLD and establish a bridge to the runtime SLD (see next slide for

details).

Save your entries. If your entries have been saved successfully, the connection data is

saved in encrypted form in the secure store in the database.

Test your settings by sending data to the SLD, choose Trigger data transfer to System

Landscape Directory (SLD).


Managed System Configuration Send system information from an SLD

To build up a bridge from a local SLD of the Java

system to the runtime SLD, the following steps

need to be performed:

1. Open the administration interface on the local

SLD, using the following URL:

.

2. Choose Administration Data Supplier.


Managed System Configuration Send system information from an SLD

3. Choose Add SLD.

4. Enter the URL of the runtime SLD using

the following URL:

5. Enter an SLD administrator and a

password on the runtime SLD

(e.g. J2EE_ADMIN).

6. Choose Save.


Managed System Configuration ABAP only system

SAP Solution

Manager

7.1 SP5

TAS

tastdc00

wdflbmt2284

SAP ERP 6.0 EHP5

TAE

taetdc00

wdflbmt2586

SAP NW 7.0 EHP2

Enterprise

Portal

J2E

portal-tae

wdflbmt2621

Cloud Environment


To start the Managed System Configuration, select the managed system to be configured in

the tab Technical Systems:

Managed System Configuration Select technical system for configuration

Select Configure System pushbutton.

The configuration of Dual Stack systems (e.g. SAP Solution Manager) must

be done using the tab Technical Scenarios.


This step specifies the software that is installed on the managed system. Change managed

system configuration wizard to Edit mode:

Managed System Configuration Select Product

Select Edit Technical System Software to proceed:


Managed System Configuration Select Product

Please make sure that you assign the product instances correctly

to your system.

For detailed information please refer to the System Landscape

Setup Guide (SAP note 1472465)

On the next slides you will see the product

assignment for an ERP system as example.

The settings may differ depending on the type

of the managed system to be connected.


A new screen will

open. Select the Add

pushbutton

Managed System Configuration Edit technical system software

In the next screen select the

relevant product instance(s)

(press Ctrl for multiple

selections) for your managed

system. Select Add

pushbutton once more.



Select Assign to Product

System pushbutton to assign

selected product instances to

the product systems. Create a

new product system if

necessary.


Once the relevant product instances are entered in the technical system editor, select Save

and Close. Pay attention to the checkbox Diagnostics Relevant:

In the overview of the Technical System Software press the Refresh pushbutton. You

should then see the managed system with the relevant products and status green.



This step will check whether the software prerequisites are fulfilled.

Select Execute All pushbutton to proceed. You can select the Display link in the

Documentation column for further information.

The status should be set to green when the check is completed.

Managed System Configuration Check prerequisites


This step will generate the RFC connections to the ABAP managed system. For each

managed system you have to create at least one READ RFC connection to the productive

client, for example to client 800.

First you can create a Managed System Setup administrator user automatically with the wizard. Regarding the authorizations please refer to SAP Note 1560717.

Select the line with the client you want to connect:

Managed System Configuration Connect managed system (ABAP only)


Select the RFC destinations to be created:

Mandatory: RFC Destination for Read Access: To enable basic SAP Solution Manager functions, read

access is required

Recommended: RFC Destination for Change Manager (TMW): Enables change requests

Recommended: RFC Destination (Back)

Managed System Configuration Create RFC destinations between SAP Solution Manager and managed systems

Create RFC on Solution Manager to

easily jump to the managed system:

Trusted Destination: without

additional authentication.

Prerequisites: user exists in both

systems with authorization object

S_RFCACL. (see next slides)

Login Destination: access with logon

screen



SM_CLNT_READ, in the SAP Solution Manager system

This RFC will be used to Read system data remote from transaction SMSY and to read the Data Collection method for System Monitoring.

SM_ CLNT_TMW, in the SAP Solution Manager system

This RFC will be used for the Change Request Management (ChaRM) functionality. Not needed unless the use of ChaRM is planned.

SM_CLNT_TRUSTED, in the SAP Solution Manager system

This RFC will be used by dialog users in the SAP Solution Manager for connecting to managed systems when using Operation tools, Implementation Tools, or Change Manager functionality. Note that _LOGIN type RFC can be generated instead.

SM_CLNT_BACK, in the Managed system

This RFC will be used to send Service Data from the managed system to the SAP Solution Manager system and to get service definitions from Solution Manager.

SM_CLNT_TRUSTED, in the Managed system

This RFC can be assigned as the RFC destination in table BCOS_CUST for sending service desk messages to the Solution Manager Service Desk. Sender requires an account in the Solution Manager to successfully send the message.



SM_TAECLNT800_READ

SM_TAECLNT800_TRUSTED*

SM_TASCLNT200_BACK

1

3

4

SM_TASCLNT200_TRUSTED* 5

SM_TAECLNT800_TMW 2

TAS

client 200

SMB_TAE Comm. type user

RFCs Solution Manager Managed System

SM_TAS Comm. type user

TAE

client 800

SMTMTAS Comm. type user

* _LOGIN RFC can be generated instead


Managed System Configuration Create RFC destinations between SAP Solution Manager and managed systems

The *_TRUSTED RFC connection requires the object S_RFCACL in the user master record

for the user in both the Solution Manager system and the managed system.

Maintain and generate this role with transaction PFCG and add it to the user in both systems.

The user name in both systems must be the same.


To be able to create RFC destinations on the managed system, a user with necessary

authorizations must be provided.

As an alternative a new user, for example SM_ADMIN_, can be created directly from

the guided procedure. Press the button Create or Update Administrator in the Managed System Administrator section:

Enter the Super User logon data and press Connect:



Provide the user name (or use the default one), specify the password and execute the

activity by pressing the Execute button:


Following roles will be copied into the customer namespace and added to the user:

SAP_RCA_CONF_ADMIN

SAP_SM_USER_ADMIN


Now you can perform the generation of the RFC connections to the ABAP managed

system. For each managed system you have to create at least one READ RFC connection

to the productive client, for example to client 800.

Enter the user and password for the SAP Solution Manager and for the managed system.

Fields for Solution Manager administrator are only enabled if the Back RFC is selected (scroll down to select).

Press the Execute pushbutton at the bottom of the screen to create the selected RFCs:



In this step you assign diagnostics agents to the selected managed system. You assign a

diagnostics agent to each server (virtual host) on which the managed system is running.

Managed System Configuration Assign Diagnostics Agents

On the Assign Diagnostics Agent tab, select a server

and choose the Assign pushbutton. A new dialog box

will appears where the available diagnostics agents are

displayed.

Select the applicable diagnostics agent and choose

Assign.


Since SPS05 it is possible to perform the Host Agent check directly from the guided

procedure by clicking on the corresponding button:

Managed System Configuration Assign Diagnostics Agents

A message in the log pane will indicate whether the check was successful:


In this step you enter the system and DB connection parameters for the managed system

(example for ABAP systems):

Managed System Configuration Enter system parameters

Save the settings.

Please refer to the following slides for

information about DBA Cockpit.


Managed System Configuration DBA Cockpit

The main purpose of the DBA cockpit is Database Monitoring and Analysis of

all connected managed systems centrally from the SAP Solution Manager


Managed System Configuration DBA Cockpit

Because of the reason that the setup,

technical requirements & limitation are

database specific, please check the

DBA cockpit Master Note 1265134 for

further details.


In this step you verify or add landscape parameters.

Managed System Configuration Enter Landscape Parameters

In the Landscape Objects hierarchy, check

the status of each parameter. For example:

- The status is set to No parameters means

no input is required.

- The status is set to Default used means you

need to verify the parameters.

On ABAP systems

check especially if the

ICM ports are entered

correctly.


In the Users screen area select a user, enter a password and click on Execute.

Managed System Configuration Create users

The user SAPSUPPORT enables SAP Active Global Support to provide support for the

managed system. Enter the password for this user manually.

The user SMDAGENT_ connects Wily Host agent to SAP Solution Manager.

This is an ABAP user that is used by the Wily Host agent.

Please refer to the

Security Guide for

details.


In this step SAP Solution Manager performs automatic configuration activities. To start

automatic configuration, select the Execute All pushbutton.

Check the results. In case of errors please select the step in error and read the error

messages in the log pane.

Managed System Configuration Configure automatically


In this step you perform manual configuration activities.

1. Activity Maintain SAP Router Data:

In the SAP Service Marketplace, maintain the SAP Router data for your managed system

so that a service connection can be opened if remote maintenance is necessary.

2. Activity Adjust HTTP Log Parameter:

To enable the analysis of logs written by the Internet Communication Manager (ICM) with

End-to-End Root Cause Analysis we need to set this parameter in each system based on

ABAP. On the managed systems, start transaction RZ10 and add the parameter to the

default profile of your system as described in the documentation (click on the

Documentation link). Save and activate the profile. Restart the ICM service (transaction

SMICM) in order to activate this profile parameter modification.

Managed System Configuration Configure Manually (ABAP system)


3. Activity Enable Exception Management:

Since SPS05 Exception Management can be enabled. To configure the functionality follow

the navigation link and switch on Edit mode in the new window:

Managed System Configuration Configure Manually (ABAP system)

Enable the areas you would like to monitor. Save the entries.


This step assigns the selected managed system to one or more logical components.

Logical components are the basis for using a system in solutions and projects.

To enable EarlyWatch Alert, at least one logical component needs to be defined and

assigned to a solution.

Select the pushbutton Create New Logical Component. In the Name column enter a name

for the new logical component. In the Systems column use the input help to assign the

system in the system roles column.

To save your entries select Save.

Managed System Configuration Create logical component (ABAP system)


Managed System Configuration Key Info: Logical Component

ABAP

Client 002

Solution 2

Customer system landscapes

Solution 1

Main

Instance

Client 200

Client

J2EE

TREX

PRD

system

DEV

system

QA

system

system

PRD

system

DEV

system

QA

system

system

Logical component A

Logical component B

Project 2 Project 1 Logical component A

Logical component B

DEV QA

Product

System

Product System /

Product

Version

PRD

DEV QA PRD

Logical component A

Logical component B

DEV QA PRD

DEV QA PRD

Logical

System



RS1-100 RD1-100 RQ1-100 RP1-100

Eval Dev QA PRD Training Logical Components

Z_ECC_100

CS1-100 CD1-100 CQ1-100 CP1-100 Z_CRM_100

BS1-100 BD1-100 BQ1-100 BP1-100 Z_BW_100

RD1 CD1 BD1

Solution View

Development Systems Landscape

Leading Role of Solution: Development

Using the leading role for a Development Systems Solution Landscape:



RS1-100 RD1-100 RQ1-100 RP1-100

Eval Dev QA PRD Training Logical Components

Z_ECC_100

CS1-100 CD1-100 CQ1-100 CP1-100 Z_CRM_100

BS1-100 BD1-100 BQ1-100 BP1-100 Z_BW_100

RP1 CP1 BP1

Solution View

Production Systems Landscape

Leading Role of Solution: Production

Using the leading role for a Production Systems Solution Landscape:


Managed System Configuration Key Info: Solution Landscape

You can manage solutions in the Work Center Solution Manager Administration (call transaction SOLMAN_WORKCENTER or SM_WORKCENTER)

1. If needed, a new solution can be

created here. Press New to create a new Solution.

2. Click on Solution Data Settings to define which data should be sent to

SAP for the selected solution.

3. Click on the solution link or call

Transaction SMSY to open the

solution maintenance view (see

next slide)


Managed System Configuration Key Info: Solution Landscape

4. The leading role for a solution landscape determines which system in a logical

component is assigned to the solution landscape.

5. You can add further logical components to the solution.

To be able to make changes in this screen please ensure the following authorizations are

assigned to the configuration user (copy the roles to the customer namespace):

SAP_SM_SOLUTION_ALL, SAP_SOLMAN_DIRECTORY_ADMIN.


In this step an automated check will be performed on the system configuration. Also the

status overview of the managed system configuration will be updated.

Choose Execute All.

Managed System Configuration Check Configuration

If you get error messages saying

required roles have not been granted to user, please implement SAP Note 1659367.


You have connected the managed system to the SAP Solution Manager.

Managed System Configuration Complete


Execution

Managed System Configuration

Select Product

Check Prerequisites

Connect Managed System (ABAP only)

Assign Diagnostics Agent

Enter System & Landscape Parameters

Create Users

Automatic & Manual Configuration

Create Logical Component

Check Configuration

To be able to follow the session in the next days please make

sure that you completed all tasks for today.


Roadmap steps Basic Configuration Outlook

Next steps Day 5

Managed Systems Configuration (2)

Java and Dual Stack systems

Best practices

Best practices for scenario usage


Expert Guided Implementation How to get help

How to get help

Customer SAP Expert

During the execution part you have direct access to the Expert via

telephone number to solve questions quickly. Please ensure that the

R/3 support and http connections are open and that we can logon to

your system.

+tel number

e-mail trainer

Thank You!

Please dont forget to send us the daily feedback form.

egi basic configuration 71 day4

Documents