welcome to the solution manager stream · pdf filecreate a new client and perform a local...

106
Welcome to the Solution Manager Stream

Upload: vannhi

Post on 31-Jan-2018

221 views

Category:

Documents


0 download

TRANSCRIPT

Welcome to the Solution Manager Stream

Demystifying Solution Manager 71 ndash

configuration focus on diagnostics

Roland HoellerSAP AGS Product Support

Movember 26 2013 Public

copy 2013 SAP AG All rights reserved 3 Public

Agenda

Prerequisites

System Preparation

(Highlights)

Basic Configuration

(Highlights)

Managed System

Configuration

Housekeeping tips

Prerequisites

copy 2013 SAP AG All rights reserved 5 Public

Check Prerequisites Roadmap

Before starting with the configuration of SAP

Solution Manager please prepare the following

Solution Manager S-users in SAP Service Market Place

Ensure correct support package level of SAP Solution

Manager

Check SLD CR content and model version

Check RFC destination SAPOSS

Verify Solution Manager profile parameters

Download software for Diagnostics Agent and SAP

Hostagent

Download CA Introscope Enterprise Manager

Optional Perform a client copy

copy 2013 SAP AG All rights reserved 6 Public

Check Prerequisites Optional Client Copy

The SAP delivered client 001 can be used as productive client for SAP Solution Manager

It is also possible to use another productive client

Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client and as

the source client for users

Afterwards convert the Java UME to the new productive client

Restart the Java Stack

Please ensure that you entered 001 as

ldquoSource Client User Mastersrdquo for your client

copy

copy 2013 SAP AG All rights reserved 7 Public

Hardware pre-requisites quick sizerSizing Tool kit

SAP Quick Sizer (for Small to Large Solution Manager installation)SAP Solution Manager

sizing Toolkit (Large Solution Manager installation) provides information on infrastructure

requirements including SAPs Memory Databases and Disk Spaces needed to implement

selected ALM scenarios for a set of Managed Systems

copy 2013 SAP AG All rights reserved 8 Public

SAP Solution Manager Configuration UI components

Step Help Section

Provides detailed information to each

step such as what needs to be done

and what will happen in the

background

Activities

Lists all single activities during each

step along with the documentation

how to perform for the IMG activity

Log

Shows detailed logs per activity

Navigation

Guided procedure with all steps for the

basic configuration

copy 2013 SAP AG All rights reserved 9 Public

SAP Solution Manager Configuration Configuration Roadmap

System Preparation

bull Prepares the Solution Manager system for the basic configuration

bull Needs to be performed fully after a new installation or upgrade

bull Partially after patches and upgrades to update dialog and system users and assign the appropriate default roles

bull During this step the Central Correction Note (CCN) that contains the latest corrections is implemented

Basic Configuration

bull Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)

bull Needs to be performed after new installations and after support packages to perform delta configuration

bull Overview screen tells you which configuration needs update

Managed Systems

Configuration

bull Connection and configuration of managed systems

bull Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on SAP Solution Manager

bull Creation of Logical Components for managed systems

bull Setup of the Exception Management Dashboard for the managed systems

System Preparation

copy 2013 SAP AG All rights reserved 11 Public

System Preparation Roadmap

The scenario System Preparation consists of

the following steps

Create Users

Check Installation

Implement SAP Note

Configure Connectivity

Prepare Landscape Description

Complete

copy 2013 SAP AG All rights reserved 12 Public

System Preparation Create Users

In the first step dialog and system users are created which are needed later during the System

Preparation Select a user to create or

update

Create a new user or

update the authorizations

of an existing user

If the user creation is

performed manually

check the respective

checkbox (4)

Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therfore make sure the user is

correct

copy 2013 SAP AG All rights reserved 13 Public

System Preparation Configure Web Dispatcher

If your SAP Solution Manager systems runs more than one instance a Web Dispatcher is

required

The web dispatcher manages the load balancing of the several web service calls between the diagnostics agents and the

Solution Manager ABAP stack and the Solution Manager ABAP and Java stack

Enter the URL and the port for the

Web Dispatcher

Save the entries

For more information about installing a SAP Web Dispatcher and configuration

options see SAP Help Portal at ldquoURL Generation in an AS-ABAP - Web Dispatcher

Configurationrdquo

copy 2013 SAP AG All rights reserved 14 Public

In this step you explicitly allow SAP Solution Manager to create web services using the

following authentication types

Basic Authentication

X509 Certificate Authentication

Ticket Authentication

System Preparation Set Authentication Types for Web Services

Read the documentation provided

for the activity

Start transaction SOAMANAGER

or click on the provided navigation

link

Activate all authentication

methods and save your changes

The explicit setup is necessary

for security compliance reasons

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

Demystifying Solution Manager 71 ndash

configuration focus on diagnostics

Roland HoellerSAP AGS Product Support

Movember 26 2013 Public

copy 2013 SAP AG All rights reserved 3 Public

Agenda

Prerequisites

System Preparation

(Highlights)

Basic Configuration

(Highlights)

Managed System

Configuration

Housekeeping tips

Prerequisites

copy 2013 SAP AG All rights reserved 5 Public

Check Prerequisites Roadmap

Before starting with the configuration of SAP

Solution Manager please prepare the following

Solution Manager S-users in SAP Service Market Place

Ensure correct support package level of SAP Solution

Manager

Check SLD CR content and model version

Check RFC destination SAPOSS

Verify Solution Manager profile parameters

Download software for Diagnostics Agent and SAP

Hostagent

Download CA Introscope Enterprise Manager

Optional Perform a client copy

copy 2013 SAP AG All rights reserved 6 Public

Check Prerequisites Optional Client Copy

The SAP delivered client 001 can be used as productive client for SAP Solution Manager

It is also possible to use another productive client

Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client and as

the source client for users

Afterwards convert the Java UME to the new productive client

Restart the Java Stack

Please ensure that you entered 001 as

ldquoSource Client User Mastersrdquo for your client

copy

copy 2013 SAP AG All rights reserved 7 Public

Hardware pre-requisites quick sizerSizing Tool kit

SAP Quick Sizer (for Small to Large Solution Manager installation)SAP Solution Manager

sizing Toolkit (Large Solution Manager installation) provides information on infrastructure

requirements including SAPs Memory Databases and Disk Spaces needed to implement

selected ALM scenarios for a set of Managed Systems

copy 2013 SAP AG All rights reserved 8 Public

SAP Solution Manager Configuration UI components

Step Help Section

Provides detailed information to each

step such as what needs to be done

and what will happen in the

background

Activities

Lists all single activities during each

step along with the documentation

how to perform for the IMG activity

Log

Shows detailed logs per activity

Navigation

Guided procedure with all steps for the

basic configuration

copy 2013 SAP AG All rights reserved 9 Public

SAP Solution Manager Configuration Configuration Roadmap

System Preparation

bull Prepares the Solution Manager system for the basic configuration

bull Needs to be performed fully after a new installation or upgrade

bull Partially after patches and upgrades to update dialog and system users and assign the appropriate default roles

bull During this step the Central Correction Note (CCN) that contains the latest corrections is implemented

Basic Configuration

bull Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)

bull Needs to be performed after new installations and after support packages to perform delta configuration

bull Overview screen tells you which configuration needs update

Managed Systems

Configuration

bull Connection and configuration of managed systems

bull Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on SAP Solution Manager

bull Creation of Logical Components for managed systems

bull Setup of the Exception Management Dashboard for the managed systems

System Preparation

copy 2013 SAP AG All rights reserved 11 Public

System Preparation Roadmap

The scenario System Preparation consists of

the following steps

Create Users

Check Installation

Implement SAP Note

Configure Connectivity

Prepare Landscape Description

Complete

copy 2013 SAP AG All rights reserved 12 Public

System Preparation Create Users

In the first step dialog and system users are created which are needed later during the System

Preparation Select a user to create or

update

Create a new user or

update the authorizations

of an existing user

If the user creation is

performed manually

check the respective

checkbox (4)

Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therfore make sure the user is

correct

copy 2013 SAP AG All rights reserved 13 Public

System Preparation Configure Web Dispatcher

If your SAP Solution Manager systems runs more than one instance a Web Dispatcher is

required

The web dispatcher manages the load balancing of the several web service calls between the diagnostics agents and the

Solution Manager ABAP stack and the Solution Manager ABAP and Java stack

Enter the URL and the port for the

Web Dispatcher

Save the entries

For more information about installing a SAP Web Dispatcher and configuration

options see SAP Help Portal at ldquoURL Generation in an AS-ABAP - Web Dispatcher

Configurationrdquo

copy 2013 SAP AG All rights reserved 14 Public

In this step you explicitly allow SAP Solution Manager to create web services using the

following authentication types

Basic Authentication

X509 Certificate Authentication

Ticket Authentication

System Preparation Set Authentication Types for Web Services

Read the documentation provided

for the activity

Start transaction SOAMANAGER

or click on the provided navigation

link

Activate all authentication

methods and save your changes

The explicit setup is necessary

for security compliance reasons

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 3 Public

Agenda

Prerequisites

System Preparation

(Highlights)

Basic Configuration

(Highlights)

Managed System

Configuration

Housekeeping tips

Prerequisites

copy 2013 SAP AG All rights reserved 5 Public

Check Prerequisites Roadmap

Before starting with the configuration of SAP

Solution Manager please prepare the following

Solution Manager S-users in SAP Service Market Place

Ensure correct support package level of SAP Solution

Manager

Check SLD CR content and model version

Check RFC destination SAPOSS

Verify Solution Manager profile parameters

Download software for Diagnostics Agent and SAP

Hostagent

Download CA Introscope Enterprise Manager

Optional Perform a client copy

copy 2013 SAP AG All rights reserved 6 Public

Check Prerequisites Optional Client Copy

The SAP delivered client 001 can be used as productive client for SAP Solution Manager

It is also possible to use another productive client

Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client and as

the source client for users

Afterwards convert the Java UME to the new productive client

Restart the Java Stack

Please ensure that you entered 001 as

ldquoSource Client User Mastersrdquo for your client

copy

copy 2013 SAP AG All rights reserved 7 Public

Hardware pre-requisites quick sizerSizing Tool kit

SAP Quick Sizer (for Small to Large Solution Manager installation)SAP Solution Manager

sizing Toolkit (Large Solution Manager installation) provides information on infrastructure

requirements including SAPs Memory Databases and Disk Spaces needed to implement

selected ALM scenarios for a set of Managed Systems

copy 2013 SAP AG All rights reserved 8 Public

SAP Solution Manager Configuration UI components

Step Help Section

Provides detailed information to each

step such as what needs to be done

and what will happen in the

background

Activities

Lists all single activities during each

step along with the documentation

how to perform for the IMG activity

Log

Shows detailed logs per activity

Navigation

Guided procedure with all steps for the

basic configuration

copy 2013 SAP AG All rights reserved 9 Public

SAP Solution Manager Configuration Configuration Roadmap

System Preparation

bull Prepares the Solution Manager system for the basic configuration

bull Needs to be performed fully after a new installation or upgrade

bull Partially after patches and upgrades to update dialog and system users and assign the appropriate default roles

bull During this step the Central Correction Note (CCN) that contains the latest corrections is implemented

Basic Configuration

bull Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)

bull Needs to be performed after new installations and after support packages to perform delta configuration

bull Overview screen tells you which configuration needs update

Managed Systems

Configuration

bull Connection and configuration of managed systems

bull Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on SAP Solution Manager

bull Creation of Logical Components for managed systems

bull Setup of the Exception Management Dashboard for the managed systems

System Preparation

copy 2013 SAP AG All rights reserved 11 Public

System Preparation Roadmap

The scenario System Preparation consists of

the following steps

Create Users

Check Installation

Implement SAP Note

Configure Connectivity

Prepare Landscape Description

Complete

copy 2013 SAP AG All rights reserved 12 Public

System Preparation Create Users

In the first step dialog and system users are created which are needed later during the System

Preparation Select a user to create or

update

Create a new user or

update the authorizations

of an existing user

If the user creation is

performed manually

check the respective

checkbox (4)

Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therfore make sure the user is

correct

copy 2013 SAP AG All rights reserved 13 Public

System Preparation Configure Web Dispatcher

If your SAP Solution Manager systems runs more than one instance a Web Dispatcher is

required

The web dispatcher manages the load balancing of the several web service calls between the diagnostics agents and the

Solution Manager ABAP stack and the Solution Manager ABAP and Java stack

Enter the URL and the port for the

Web Dispatcher

Save the entries

For more information about installing a SAP Web Dispatcher and configuration

options see SAP Help Portal at ldquoURL Generation in an AS-ABAP - Web Dispatcher

Configurationrdquo

copy 2013 SAP AG All rights reserved 14 Public

In this step you explicitly allow SAP Solution Manager to create web services using the

following authentication types

Basic Authentication

X509 Certificate Authentication

Ticket Authentication

System Preparation Set Authentication Types for Web Services

Read the documentation provided

for the activity

Start transaction SOAMANAGER

or click on the provided navigation

link

Activate all authentication

methods and save your changes

The explicit setup is necessary

for security compliance reasons

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

Prerequisites

copy 2013 SAP AG All rights reserved 5 Public

Check Prerequisites Roadmap

Before starting with the configuration of SAP

Solution Manager please prepare the following

Solution Manager S-users in SAP Service Market Place

Ensure correct support package level of SAP Solution

Manager

Check SLD CR content and model version

Check RFC destination SAPOSS

Verify Solution Manager profile parameters

Download software for Diagnostics Agent and SAP

Hostagent

Download CA Introscope Enterprise Manager

Optional Perform a client copy

copy 2013 SAP AG All rights reserved 6 Public

Check Prerequisites Optional Client Copy

The SAP delivered client 001 can be used as productive client for SAP Solution Manager

It is also possible to use another productive client

Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client and as

the source client for users

Afterwards convert the Java UME to the new productive client

Restart the Java Stack

Please ensure that you entered 001 as

ldquoSource Client User Mastersrdquo for your client

copy

copy 2013 SAP AG All rights reserved 7 Public

Hardware pre-requisites quick sizerSizing Tool kit

SAP Quick Sizer (for Small to Large Solution Manager installation)SAP Solution Manager

sizing Toolkit (Large Solution Manager installation) provides information on infrastructure

requirements including SAPs Memory Databases and Disk Spaces needed to implement

selected ALM scenarios for a set of Managed Systems

copy 2013 SAP AG All rights reserved 8 Public

SAP Solution Manager Configuration UI components

Step Help Section

Provides detailed information to each

step such as what needs to be done

and what will happen in the

background

Activities

Lists all single activities during each

step along with the documentation

how to perform for the IMG activity

Log

Shows detailed logs per activity

Navigation

Guided procedure with all steps for the

basic configuration

copy 2013 SAP AG All rights reserved 9 Public

SAP Solution Manager Configuration Configuration Roadmap

System Preparation

bull Prepares the Solution Manager system for the basic configuration

bull Needs to be performed fully after a new installation or upgrade

bull Partially after patches and upgrades to update dialog and system users and assign the appropriate default roles

bull During this step the Central Correction Note (CCN) that contains the latest corrections is implemented

Basic Configuration

bull Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)

bull Needs to be performed after new installations and after support packages to perform delta configuration

bull Overview screen tells you which configuration needs update

Managed Systems

Configuration

bull Connection and configuration of managed systems

bull Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on SAP Solution Manager

bull Creation of Logical Components for managed systems

bull Setup of the Exception Management Dashboard for the managed systems

System Preparation

copy 2013 SAP AG All rights reserved 11 Public

System Preparation Roadmap

The scenario System Preparation consists of

the following steps

Create Users

Check Installation

Implement SAP Note

Configure Connectivity

Prepare Landscape Description

Complete

copy 2013 SAP AG All rights reserved 12 Public

System Preparation Create Users

In the first step dialog and system users are created which are needed later during the System

Preparation Select a user to create or

update

Create a new user or

update the authorizations

of an existing user

If the user creation is

performed manually

check the respective

checkbox (4)

Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therfore make sure the user is

correct

copy 2013 SAP AG All rights reserved 13 Public

System Preparation Configure Web Dispatcher

If your SAP Solution Manager systems runs more than one instance a Web Dispatcher is

required

The web dispatcher manages the load balancing of the several web service calls between the diagnostics agents and the

Solution Manager ABAP stack and the Solution Manager ABAP and Java stack

Enter the URL and the port for the

Web Dispatcher

Save the entries

For more information about installing a SAP Web Dispatcher and configuration

options see SAP Help Portal at ldquoURL Generation in an AS-ABAP - Web Dispatcher

Configurationrdquo

copy 2013 SAP AG All rights reserved 14 Public

In this step you explicitly allow SAP Solution Manager to create web services using the

following authentication types

Basic Authentication

X509 Certificate Authentication

Ticket Authentication

System Preparation Set Authentication Types for Web Services

Read the documentation provided

for the activity

Start transaction SOAMANAGER

or click on the provided navigation

link

Activate all authentication

methods and save your changes

The explicit setup is necessary

for security compliance reasons

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 5 Public

Check Prerequisites Roadmap

Before starting with the configuration of SAP

Solution Manager please prepare the following

Solution Manager S-users in SAP Service Market Place

Ensure correct support package level of SAP Solution

Manager

Check SLD CR content and model version

Check RFC destination SAPOSS

Verify Solution Manager profile parameters

Download software for Diagnostics Agent and SAP

Hostagent

Download CA Introscope Enterprise Manager

Optional Perform a client copy

copy 2013 SAP AG All rights reserved 6 Public

Check Prerequisites Optional Client Copy

The SAP delivered client 001 can be used as productive client for SAP Solution Manager

It is also possible to use another productive client

Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client and as

the source client for users

Afterwards convert the Java UME to the new productive client

Restart the Java Stack

Please ensure that you entered 001 as

ldquoSource Client User Mastersrdquo for your client

copy

copy 2013 SAP AG All rights reserved 7 Public

Hardware pre-requisites quick sizerSizing Tool kit

SAP Quick Sizer (for Small to Large Solution Manager installation)SAP Solution Manager

sizing Toolkit (Large Solution Manager installation) provides information on infrastructure

requirements including SAPs Memory Databases and Disk Spaces needed to implement

selected ALM scenarios for a set of Managed Systems

copy 2013 SAP AG All rights reserved 8 Public

SAP Solution Manager Configuration UI components

Step Help Section

Provides detailed information to each

step such as what needs to be done

and what will happen in the

background

Activities

Lists all single activities during each

step along with the documentation

how to perform for the IMG activity

Log

Shows detailed logs per activity

Navigation

Guided procedure with all steps for the

basic configuration

copy 2013 SAP AG All rights reserved 9 Public

SAP Solution Manager Configuration Configuration Roadmap

System Preparation

bull Prepares the Solution Manager system for the basic configuration

bull Needs to be performed fully after a new installation or upgrade

bull Partially after patches and upgrades to update dialog and system users and assign the appropriate default roles

bull During this step the Central Correction Note (CCN) that contains the latest corrections is implemented

Basic Configuration

bull Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)

bull Needs to be performed after new installations and after support packages to perform delta configuration

bull Overview screen tells you which configuration needs update

Managed Systems

Configuration

bull Connection and configuration of managed systems

bull Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on SAP Solution Manager

bull Creation of Logical Components for managed systems

bull Setup of the Exception Management Dashboard for the managed systems

System Preparation

copy 2013 SAP AG All rights reserved 11 Public

System Preparation Roadmap

The scenario System Preparation consists of

the following steps

Create Users

Check Installation

Implement SAP Note

Configure Connectivity

Prepare Landscape Description

Complete

copy 2013 SAP AG All rights reserved 12 Public

System Preparation Create Users

In the first step dialog and system users are created which are needed later during the System

Preparation Select a user to create or

update

Create a new user or

update the authorizations

of an existing user

If the user creation is

performed manually

check the respective

checkbox (4)

Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therfore make sure the user is

correct

copy 2013 SAP AG All rights reserved 13 Public

System Preparation Configure Web Dispatcher

If your SAP Solution Manager systems runs more than one instance a Web Dispatcher is

required

The web dispatcher manages the load balancing of the several web service calls between the diagnostics agents and the

Solution Manager ABAP stack and the Solution Manager ABAP and Java stack

Enter the URL and the port for the

Web Dispatcher

Save the entries

For more information about installing a SAP Web Dispatcher and configuration

options see SAP Help Portal at ldquoURL Generation in an AS-ABAP - Web Dispatcher

Configurationrdquo

copy 2013 SAP AG All rights reserved 14 Public

In this step you explicitly allow SAP Solution Manager to create web services using the

following authentication types

Basic Authentication

X509 Certificate Authentication

Ticket Authentication

System Preparation Set Authentication Types for Web Services

Read the documentation provided

for the activity

Start transaction SOAMANAGER

or click on the provided navigation

link

Activate all authentication

methods and save your changes

The explicit setup is necessary

for security compliance reasons

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 6 Public

Check Prerequisites Optional Client Copy

The SAP delivered client 001 can be used as productive client for SAP Solution Manager

It is also possible to use another productive client

Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client and as

the source client for users

Afterwards convert the Java UME to the new productive client

Restart the Java Stack

Please ensure that you entered 001 as

ldquoSource Client User Mastersrdquo for your client

copy

copy 2013 SAP AG All rights reserved 7 Public

Hardware pre-requisites quick sizerSizing Tool kit

SAP Quick Sizer (for Small to Large Solution Manager installation)SAP Solution Manager

sizing Toolkit (Large Solution Manager installation) provides information on infrastructure

requirements including SAPs Memory Databases and Disk Spaces needed to implement

selected ALM scenarios for a set of Managed Systems

copy 2013 SAP AG All rights reserved 8 Public

SAP Solution Manager Configuration UI components

Step Help Section

Provides detailed information to each

step such as what needs to be done

and what will happen in the

background

Activities

Lists all single activities during each

step along with the documentation

how to perform for the IMG activity

Log

Shows detailed logs per activity

Navigation

Guided procedure with all steps for the

basic configuration

copy 2013 SAP AG All rights reserved 9 Public

SAP Solution Manager Configuration Configuration Roadmap

System Preparation

bull Prepares the Solution Manager system for the basic configuration

bull Needs to be performed fully after a new installation or upgrade

bull Partially after patches and upgrades to update dialog and system users and assign the appropriate default roles

bull During this step the Central Correction Note (CCN) that contains the latest corrections is implemented

Basic Configuration

bull Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)

bull Needs to be performed after new installations and after support packages to perform delta configuration

bull Overview screen tells you which configuration needs update

Managed Systems

Configuration

bull Connection and configuration of managed systems

bull Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on SAP Solution Manager

bull Creation of Logical Components for managed systems

bull Setup of the Exception Management Dashboard for the managed systems

System Preparation

copy 2013 SAP AG All rights reserved 11 Public

System Preparation Roadmap

The scenario System Preparation consists of

the following steps

Create Users

Check Installation

Implement SAP Note

Configure Connectivity

Prepare Landscape Description

Complete

copy 2013 SAP AG All rights reserved 12 Public

System Preparation Create Users

In the first step dialog and system users are created which are needed later during the System

Preparation Select a user to create or

update

Create a new user or

update the authorizations

of an existing user

If the user creation is

performed manually

check the respective

checkbox (4)

Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therfore make sure the user is

correct

copy 2013 SAP AG All rights reserved 13 Public

System Preparation Configure Web Dispatcher

If your SAP Solution Manager systems runs more than one instance a Web Dispatcher is

required

The web dispatcher manages the load balancing of the several web service calls between the diagnostics agents and the

Solution Manager ABAP stack and the Solution Manager ABAP and Java stack

Enter the URL and the port for the

Web Dispatcher

Save the entries

For more information about installing a SAP Web Dispatcher and configuration

options see SAP Help Portal at ldquoURL Generation in an AS-ABAP - Web Dispatcher

Configurationrdquo

copy 2013 SAP AG All rights reserved 14 Public

In this step you explicitly allow SAP Solution Manager to create web services using the

following authentication types

Basic Authentication

X509 Certificate Authentication

Ticket Authentication

System Preparation Set Authentication Types for Web Services

Read the documentation provided

for the activity

Start transaction SOAMANAGER

or click on the provided navigation

link

Activate all authentication

methods and save your changes

The explicit setup is necessary

for security compliance reasons

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 7 Public

Hardware pre-requisites quick sizerSizing Tool kit

SAP Quick Sizer (for Small to Large Solution Manager installation)SAP Solution Manager

sizing Toolkit (Large Solution Manager installation) provides information on infrastructure

requirements including SAPs Memory Databases and Disk Spaces needed to implement

selected ALM scenarios for a set of Managed Systems

copy 2013 SAP AG All rights reserved 8 Public

SAP Solution Manager Configuration UI components

Step Help Section

Provides detailed information to each

step such as what needs to be done

and what will happen in the

background

Activities

Lists all single activities during each

step along with the documentation

how to perform for the IMG activity

Log

Shows detailed logs per activity

Navigation

Guided procedure with all steps for the

basic configuration

copy 2013 SAP AG All rights reserved 9 Public

SAP Solution Manager Configuration Configuration Roadmap

System Preparation

bull Prepares the Solution Manager system for the basic configuration

bull Needs to be performed fully after a new installation or upgrade

bull Partially after patches and upgrades to update dialog and system users and assign the appropriate default roles

bull During this step the Central Correction Note (CCN) that contains the latest corrections is implemented

Basic Configuration

bull Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)

bull Needs to be performed after new installations and after support packages to perform delta configuration

bull Overview screen tells you which configuration needs update

Managed Systems

Configuration

bull Connection and configuration of managed systems

bull Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on SAP Solution Manager

bull Creation of Logical Components for managed systems

bull Setup of the Exception Management Dashboard for the managed systems

System Preparation

copy 2013 SAP AG All rights reserved 11 Public

System Preparation Roadmap

The scenario System Preparation consists of

the following steps

Create Users

Check Installation

Implement SAP Note

Configure Connectivity

Prepare Landscape Description

Complete

copy 2013 SAP AG All rights reserved 12 Public

System Preparation Create Users

In the first step dialog and system users are created which are needed later during the System

Preparation Select a user to create or

update

Create a new user or

update the authorizations

of an existing user

If the user creation is

performed manually

check the respective

checkbox (4)

Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therfore make sure the user is

correct

copy 2013 SAP AG All rights reserved 13 Public

System Preparation Configure Web Dispatcher

If your SAP Solution Manager systems runs more than one instance a Web Dispatcher is

required

The web dispatcher manages the load balancing of the several web service calls between the diagnostics agents and the

Solution Manager ABAP stack and the Solution Manager ABAP and Java stack

Enter the URL and the port for the

Web Dispatcher

Save the entries

For more information about installing a SAP Web Dispatcher and configuration

options see SAP Help Portal at ldquoURL Generation in an AS-ABAP - Web Dispatcher

Configurationrdquo

copy 2013 SAP AG All rights reserved 14 Public

In this step you explicitly allow SAP Solution Manager to create web services using the

following authentication types

Basic Authentication

X509 Certificate Authentication

Ticket Authentication

System Preparation Set Authentication Types for Web Services

Read the documentation provided

for the activity

Start transaction SOAMANAGER

or click on the provided navigation

link

Activate all authentication

methods and save your changes

The explicit setup is necessary

for security compliance reasons

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 8 Public

SAP Solution Manager Configuration UI components

Step Help Section

Provides detailed information to each

step such as what needs to be done

and what will happen in the

background

Activities

Lists all single activities during each

step along with the documentation

how to perform for the IMG activity

Log

Shows detailed logs per activity

Navigation

Guided procedure with all steps for the

basic configuration

copy 2013 SAP AG All rights reserved 9 Public

SAP Solution Manager Configuration Configuration Roadmap

System Preparation

bull Prepares the Solution Manager system for the basic configuration

bull Needs to be performed fully after a new installation or upgrade

bull Partially after patches and upgrades to update dialog and system users and assign the appropriate default roles

bull During this step the Central Correction Note (CCN) that contains the latest corrections is implemented

Basic Configuration

bull Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)

bull Needs to be performed after new installations and after support packages to perform delta configuration

bull Overview screen tells you which configuration needs update

Managed Systems

Configuration

bull Connection and configuration of managed systems

bull Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on SAP Solution Manager

bull Creation of Logical Components for managed systems

bull Setup of the Exception Management Dashboard for the managed systems

System Preparation

copy 2013 SAP AG All rights reserved 11 Public

System Preparation Roadmap

The scenario System Preparation consists of

the following steps

Create Users

Check Installation

Implement SAP Note

Configure Connectivity

Prepare Landscape Description

Complete

copy 2013 SAP AG All rights reserved 12 Public

System Preparation Create Users

In the first step dialog and system users are created which are needed later during the System

Preparation Select a user to create or

update

Create a new user or

update the authorizations

of an existing user

If the user creation is

performed manually

check the respective

checkbox (4)

Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therfore make sure the user is

correct

copy 2013 SAP AG All rights reserved 13 Public

System Preparation Configure Web Dispatcher

If your SAP Solution Manager systems runs more than one instance a Web Dispatcher is

required

The web dispatcher manages the load balancing of the several web service calls between the diagnostics agents and the

Solution Manager ABAP stack and the Solution Manager ABAP and Java stack

Enter the URL and the port for the

Web Dispatcher

Save the entries

For more information about installing a SAP Web Dispatcher and configuration

options see SAP Help Portal at ldquoURL Generation in an AS-ABAP - Web Dispatcher

Configurationrdquo

copy 2013 SAP AG All rights reserved 14 Public

In this step you explicitly allow SAP Solution Manager to create web services using the

following authentication types

Basic Authentication

X509 Certificate Authentication

Ticket Authentication

System Preparation Set Authentication Types for Web Services

Read the documentation provided

for the activity

Start transaction SOAMANAGER

or click on the provided navigation

link

Activate all authentication

methods and save your changes

The explicit setup is necessary

for security compliance reasons

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 9 Public

SAP Solution Manager Configuration Configuration Roadmap

System Preparation

bull Prepares the Solution Manager system for the basic configuration

bull Needs to be performed fully after a new installation or upgrade

bull Partially after patches and upgrades to update dialog and system users and assign the appropriate default roles

bull During this step the Central Correction Note (CCN) that contains the latest corrections is implemented

Basic Configuration

bull Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)

bull Needs to be performed after new installations and after support packages to perform delta configuration

bull Overview screen tells you which configuration needs update

Managed Systems

Configuration

bull Connection and configuration of managed systems

bull Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on SAP Solution Manager

bull Creation of Logical Components for managed systems

bull Setup of the Exception Management Dashboard for the managed systems

System Preparation

copy 2013 SAP AG All rights reserved 11 Public

System Preparation Roadmap

The scenario System Preparation consists of

the following steps

Create Users

Check Installation

Implement SAP Note

Configure Connectivity

Prepare Landscape Description

Complete

copy 2013 SAP AG All rights reserved 12 Public

System Preparation Create Users

In the first step dialog and system users are created which are needed later during the System

Preparation Select a user to create or

update

Create a new user or

update the authorizations

of an existing user

If the user creation is

performed manually

check the respective

checkbox (4)

Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therfore make sure the user is

correct

copy 2013 SAP AG All rights reserved 13 Public

System Preparation Configure Web Dispatcher

If your SAP Solution Manager systems runs more than one instance a Web Dispatcher is

required

The web dispatcher manages the load balancing of the several web service calls between the diagnostics agents and the

Solution Manager ABAP stack and the Solution Manager ABAP and Java stack

Enter the URL and the port for the

Web Dispatcher

Save the entries

For more information about installing a SAP Web Dispatcher and configuration

options see SAP Help Portal at ldquoURL Generation in an AS-ABAP - Web Dispatcher

Configurationrdquo

copy 2013 SAP AG All rights reserved 14 Public

In this step you explicitly allow SAP Solution Manager to create web services using the

following authentication types

Basic Authentication

X509 Certificate Authentication

Ticket Authentication

System Preparation Set Authentication Types for Web Services

Read the documentation provided

for the activity

Start transaction SOAMANAGER

or click on the provided navigation

link

Activate all authentication

methods and save your changes

The explicit setup is necessary

for security compliance reasons

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

System Preparation

copy 2013 SAP AG All rights reserved 11 Public

System Preparation Roadmap

The scenario System Preparation consists of

the following steps

Create Users

Check Installation

Implement SAP Note

Configure Connectivity

Prepare Landscape Description

Complete

copy 2013 SAP AG All rights reserved 12 Public

System Preparation Create Users

In the first step dialog and system users are created which are needed later during the System

Preparation Select a user to create or

update

Create a new user or

update the authorizations

of an existing user

If the user creation is

performed manually

check the respective

checkbox (4)

Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therfore make sure the user is

correct

copy 2013 SAP AG All rights reserved 13 Public

System Preparation Configure Web Dispatcher

If your SAP Solution Manager systems runs more than one instance a Web Dispatcher is

required

The web dispatcher manages the load balancing of the several web service calls between the diagnostics agents and the

Solution Manager ABAP stack and the Solution Manager ABAP and Java stack

Enter the URL and the port for the

Web Dispatcher

Save the entries

For more information about installing a SAP Web Dispatcher and configuration

options see SAP Help Portal at ldquoURL Generation in an AS-ABAP - Web Dispatcher

Configurationrdquo

copy 2013 SAP AG All rights reserved 14 Public

In this step you explicitly allow SAP Solution Manager to create web services using the

following authentication types

Basic Authentication

X509 Certificate Authentication

Ticket Authentication

System Preparation Set Authentication Types for Web Services

Read the documentation provided

for the activity

Start transaction SOAMANAGER

or click on the provided navigation

link

Activate all authentication

methods and save your changes

The explicit setup is necessary

for security compliance reasons

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 11 Public

System Preparation Roadmap

The scenario System Preparation consists of

the following steps

Create Users

Check Installation

Implement SAP Note

Configure Connectivity

Prepare Landscape Description

Complete

copy 2013 SAP AG All rights reserved 12 Public

System Preparation Create Users

In the first step dialog and system users are created which are needed later during the System

Preparation Select a user to create or

update

Create a new user or

update the authorizations

of an existing user

If the user creation is

performed manually

check the respective

checkbox (4)

Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therfore make sure the user is

correct

copy 2013 SAP AG All rights reserved 13 Public

System Preparation Configure Web Dispatcher

If your SAP Solution Manager systems runs more than one instance a Web Dispatcher is

required

The web dispatcher manages the load balancing of the several web service calls between the diagnostics agents and the

Solution Manager ABAP stack and the Solution Manager ABAP and Java stack

Enter the URL and the port for the

Web Dispatcher

Save the entries

For more information about installing a SAP Web Dispatcher and configuration

options see SAP Help Portal at ldquoURL Generation in an AS-ABAP - Web Dispatcher

Configurationrdquo

copy 2013 SAP AG All rights reserved 14 Public

In this step you explicitly allow SAP Solution Manager to create web services using the

following authentication types

Basic Authentication

X509 Certificate Authentication

Ticket Authentication

System Preparation Set Authentication Types for Web Services

Read the documentation provided

for the activity

Start transaction SOAMANAGER

or click on the provided navigation

link

Activate all authentication

methods and save your changes

The explicit setup is necessary

for security compliance reasons

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 12 Public

System Preparation Create Users

In the first step dialog and system users are created which are needed later during the System

Preparation Select a user to create or

update

Create a new user or

update the authorizations

of an existing user

If the user creation is

performed manually

check the respective

checkbox (4)

Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therfore make sure the user is

correct

copy 2013 SAP AG All rights reserved 13 Public

System Preparation Configure Web Dispatcher

If your SAP Solution Manager systems runs more than one instance a Web Dispatcher is

required

The web dispatcher manages the load balancing of the several web service calls between the diagnostics agents and the

Solution Manager ABAP stack and the Solution Manager ABAP and Java stack

Enter the URL and the port for the

Web Dispatcher

Save the entries

For more information about installing a SAP Web Dispatcher and configuration

options see SAP Help Portal at ldquoURL Generation in an AS-ABAP - Web Dispatcher

Configurationrdquo

copy 2013 SAP AG All rights reserved 14 Public

In this step you explicitly allow SAP Solution Manager to create web services using the

following authentication types

Basic Authentication

X509 Certificate Authentication

Ticket Authentication

System Preparation Set Authentication Types for Web Services

Read the documentation provided

for the activity

Start transaction SOAMANAGER

or click on the provided navigation

link

Activate all authentication

methods and save your changes

The explicit setup is necessary

for security compliance reasons

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 13 Public

System Preparation Configure Web Dispatcher

If your SAP Solution Manager systems runs more than one instance a Web Dispatcher is

required

The web dispatcher manages the load balancing of the several web service calls between the diagnostics agents and the

Solution Manager ABAP stack and the Solution Manager ABAP and Java stack

Enter the URL and the port for the

Web Dispatcher

Save the entries

For more information about installing a SAP Web Dispatcher and configuration

options see SAP Help Portal at ldquoURL Generation in an AS-ABAP - Web Dispatcher

Configurationrdquo

copy 2013 SAP AG All rights reserved 14 Public

In this step you explicitly allow SAP Solution Manager to create web services using the

following authentication types

Basic Authentication

X509 Certificate Authentication

Ticket Authentication

System Preparation Set Authentication Types for Web Services

Read the documentation provided

for the activity

Start transaction SOAMANAGER

or click on the provided navigation

link

Activate all authentication

methods and save your changes

The explicit setup is necessary

for security compliance reasons

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 14 Public

In this step you explicitly allow SAP Solution Manager to create web services using the

following authentication types

Basic Authentication

X509 Certificate Authentication

Ticket Authentication

System Preparation Set Authentication Types for Web Services

Read the documentation provided

for the activity

Start transaction SOAMANAGER

or click on the provided navigation

link

Activate all authentication

methods and save your changes

The explicit setup is necessary

for security compliance reasons

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 15 Public

System Preparation Set Authentication Policy for Agents

Starting with Solution Manager 71 the diagnostics agents can be connected with certificate

based authentication to SAP Solution Manager This has the following benefits

Prevents agents locking the agent connection user because of a wrong password

The password of the connection user (SMD_ADMIN) does not expire

Diagnostics agents having authentication issues will show up on the tab

ldquoNon-authenticated agentsrdquo in the Agent Administration UI

New agents and agents (re)connecting to Solution Manager will

automatically use this authentication method after the next agent

connection

Even if the password is not expiring anymore please note that the

certificate itself only has a restricted validity Make sure to recreate a

new certificate before the old one expires

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 16 Public

System Preparation Select SLD

This step enables SAP Solution Manager to access to the System Landscape Directory (SLD)

If SLDrsquos exist specify all of them which are connected to either Managed Systems or Diagnostics agents via the ldquoAdd SLD

Serverrdquo button

Register Solution Manager in one of the SLDs by choosing the ldquoTarget of SAP Solution Manager DSldquo radio button

If no SLD yet exists you can set up a local one in the SAP Solution Manager system

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 17 Public

System Preparation Set Up LMDB

In this step the synchronization between LMDB and one ore more SLDs is set up

The Landscape Management Database (LMDB) synchronizes with the System Landscape Directory (SLD) to collect the

following information from the system landscape

bull SAP Software Catalog (CR content)

bull CIM Model

bull Technical system

landscape descriptions

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 18 Public

System Preparation Migrate Data into LMDB

In this step the System Landscape information can be migrated from the SMSY The SMSY was

used in earlier releases and contains information that cannot be provided by an SLD

It is strongly recommended to perform the Product System migration

This migration is necessary after an

update or upgrade from SAP Solution

Manager below 71 SP04 to avoid

manual recreation

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 19 Public

System Preparation Prepare Outside Discovery - Overview

SAP Solution Manager uses different agents for the monitoring of the landscape In this step

the agents are installed

Install the agents on all hosts on which one or more of the following is running

A Managed System which should be connected to SAP Solution Manager

A CA Wily Introscope Enterprise Manager

A Standalone database

A third party product not registered to an SLD

For more detailed information please refer

to the agent installation strategy document

attached to SAP note 1365123

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 20 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents Installation

For Diagnostics Agents the following activities have to be performed

On each Logical Host on which a managed object is running

Provide a Diagnostics Agent Either install a dedicated Diagnostics Agent or use the agents on-the-fly functionality

Please refer to the agent installation strategy documentation attached to SAP Note 1365123

For complex system landscapes mass-deployment of the Diagnostics Agents can be achieved by running the SAP installer in unattended mode See

SAP Note 1486330 for details

Each Diagnostics Agent can report to exactly one SAP Solution Manager in multi-tier landscapes several Diagnostics Agents per host are needed

eg to connect development systems to the developmenttest Solution Manager and to the productive Solution Manager

It is highly recommended to install all agents and

plug-ins for a system before starting with the managed

systems configuration

Please visit the SOLMAN_SETUP Wiki in SDN to

learn about the Managed System Setup prerequisites

checklist

httpwikisdnsapcomwikidisplaySMSETUPManag

ed_System_Checklist

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 21 Public

System Preparation Connect Diagnostics Agents

In this step all necessary Diagnostics Agents are connected to the Solution Manager system

Only agents using the SLD connection method connected to an SLD known to Solution Manager are visible

Select the SLD that contains your agents and click ldquoGet Agentsrdquo to retrieve the agents

Only agents using the direct connection

method are visible in the SMD Agent

Administration (httpltSolMan-

Hostgt5XX00smdAgentAdmin) You can later

push the SLD settings to all agents via

ldquoAdvanced Settingsrdquo ldquoAgent Candidates

Managementrdquo

The agents of the following systems

need to be connected

Managed Systems

Introscope Enterprise Manager

Solution Manager itself (Self-

Monitoring)

The list of SLDlsquos is maintained in step 51

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 22 Public

System Preparation Complete

The Complete step gives an overview over all performed activities and their status

After the System Preparation the Basic Configuration needs to be performed

To perform the Basic Configuration log off from Solution Manager and log on again with the Solution Manager Administrator

user (default SOLMAN_ADMIN) which you have created in step 1

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

Basic Configuration

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 24 Public

Basic Configuration Roadmap

The scenario Basic Configuration consists of

the following steps

Specify Solution

Specify User and Connectivity Data

Configure CA Introscope

Configure Manually

Configure Automatically

Configure Engagement Reports

Create Configuration Users

Maintain Systems in IBase

Complete

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 25 Public

Basic Configuration Specify Solution

In this step the first Solution is created in Solution Manager

A logical component is created for SAP Solution Manager

Solution Manager and all production systems known in Solution Manager which are not yet part of a Solution are added to the

SAP Solution this makes sure that

bull You can perform Service Delivery for all production systems

bull SAP EarlyWatch Alert is scheduled for all production systems

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 26 Public

Basic Configuration Specify SAP BW System

In this step it is defined witch BW system SAP Solution Manager will use

Solution Manager uses a BW system to store data collected during monitoring for reporting and long term analysis

SAP recommends setting up BW in the production SAP Solution Manager client

A separate BW system can be used for Solution Manager

bull Itrsquos not recommended to use the companys business BW system together with SAP Solution Manager

bull If you use a separate BW system please make sure that the BI_CONT and the ST-BCO is always the level as required by

the Solution Manager (SAP Note 1483508)

By default the BW client is always set to client 001

The BW environment setting can be changed using

function module RS_MANDT_UNIQUE_SET if

bull Another client than 001 is used as production

Solution Manager client BW should be set up in

this client

bull BW should be set up in a separate Solution

Manager client and this client is not 001

bull BW should be set up on a separate system but the

client is not 001

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 27 Public

Basic Configuration Create Users

In the first step the dialog and system users are created which are used later in the System

Preparation Select the user you want

to create or update

Create a new user or

update the authorizations

of an existing user

If user management is

performed manually

check the respective

checkbox ldquoUser creation

and role assignment

performed manuallyrdquo Provide the manually created user

and a password for later use in

SOLMAN Setup

Solution Manager will then not check

the existence password correctness

or the authorizations of the user in this

case therefore please make sure the

user is correct

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 28 Public

Basic Configuration Configure CA Wily Introscope

In this sub-step CA Introscope Enterprise Manager is connected to Solution Manager

It is possible to connect already existing Introscope Enterprise Managers

The recommended version to be used is Wily Introscope Enterprise Manager 91

Prerequisites

A Diagnostics agents needs to be installed and connected to

Solution Manager on the Wily EM host

The operating system user of the Diagnostics agent (default

daaadm for UNIX and SAPServiceDAA for Windows) needs read

and write access to the Wily EM installation directory (default

urssapccmswilyintroscope)

Dependencies on IS Bytecode agents

bull IS BC Agent 9 support only Java 5 and higher

bull IS BC Agent 8 is needed to manage older managed systems running with

Java 4

bull Deploy both SCAs on Solution Manager Java Stack automatic

deployment of the appropriate BC Agent depending on the JVM of the

managed system

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 29 Public

In this step IBase components and objects that represent systems are created

The systems need to be maintained in the IBase of SAP Solution Manager to be used in ITSM

All systems in LMDB and SMSY need to be maintained in IBase

Basic Configuration Maintain Systems in IBase

1 Run the report COM_PRODUCT_UPDATE

manually using transaction SA38 rarr make

sure there are no errors in the report output

2 Run the automatic activities by choosing

ldquoExecute Allrdquo

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 30 Public

Basic Configuration Complete

The Complete step gives an overview over all performed activities and their status

After the Basic Configuration the Solution Manager is ready to connect systems using the Managed Systems Configuration

Please make sure to run the Managed System Configuration also for the SAP Solution Manager itself because otherwise

monitoring functionalities might not work correctly

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

Managed System

Configuration

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 32 Public

Managed Systems Configuration Roadmap

The Managed Systems Configuration consists

of the following steps

Assign Product

Check Prerequisites

Connect Managed System

Assign Diagnostics Agent

Enter System Parameters

Enter Landscape Parameters

Create Users

Configure Automatically

Configure Manually

Check Configuration

Complete

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 33 Public

Managed Systems Configuration Overview

All technical systems known in LMDB are visible in the Managed Systems Configuration

Single technical systems can be found under the tab ldquoTechnical Systemsrdquo

bull Also the single stacks of dual-stack systems are visible here but the configuration is performed in scenario context

Dual-stack system are visible under the tab ldquoTechnical Scenariosrdquo

bull The technical scenario ldquoDual Stackrdquo is created by Solution Manager automatically if it finds an ABAP stack with a matching Java stack in LMDB

during LMDB sync

bull To configure a dual-stack system always start the configuration for the technical scenario

Standalone databases and system databases are visible under the tab ldquoDatabasesrdquo

bull System databases are set up together with the technical system or the technical scenario they belong to

Standalone hosts are visible under the tab ldquoHostsrdquo

bull A host needs to be configured explicitly to activate Diagnostics agent nodes

If the system is not displayed in the technical system list check if it is properly connected to SLD for more information see

httpwikisdnsapcomwikidisplaySMSETUPMaintenance+of+Product+in+the+System+Landscape

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 34 Public

Managed Systems Configuration Roadmap Overview

The roadmap of the Managed System Setup depends on the type of the configured object and only

contains the steps necessary for this system

To get more information about the selected configured object use the link for the technical system

Dual stack system

J2EE system

DatabaseHost only

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 35 Public

Managed Systems Configuration Assign Product

The first step is to maintain the Managed System information in LMDB this includes

Assigning the technical system(s) to a product system

Selecting the product instances that are diagnostics relevant

Assigning the technical system to a logical component

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 36 Public

Managed Systems Configuration Assign Product ndash Set Diagnostics Relevant Flag

Set Diagnostics Relevant Flag

There are three ways to set the Diagnostics

Relevant flag

A Set the Diagnostics Relevant flag

automatically

Or edit the assignment manually To do this

choose ldquoEdit Assignmentrdquo

B Set the Diagnostics Relevant flag on the

ldquoProduct Instancesrdquo tab Here the flag is

also set for all assigned product instances

for which a Diagnostics template exist

C Set the Diagnostics Relevant flag for

selected product instances on the

ldquoProduct Instances (Details)rdquo tab

Make sure to select the product

version listed in SAP note

1478974 as diagnostics relevant

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 37 Public

Managed Systems Configuration Assign Product ndash Assign Logical Components

Assign Logical Components

As of Solution Manager 71 SP 10 Logical

Components are related to Technical

Systems You need to create one Logical

Component for each Technical System

1 Choose ldquoAssign Logical Componentrdquo

2 Select the correct client (ABAP only)

3 Select the system role

4 Select the correct Product Instance

5 Select an existing Logical Component or

create a new one

6 Click the ldquoCheckrdquo button to verify your

entries

7 Click OK

8 Save your changes

Up to SM 71 SP 08 Logical Components were related to the Product System This way you could indirectly assign the ABAP and the Java stack of dual stack system to the same Logical

Component This is not longer possible

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 38 Public

Managed Systems Configuration Logical Components in LMDB

With SAP Solution Manager 71 SP 10 the maintenance of Logical Components moved to LMDB

You can access Logical Components via transaction LMDB under the tab ldquoLogical Componentsrdquo

You can

1 Assign or delete technical systems tofrom

a Logical Component

2 Maintain the available system roles

(changes made here apply to all logical

components system wide)

3 Change the system role of a Technical

System

4 Delete a Logical Component

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 39 Public

Managed Systems Configuration Check Prerequisites

The check prerequisites step verifies that the Managed System and Solution Manager fulfill the

diagnostics prerequisites from a landscape definition and software component point of view

Run the prerequisites check If there is an error check the log information for details and correct the errors

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 40 Public

Managed Systems Configuration Connect Managed System

This step only exists for ABAP systems because only ABAP needs to be connected via RFC

For each ABAP system create at least one READ RFC destination (typically connect to the active client)

You also need to create a READ RFC destination for Solution Manager itself The NONE RFC destination is currently not supported by

Diagnostics

To be able to create TRUSTED RFC destinations make sure the user in Solution Manager and the Managed System has the authorization S_RFCACL To

use the TRUSTED RFC destination the user needs S_RFCACL in the Managed System

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 41 Public

Managed Systems Configuration Connect Managed System ndash Further functionality

Create ABAP administration user

For the creation of RFCrsquos and further configuration a quite powerful

user is needed

Create this user here

Create the user as user type ldquoSystemrdquo to prevent dialog log on with this

user

Clean up existing RFCs

If necessary clean up existing RFCs for the managed system

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 42 Public

Managed Systems Configuration Assign Diagnostics Agent

To be able to connect a system for Root Cause Analysis and Technical Monitoring assign a

Diagnostics Agent to each instance of the system

Select the instance from the list and click ldquoAssignrdquo

In the new window select the Diagnostics Agent from the list that has the same host name as the managed instance

It is recommended to install and connect all required agents before the managed system setup see

httpwikisdnsapcomwikidisplaySMSETUPManaged_System_Checklist

Use Check Host Agents to check the connection status

and the release of the SAP Hostagent

If the required agent is not in the list use the SLD Agent

Candidates to connect the agent from SLD or the Agent

Admin for agent trouble shooting Preferred method

Connect the Diagnostics Agent via the smdsetupscript

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 43 Public

Managed Systems Configuration Enter System Parameter

In this step the connection parameters of the Managed System are configured

Use the Check URL link to check if the load

balancer host and the HTTP port are correct

(the port can be found in transaction SMICM

of the managed system and under ldquoTechnical

Instancesrdquo ldquoHTTP Portsrdquo in the LMDB

To make EWA alerts visible in alert inbox

check Activate EWA Monitoring

Carefully read the context help of the input

fields and provide the necessary input

The database parameters

depend on the database type

Provide an administrative user for

the managed system Use the Test

Logon links to verify the provided

logon data

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 44 Public

Managed Systems Configuration Enter Landscape Parameter

In this step verify the Managed Systemrsquos default landscape parameters Sometimes additional

input is required so that the step can be performed correctly

Check every landscape parameter carefully

Use the ldquoCheck existence of path when savingrdquo option to make sure the entered paths are valid

The following statuses are possible

bull No Parameter No input required

bull Default used Verify the parameter

bull Input missing Enter the parameter

bull Agent offline This is for your information

only The agent on the system is only

needed to verify the entered values on

the system (eg the instance path) You

can continue even when the agent is

offline

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 45 Public

Managed Systems Configuration Create Users

To enable the Diagnostics Agent to gather data about the Managed System connection users

for the ABAP and the Java stack are required

Additionally users can be created to be provided to SAP in case the support needs to log on to the system

Select the user that

should be created or

updated

Either create a new user

or update the

authorizations of an

existing user

If your user management

manually is performed

manually check the

respective checkbox (4)

Provide the manually created user and a

password

Solution Manager will then not check the

userrsquos existence itrsquos password nor if the user

has the correct authorizations

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 46 Public

In this step several automatic activities are performed

Connect the managed system to Root Cause Analysis

Set up a Single-Sign-On connection between the managed system and Solution Manager (needed for RCA)

Set up of the alerting for Early Watch Alerts

Managed Systems Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 47 Public

Managed Systems Configuration Configure Manually

In this step several manual activities can be performed that cannot be carried out

automatically These are

Maintain SAPRouter data for the system in Service Market Place

Adjust HTTP log parameter to enable ICM logging

Restart the Java Stack (this is necessary for the Byte Code Adapter installation)

Set up the R3 connection to enable remote supportability for the Managed System

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 48 Public

This step verifies whether the system is configured correctly Additionally the status in the

overview of the Managed Systems Configuration is updated

Select ldquoExecute Allrdquo to perform all activities

If there are errors in the configuration check please see the log area for details and fix the listed errors

Managed Systems Configuration Check Configuration

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 49 Public

Managed Systems Configuration Complete

The Complete step gives an overview over all performed activities and their status

If there is all green in the Managed Systems Configuration the Managed System can be set up for Technical Monitoring and

other scenarios in SAP Solution Manager

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

Housekeeping

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 51 Public

Housekeeping tips

To ensure a smooth operation of your Solution Manager system

Configure the BW Housekeeping job This job deletes data from the cubes in BW compresses the cubes and deletes

requests SAP Note 1480588

When using MS SQL or Oracle please 1178655

Keep your Solution Manager patched and up to date

Update the Solution Manager Central Note

Make sure to implement SAP Note 1717403 Collective Note for Extractor FWK - ST71

By default Solution Manager is configured to support about 40 SMDAgents Adjust the number of threads ndash SAP Note

1916137

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 52 Public

Further information

Documentation (Master Guide Sizing

Upgrade)

httpservicesapcominstguides -gt SAP

Components -gt SAP Solution Manager

Expert Guided Applications (EGI)

httpswebsmp107sap-

agdesapbcbspspnesa_redirectindex

htmgotocal=Xampdeliverymethod=0401

Notes

706705 Solution Manager Components

for Messages

1478974 - Diagnostics in SAP Solution

Manager 71 (Supported Products)

1483508 Solution

Manager 710 Root Cause Analysis pre-

requisites

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

Thank you

Contact information

Roland Hoeller

Senior Support Engineer

RolandHoellerSAPcom

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

Appendix Solution Manager Upgrade

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 55 Public

SAP Solution Manager 71

Installationupgrade roadmap

Implement

Pre-requisites

Implement missing

software on managed

systems

Install

Solution

Manager Upgrade

Solution

Manager

Including

Wili IS EM

Download

software from

SMP

Solman_setup

Repeat

managed

Systems

configuration

for PI systems

Preparation

Upgrade Installation

Post Processing

Upgrade

SAPHostAgent

on all managed

hosts

Install

SMDAgent

for DB host

and Wily

Hosts

Perform

Backup

Run Self-

Diagnosis

Solman_setup

Install wily

IS EM

Install

SMDAgent

for All

managed

Hosts

Run managed

Systems

configuration

Install

SMDAgent

on Wily

Hosts

Restart Java

Managed

systems

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 56 Public

Installation amp Upgrade

upgrader

The complete upgrade process is divided into eight roadmap steps

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 57 Public

Installation amp Upgrade

upgrader

The upgrade program upgrades an ABAP system using a system cloning and switch procedure

This procedure installs a copy of the system the shadow system in parallel with the original system The

shadow system is used to update the affected software components and to install the additional

components while the original system is still in production operation

Space

bull Operating two instances in parallel places increased demands on free space in the file system in the

database and on the system resources

Duration

bull No precise guidelines can be given for the duration of an upgrade The duration of the system cloning

depends to a great extent on the amount of data the database system and the hardware and can take

several hours Although the system can still be used in production operation you have to take into

account a possible performance decrease during this cloning process

To upgrade to SAP Solution Manager 71 on the JAVA Stack the SAP Enhancement Package Installer uses

a deployment-based procedure No shadow system is required for the JAVA Stack The procedure is highly

automated with minimum user interaction

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

Appendix Prerequisites

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 59 Public

Check Prerequisites S-Users in SAP Service Market Place

S-Users are requested and maintained via SAP Service Market Place httpservicesapcomuser-

admin

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 60 Public

Ensure that all support package levels for the managing system (Solution Manager) and the

managed systems are up to date according to SAP Note 1483508

Check Prerequisites SAP Solution Manager Support Package Level

Main Component Version

Solution Manager

ABAP Stack

SAP_BASIS 702 SP13

ST 710 SP10

Solution Manager

Java Stack

LM-SERVICE 710 SP10

BI Component BI_CONT 706 SP06

SAP_BW 702 SP13

ST_BCO 710 SP07

CRM BBPCRM 701 SP10

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 61 Public

Check Prerequisites Update SLD CR Content amp Model

Check SLD Prerequisites

Landscape data in Solution Manager 71 is stored in the Landscape Management Database which is synchronized

with SLD This synchronization requires some minimum version of the CR Content and the model deployed in the

connected SLD

bull SLD Netweaver Stack NW 702 SP 06 Patch 5

bull CR Content minimum 91 better latest available

bull Model Version minimum 1636 better latest available

To check the content version go to httpsldhostsldportsld

Check SAP note 669669 for further

information on CR Content amp Model

update

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 62 Public

Check Prerequisites RFC Destination SAPOSS

SAP Solution Manager needs a working connection to the SAP support backbone

Check if RFC destination SAPOSS is working properly in SM59

If there are connection problems with SAPOSS check and maintain the connection settings in transaction OSS1

the configuration changes will be adapted automatically

You can find detailed information about transaction OSS1 and RFC connection SAPOSS in SAP Note

17285

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 63 Public

Check Prerequisites SAP Solution Manager Profile Parameters

Make sure the following profile parameters are set in you SAP Solution Manager system

Check SAP note 1582842 - Profile parameters for Solution Manager 71 for latest recommendations

Parameters Description Recommended value

abapbuffersize Program buffer size 500000

abapshared_objects_size_MB Size of Shared Objects Memory in MB 100

rsdbntabentrycount Number of nametab entries administrated 30000

rsdbntabftabsize Data area size for field description buffer 60000

rsdbntabirbdsize Data area size for initial records buffer 15000

rtbbbuffer_length Size of single record table buffers 60000

rsdbcuabuffersize CUA Buffer Size 10000

zcsatable_buffer_area Size of generic table buffer 100000000

zcsadb_max_buftab Directory entries in generic table buffer 10000

zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000

sapbufdir_entries Maximum number of entries in the

presentation buffer 10000

rsdbobjbuffersize Size of exportimport buffer 50000

rsdbobjmax_objects Max no of exportingimporting objects 20000

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

Appendix System Preparation

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 65 Public

SAP Solution Manager Configuration with

SOLMAN_SETUP

SAP Solution Manager 71 is configured using guided procedures

Accessible via transaction code SOLMAN_SETUP

Allows an easy fast and step-by-step configuration of SAP Solution Manager

Single easy to use wizard for system

preparation amp basic configuration

Highly automated configuration

Integrated documentation for each step

Easy access to open tasks and postponed

activities

Configuration of all managed systems from

one central entry point

Configuration of other scenarios like Technical

Monitoring Data Volume Management

Exception Management hellip

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 66 Public

SAP Solution Manager Configuration Configuration Dependencies

The Basic Configuration and the configuration of the managed systems build the basis for further

configuration and make sure the following basic functionalities is set up

bull Early Watch Alerts

bull Service Engagement and Delivery

bull Issue Management

bull Maintenance Optimizer

bull Send tickets to SAP

System Preparation

(~ 2h) Basic Configuration (~ 3h)

Managed System Configuration (~ 1h per system + agent installation)

Data Volume

Management

Measurement Platform

IT Service Managem

ent

Change Request

Management

Business Process

Monitoring

Business Process Change Analyzer

Custom Code

Management

Technical Monitoring (~ 1h for Infrastructure Configuration amp ~1h per system type for Template Maintenance if custom templates are used)

Job Monitoring

PI Monitoring

BI Monitoring

SolMan Self-

Monitoring

Interface Monitoring

End-User Experienc

e Monitoring

Please add waiting time for initial LMDB sync (~4 ndash 12h))

bull System recommendations

bull Project Management

bull Solution Documentation

bull Test Management

SOLMAN_SETUP supports the standard customizing for

the most Solution Manager scenarios Further expert

customizing is possible using SAP Reference IMG

EWA Alert Managem

ent

Job Managem

ent

Service Avail

Management

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 67 Public

Check Prerequisites Optional User management with Central User Administration

(CUA)

Option 1 Create and maintain users manually

bull You can create all required users manually before or during

SOLMAN_SETUP

bull The documentation in the user creation steps of SOLMAN_SETUP tell

you which users are needed and which roles need to assigned to this

users

bull After the creation of the user you can provide this existing user to

SOLMAN_SETUP

bull This is the only option if you run a central user management tool other

than SAP CUA

Option 2 Create users automatically via SOLMAN_SETUP

in CUA

bull To be able to create users automatically in the CUA via

SOLMAN_SETUP you need to adjust the roles of the CUA_ADM user

used in the RFC (2) from the managed system to CUA

bull The picture below describes the dataflow during user creation in CUA

During the basic configuration of SAP Solution Manager several users and roles are created if you run a CUA

or another user management tool you have two options to handle this user creation

See the SAP Solution Manager Security Guide for details

httpservicesapcom~formsapnet_SHORTKEY=011000358700

00735220amp_OBJECT=011000358700000482312011E

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 68 Public

System Preparation Check Installation

This is an automatic installation check for configuration-relevant parts of the installation

If a check status turns red check the Documentation for information on how to solve the problem

Repeat the check to make sure the problem is fixed

You can exclude checks by setting Execution Status to Postpone or Manual

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 69 Public

System Preparation Implement SAP Note

In this step you download and implement the Central Correction Note for Solution Manager

The CCN comprises all corrections for the configuration

scenarios of the basic configuration

It is recommended to implement the complete central

correction note but if you want to implement only certain

corrections the note contains the information about all

single notes and their source application

You must implement the central correction SAP Note

manually with the SAP Note Assistant (SNOTE)

Some post-processing steps in the notes could be

automated these can be performed by executing the Post-

Processing

In a multi-tier Solution Manager landscape the note

download is performed in the development system and the

note corrections are transported to the other systems

Nevertheless the post processing steps have to be

performed in each system

Check for notes which require manual activities before the

implementation and for notes that require manual post-

processing activities You will be notified by SOLMAN_SETUP if a new version of the note a

released

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 70 Public

System Preparation Configure Connectivity

In the sub-steps of this step you perform the initial part of the connectivity configuration this

includes

Web Dispatcher related configuration

Web services related configurations

Authentication policy for Diagnostics Agents connecting to the SAP Solution Manager system

SAP Gateway (required in the scope of the Sybase Unwired Platform integration)

Setup of SAP Connect for notification management

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 71 Public

System Preparation Enable Web Services

In this step you enable the SAP Web Services communication between the ABAB and the Java

stack of SAP Solution Manager

Required logical ports are created in transaction SOAMANAGER the creation is performed automatically

The user SM_INTERN_WS is used for the web service communication

The activity has to be re-performed if the user password is changed

Make sure you change the password only in SOLMAN_SETUP System

Preparation Step 1

To check the logical ports

and end points work

correctly check them via

transaction SOAMANAGER

as described in the activity

documentation

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 72 Public

System Preparation Configure Gateway

In this step you activate SAP NetWeaver Gateway Services for mobile devices

To enable mobile devices like smartphones or tablets to connect to SAP Solution Manager via eg the Technical Monitoring

app

Prerequisite To create a system alias a customizing request has to be created in Solution Manager first

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 73 Public

System Preparation Configure SAPconnect

In this sub-step you enable Solution Manager to send notifications

SAPconnect infrastructure is set up and the SAPconnect send job is scheduled automatically (period 10 minutes)

To send notification you additionally have to maintain the Global Recipient pool and maintain recipient lists later on in the

Notification Management

Node the name of the SMTP node which handles outgoing e-mail

Host the name of your mail server

Port the port number at which your mail server can be accessed

To enable SAP Solution Manager to send notification via e-mail

select the SMTP Active field

To enable SAP Solution Manager to send notification via SMS

select the FaxPager Active field

In the Domain field you can for example enter the domain name

of your organization if you want to restrict the scope of possible

recipients

To set up a more complex mail

configuration or change the send job

frequency call transaction SCOT

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 74 Public

System Preparation Prepare Landscape Description

When you have completed this step the system landscape description is stored in SAP

Solution Manager This includes the following sub-steps

The SAP Solution Manager system is registered in the SLD

The technical system descriptions CIM model and the SAP Software Catalog (CR content) from the System Landscape

Directory (SLD) are synchronized with the Landscape Management Database (LMDB) in SAP Solution Manager

The synchronization connection between LMDB and the relevant SLDs is setup and activated

For upgraded SAP Solution Manager systems system information created in SMSY previously can be migrated into LMDB

Diagnostics agents and SAP Hostagents are installed

Diagnostics agents are connected to SAP Solution Manager

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 75 Public

System Preparation Set Up LMDB - Details

Configure Object Server

The Object Server Name differentiate equal objects in

different CIM servers (SLD or LMDB)

Choose a name that is different from all other SLD or

LMDB object server names in you landscape

Add new Synchronization Connection

Select the SLD with which you want to synchronize from

the ldquoSource URLrdquo drop-down list

Save amp Activate your connection

The very first activation starts an initial full

synchronization to import all SLD system information to

the LMDB which can take several hours

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 76 Public

System Preparation Set Up LMDB - Details

ActivateDeactivate

You can activate and deactivate a connection

After the first full synchronization and incremental

synchronization imports new changes every 10 minutes

The job for the LMDB synchronization is called

SAP_LMDB_LDB_0000000001

Advanced Change SourceTarget Rank

A rank is the quantifier in case of conflicting changes

The LMDB rank must be higher than the SLD rank to

protect manual changes in the LMDB from being

overwritten

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 77 Public

System Preparation Set Up LMDB - Details

Advanced Add Notification

For connected SLDs as of SAP Netweaver 71 SP 12 (SAP

note 1546079) you can configure an additional SLD

change notification to actively propagate SLD content

changes

Advanced Set CR Source

One of the SLD systems must be selected as the CR

Source

This SLD must have the latest SAP Software Catalog

including SAP CR Content updates and own product

definitions

The first synchronization connection is automatically

selected as CR source

If you set up notification additional batch jobs which actively

request SLD changes are started at notification time To

avoid high system load due to notifications SLD and LMDB

limit notifications and notification processing if the change

rate is too high

System landscape descriptions are always

imported from all connected SLDs Therefore

they must not overlap

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 78 Public

System Preparation Set Up LMDB - Details

Data Migration from SMSY to LMDB

After the first full LMDB synchronization you can migrate

the complete description of selected technical systems

from SMSY

This migration is restricted to systems that were created manually

in SMSY in earlier SAP Solution Manager releases and for which no

SLD data suppliers for an automatic data transfer are available

Never use this for systems registered in an SLD connected to

Solution Manager otherwise there is a risk of system duplicates in

LMDB with one system that was migrated from SMSY and the other

one synchronized from the SLD

To migrate information that cannot be provided by an SLD

such as product system information and custom attributes

you will use the next step ldquoMigrate Data into LMDBrdquo

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 79 Public

System Preparation Configure Automatically

In this step different basic ABAP configuration steps are performed

Choose ldquoExecute Allrdquo to perform all activities

In case of errors check the log area and correct the error

If the security regulations of your organization require it you can perform the activities manually as described in the activities

documentation

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 80 Public

System Preparation Prepare Outside Discovery ndash SAP Hostagents

For SAP Hostagents the following activities have to be performed

On each physical or virtual host

InstallUpdate SAP Hostagent The installation procedure is described in the installation guide attached to SAP note 1031096

It is recommended to enable the automatic update feature of the SAP Hostagent so that you can update the Hostagent centrally This is described in SAP

Note 1473974

Establish Trusted Connection The information gathered by the SAP Hostagent (OS and DB information and information on hostnames on the

physical host) is provided to the Diagnostics Agent via a Web Service To call this Web Service the OS user of the diagnostics agent (default

daaadm) must be a trusted user to the SAP Hostagent

As a rule of thumb you can say you have to install the SAP Hostagent and establish the trusted connection on each host that runs an Operating

System

SAPMSCT

RL

SAPDBCT

RL

SAPOscol

Web S

erv

ice

SAP Hostagent

Web S

erv

ice

Physical Host

P4 C

lient

IS Host

Adapter

Outside

Discovery

Other Agelets Other Agelets

Diagnostics Agent

Unix

Windows

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 81 Public

System Preparation Prepare Outside Discovery ndashDiagnostics Agents On-the-fly

An agent on-the-fly is similar to a standard Diagnostics Agent regarding

Runtime behavior

Configuration

Deployment layout

Each agent node still has its own configuration and its own dedicated logical host name

The agents on-the-fly capability has to be activated in the managed host setup (Managed Systems Configuration) for

the physicalvirtual host

After the activation the diagnostics agent installed on this host can start up and shut down agents on-the-fly

Which agents are started depends on the current logical hostname situation on the physicalvirtual host requires it

eg if an SAP instance moves from one physical host to another (taking it logical host name with it)

Only one Diagnostics Agent needs to be installed on

a physical host with several logical managed hosts

See the Appendix of this slide show for

installation and setup information

With SP 05 the agents on-the-fly are recommended to be used mainly for HA scenarios where a logical host moves from one physical host to

another See the RCA wiki under httpwikisdnsapcomwikidisplaySMSETUPDiagnostics+Agent+and+HA+support for details

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 82 Public

System Preparation Prepare Outside Discovery ndash Diagnostics Agents new functionality

with SP 05

Up to Solution Manager 71 SP 04

bull One diagnostics agent instance needed to be installed for each

managed host

bull High installation effort especially in highly virtualized environments

bull Higher resource consumption by the diagnostics agents

As of Solution Manager 71 SP 05

bull Introduction of the agent on-the-fly concept that enables a diagnostics

agent to start up agent instances on-the-fly as required by the current

hostname situation

bull Agent on-the-fly are running under the same SID and instance

number but in isolated processes

bull Agents on-the-fly share the SAP Kernel and the SAPJVM binaries of

the parent diagnostics agent

Physical Host Physical Host SAP

Hostagent

SAP

Hostagent

Jstart

Logical Host A

sapsta

rtserv

Agent SIDSMDA98

Logical Host A

Logical Host B

Jstart

Logical Host B

sapsta

rtserv

Agent SIDSMDA97

Logical Host A

Logical Host B

Jstart

Logical Host A sapsta

rtserv

Agent SIDSMDA98

Jstart

Logical Host B

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

Appendix Basic Configuration

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 84 Public

Basic Configuration Specify User and Connectivity Data

In the sub-steps of this step you make sure that SAP Solution Manager can be connected to

SAP and to other systems this includes

Maintaining the connection to SAP Service Market Place

Specifying which system will be used as BW to store data collected by SAP Solution Manager during monitoring

Create users necessary for internal and external connectivity of Solution Manager

Set up the RFCs and web services for Root Cause Analysis and other scenarios

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 85 Public

Basic Configuration Specify Connectivity Data

In this sub-step you set up the connection between Solution Manager and SAP Service Market

place

Enter the S-user(s) that were created during the preparation steps

During this step two RFC destinations are created

bull SAP-OSS

bull SAP-OSS-LIST-O01

The S-user for SAP Backend will be maintained in the

global settings of Solution Manager and it will be used

in the RFC connections SAP-OSS and SAP-OSS-

LIST-O01

The S-User for Communication will be assigned to the

user SOLMAN_ADMIN and SOLMAN_BTC in

transaction AISUSER

For security reasons it is recommended to maintain two S-users for Solution Manager The S-user for

SAP Backend should have no authorizations since it could be misused for direct logon

The S-user for Communication is needed to perform tasks like synchronize service messages and system

data and to request licenses This user needs more extensive authorizations

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 86 Public

Basic Configuration Set Up Credentials

In this step you provide the administrator users used for further setup

Recommendation Use the default SOLMAN_ADMIN user as the SAP Solution Manager administrator This ensures that the

administrator has the required authorizations

If you set up the BW in a different client or system you have to create or update a BW administrator user

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 87 Public

Basic Configuration Solution Manager Internal Connectivity

In this sub-step you set up RFCs and web service URLs for the communication between

Solution Manager ABAP and Java stack and between Solution Manager and the Diagnostics

Agents

Create RFC connections between the ABAP and Java stack of SAP Solution Manager

Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics agents

Switch off the maintenance mode of SAP Solution Manager so that the Diagnostics agents can connect to SAP Solution

Manager

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 88 Public

Basic Configuration Configure CA Wily Introscope ndash Extended Configuration

Expert Mode

The expert mode give you more detailed information on

the connected CA Wily Introscope

Gives you access to the ldquoDelete Referencesrdquo functionality

to clean up references between managed systems and CA

Wily Introscope

Delete References

If you want to delete CA Wily Introscope from Solution

Manager you have to delete all references of managed

systems to this CA Wily Introscope first

Please note that the Introscope agents assigned to this

systems will continue to report to the old CA Wily

Introscope until you re-run the relevant activities in the

managed systems setup for these systems

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 89 Public

Basic Configuration Configure Manually

In this step you perform several manual activities in Solution Manager that cannot be carried

out automatically

You configure the logical systems in SAP Solution Manager

You activate automatic service content updates

You can delete documents and sessions from Solution Manager

You activate extended authorization checks for Workcenter views

You can perform configuration for IT Task Management

You setup HTTP and R3 connections in Service Market Place to enable remote supportabilty

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 90 Public

Basic Configuration Configure CA Wily Introscope ndash Connect existing CA Wily Introscope

Step 1 Discover Installation

Click ldquoImport Existing Installationrdquo

Enter the installation path under which CA Wily Introscope

is installed on the host (default

usrsapccmswilyintroscope)

Select the Diagnostics agent which is installed on the host

Import all CA Wily Introscopes in your landscape also

MoMs and Collectors

Step 2 Assign a User

Assign a connection user and a password for each CA Wily

Introscope Enterprise Manager

By default the administration user of the CA Wily

Introscope Enterprise Manager is assigned as the

connection user

You can also create own users

Click the ldquoRefreshrdquo button when you are done

If the system denies

access ensure that

the diagnostics

agent user has

readwrite access

to the folder in

which CA Wily

Introscope is

installed

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 91 Public

Basic Configuration Configure Manually

Maintain Logical Systems

The logical system name identifies the SAP system client uniquely in a

distributed SAP landscape this is necessary for ALE and RFC

communication

The following functions use logical systems

bull Customizing Distribution Business Process Monitoring BI Analysis

Service Desk and Change Request Management

The SAP recommendation for the logical system name is

ltSIDgtCLNTltclientgt

Service Content Update Configuration

Instead of applying ST-SER Support Packages you can activate the

Service Content Update to keep your EarlyWatch Alert up-to-date

The SAP Solution Manager will then always retrieve the latest

corrections for the EarlyWatch Alert from SAP Service Marketplace

1 Maintain the logical

systems names in view

V_TBDLS using

transaction SM30

2 Assign the logical

system name to a

client in transaction

SCC4

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 92 Public

Basic Configuration Configure Manually

Enable Work Center Authorization Check

With Solution Manager 71 a new check on authorization object

SM_WC_VIEW is provided with this check you control the views and

tasks (navigation panel entries) in a work center

By default this authorization check is not active you need to activate

the authorization check by activating a BAdi

The authorization object is contained in the new

SAP_SMWORK_BASIC_ roles

Caution Refer to the activity help for more

detailed information on the activation of the

BAdi

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 93 Public

Basic Configuration Configure Manually

Enable remote HTTP and R3 Connection

With this activity you set up the HTTP and R3 connection for the system from SAP Service Market Place to enable SAP support to access the system for

remote support

Please refer also to SAP note 592085 (HTTP) and SAP note 812732 (R3) for details

1 Make sure SAP Router data is maintained

for your system in the system data in SAP

Service Market Place

2 Go to

wwwservicesapcomremoteconnection

and click ldquoMaintain Connectionsrdquo

3 Click on your systems and scroll to the area

ldquoSet up Connection typesrdquo

4 Click on the connection type and maintain

the contact person

5 Donrsquot forget to maintain the URLs for the

HTTP connection

6 In the section ldquoOpenClose Connectionrdquo you

can then select your connection to open it

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 94 Public

Basic Configuration Configure Manually

Delete Session Documents and Download

With this activity you can delete sessions and their documents and

delete download data and reporting documents of a solution or

landscape

When deleting a check is made for inconsistencies within the sessions

and documents to be deleted

This activity helps you to reduce data volume in Solution Manager

Import Calendar Entries

IT Calendar Work Mode Management and central Notification

Management use factory and holiday calendars

With this activity you extend the validity date of the SAP calendars if

necessary

1 Call transaction SCAL and

display the Factory Calendars

2 Make sure they are valid until

2050 In case the calendars are only

valid until 2010 you can

import the calendars valid

until 2050 from SAP Note

1426524

If SAP Calendar was

changed you can manually

maintain the calendars as

described in SAP note

1426524

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 95 Public

Basic Configuration Configure Manually

Configuration for IT Task Management

IT Task Management is based on IT Service Management in SAP Solution Manager 71 and hence some configuration has to be done before it can

be used

1 Copy transaction type SMOT to transaction type ZMOT

2 Maintain your custom transaction type if you chose another name than ZMOT

3 Create Business Partners for Solution Manager users

4 Create an Organizational Model

5 Schedule task scheduler batch job

Please refer for SAP Note 1825634 for more details

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 96 Public

In this step you schedule automatic activities in Solution Manager

Solution Manager BW system related setup and customizing is performed

Piece list import and customizing to set up the most important basic functions like Maintenance Optimizer Issue Management

and Service Desk

Activation of WebDynpro services and creation of external aliases necessary to work with Solution Manager

Scheduling of SAP basis and Solution Manager specific house-keeping jobs

Setup of Solution Manager Diagnostics and the extractor framework

Setup of the monitoring and alerting infrastructure

Basic Configuration Configure Automatically

1 Choose ldquoExecute Allrdquo to execute all activities

2 A progress bar shows you the current execution

status

3 If an activity fails check the log area for details

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 97 Public

In this step you perform further manual configuration

You activate BW content and schedule data extraction necessary to retrieve data from SAP Solution Manager and SAP

Service and Support Backbone to generate landscape data and engagement reports

The activities in this step have some automatic activities from the previous step as prerequisite check the activity

documentation and make sure all necessary activities from the previous step were performed successfully

Start the activities via the link in the navigation column the setup is done as soon as the transactions are launched

Basic Configuration Configure Engagement Reporting

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 98 Public

Basic Configuration Create Configuration Users

In this optional step you create configuration users for the other Solution Manager scenarios

The users will be created with the necessary authorizations to perform the configuration of the single Solution Manager

scenarios

You can use this users as templates for other users

Details about the users and roles can be found in the user documentation and

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

Appendix Managed System Configuration

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 100 Public

Managed Systems Configuration Status Overview

In the Managed System Configuration the configuration status of the system is displayed

You can use the ldquoShow Detailsrdquo button to display status details below the overview table and to update the status via status

check

Use the filter functionality to find the system you are interested in

To start the configuration of a systemscenariodatabasehost select it from the list and press the respective ldquoConfigure helliprdquo

button

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 101 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System

1 Click the ldquoAssign Product Systemrdquo link

2 ldquoSelectrdquo the product system if it doesnrsquot

exist use the ldquoCreaterdquo button to create it

3 Use the ldquoProposalrdquo option to find the

correct product version and product

instances for your system

4 Select the correct product instances

5 Save

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 102 Public

Managed Systems Configuration Assign Product ndash Assign Product System

Assign Product System (option)

If the correct product version is not in the list

close the pop-up

1 Switch to the tab ldquoProduct Instance

(Detail)rdquo and use the ldquoAddrdquo button to

assign the product instances manually

2 Use ldquoProposal For All Software

Componentsrdquo

3 Select the correct product instance

4 Now assign the product system on the tab

ldquoProduct Instancesrdquo with the button ldquoEdit

Product System Assignmentrdquo

5 Select ldquoAssign All Unassignedrdquo

6 Save

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 103 Public

Managed Systems Configuration Connect Managed System ndash Create RFC Destinations

Create RFC Destinations

1 Select the client for which you want to

create RFC destinations on the table

above

2 Add additional information to the RFC

(eg if you want to use load balancing)

3 Select the RFCs you want to create and

how you want to create the users used in

the RFC destination

4 Fill in the administrator credentials (if you

create BACK RFCs you also need to

provide credentials for Solution Manager)

hellip you can only add credentials after

selecting RFCs to create or update

5 Click the ldquoExecuterdquo button

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 104 Public

Managed Systems Configuration Configure Manually

Maintain SAP Router data

By maintaining SAP router data for the managed system in the SAP

Service Market place you make sure the system can be opened for

remote service connections

Navigate to httpservicesapcomsystem-data and select the

managed system

Maintain the system data for the SAP Router that you wish to use on

the System tab in the SAP Router area

Adjust HTTP Log Parameter

To be able to analyze logs written by the Internet Communication

Manager (ICM) with Root Cause Analysis you need to maintain the additional parameter icmHTTPlogging_0

This activity is only needed for ABAP-based systems and for J2EE

systems based on SAP Netweaver 710 or higher

See the activity help for details on how to perform the activity

Click on Multiple Links to open the sub-activities

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 105 Public

Managed Systems Configuration Configure Manually

Restart JAVA Stack

Some activities during the automatic configuration require the restart of

the Java Stack

bull The adjustment of the JVM parameters

bull The deployment of the Wily Byte Code Agent

The restart can be scheduled during maintenance but until the restart

no JVM specific metrics (like Garbage Collection and Heap Size) are

reported to CA Introscope Enterprise Manager

Enable remote R3 Connection

To enable remote supportability for the managed system you need to

maintain the remote R3 connection for the system in Service Market

Place

Go to httpservicesapcomremoteconnection and click ldquoMaintain

Connectionsrdquo

Select the managed system and the R3 Support connection type

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices

copy 2013 SAP AG All rights reserved 106 Public

copy 2013 SAP AG All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG

The information contained herein may be changed without prior notice

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors

National product specifications may vary

These materials are provided by SAP AG and its affiliated companies (SAP Group) for informational purposes only without representation or

warranty of any kind and SAP Group shall not be liable for errors or omissions with respect to the materials The only warranties for SAP Group

products and services are those that are set forth in the express warranty statements accompanying such products and services if any Nothing

herein should be construed as constituting an additional warranty

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries

Please see httpwwwsapcomcorporate-enlegalcopyrightindexepxtrademark for additional trademark information and notices