CONFIGURATION GUIDE | PUBLIC

Document Version: SPS 11 – 2020-05-11

Configuration Guide - SAP Solution Manager 7.2

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

THE BEST RUN

Content

1 Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Adjusting Roles and Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

4 Checklist for a Newly Installed System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

5 Prerequisites for the Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

6 Configuring SAP Solution Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

7 Executing the Configuration Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

8 Using SAP Solution Manager as a Service Provider. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Configuration Guide - SAP Solution Manager 7.2

2 PUBLIC Content
1 Document History

The following table provides an overview of the most important document changes.

Version Date Description

5.0 2020-01-30 Updated information about user creation in Prerequisites for

the Configuration [page 8].

4.0 2019-12-01 Included information on Using SAP Solution Manager as a

Service Provider [page 12]. Information about the ABAP task
list SAP_SUPPORT_HUB_CONFIG has been updated in Check­
list for a Newly Installed System [page 7].

3.0 2019-07-01 Guide was restructured. New information added on adjusting

roles and profiles as well as prerequisites for the configuration.
A checklist for a newly installed system was also added. Links
to information about the update of the support backbone have
been added. As a result of the update, you need to ensure that
your systems can continue to communicate with the support
backbone after the legacy infrastructure is retired in January
2020.

2.0 2018-12-06 No changes

1.1 2017-05-08 Guide is now relevant for all support package stacks of SAP
Solution Manager 7.2. Therefore only one guide is available.

1.01 2016-09-20 CA Introscope Enterprise Manager version corrected. The ver­

sion relevant for SAP Solution Manager 7.2 SP03 is 9.7 SP01 or
higher.

1.0 2016-08-15 Initial version

Configuration Guide - SAP Solution Manager 7.2

Document History PUBLIC 3
2 Introduction

Use

This guide gives an introduction to the SAP Solution Manager Configuration application (transaction
SOLMAN_SETUP) and provides general configuration information for SAP Solution Manager 7.2. The guide is
updated regularly on the SAP Help Portal at: https://help.sap.com/viewer/p/SAP_Solution_Manager.

 Note

For configuration information on SAP Fiori for SAP Solution Manager, see the SAP Fiori for SAP Solution
Manager configuration guide.

The extent to which you can use the SAP Solution Manager software depends upon the type of maintenance
contract you have. For information about the usage rights, see https://support.sap.com/usagerights .

Prerequisites

Before you start with the configuration, read the Master Guide. If you need to upgrade from SAP Solution
Manager 7.1 to 7.2, focus on the Upgrade Guide.

Configuration Guide - SAP Solution Manager 7.2

4 PUBLIC Introduction
3 Adjusting Roles and Profiles

SAP delivers predefined roles with default values. If these values are missing, you need to set them manually in
the authorization objects.

 Note

This procedure does not apply to the roles that you maintain in SAP Solution Manager Configuration
(transaction SOLMAN_SETUP).

Procedure

To manually adjust roles, proceed as follows:

1. Load the roles and profiles from client 000 into your target client.
You have the following options for this step:
○ Transport the roles and profiles from client 000 into your target client
○ In client 000, download the roles and profiles in the Role Maintenance (transaction PFCG), and upload
them in your target client.
2. Copy the roles and profiles to your namespace.
1. Start the Role Maintenance with transaction PFCG.
2. Enter a role name and choose Copy Role.
3. In the To Role field, enter a new name for the role.
4. Choose Copy All.
5. Save your entries.
3. Complete missing values in the authorization objects.
1. On the Authorizations tab, choose Change Authorization Data.
2. Enter your own values for the authorization objects.

 Note

To grant full authorization (value *) for a particular field, double-click the yellow traffic light icon.

3. Save your entries.

4. Generate the authorization profile.
4. Assign the role to users.
1. On the User tab, enter the user names to which you want to assign the role.
2. Choose User Comparison.
3. To save your entries, choose Complete Comparison.

 Note

You can also assign roles to users in the User Maintenance (transaction SU01).

Configuration Guide - SAP Solution Manager 7.2

Adjusting Roles and Profiles PUBLIC 5
More Information

For information on how to create users and roles automatically, see Secure Configuration Security Guide at
https://help.sap.com/viewer/product/SAP_Solution_Manager/.

Configuration Guide - SAP Solution Manager 7.2

6 PUBLIC Adjusting Roles and Profiles
4 Checklist for a Newly Installed System

If you have created a system from scratch, make sure to prepare the following, before you start the
configuration:

● You have created two S-users in SAP Support Portal:

○ S-user to be assigned to the relevant SAP Solution Manager user
Dialog user entered in table AISUSER. For information, see the Secure Configuration Security Guide,
select the version, and search for S-User for Communication in Transaction AISUSER.
○ Technical communication user
System user. For information, see SAP Note 2174416 and the Secure Configuration Security Guide,
select the version, and search for Technical Communication User.
Customers need an S-user to access SAP Support Portal. For more information about S-users, see http://
support.sap.com/user-admin .
● The component repository of the system landscape directory (SLD) and the CIM model are up-to-date (see
SAP Note 669669 ).
● The RFC destinations are correctly maintained. For more information, see the Support Backbone Update
Guide, and search for Connection to SAP's Support Backbone.
● You have installed CA Introscope Enterprise Manager 9.7 SP01 or higher (see SAP Note 797147 )
● Make sure that a Diagnostics Agent is installed on each associate host (see SAP Note 1833501 ).
● Perform an initial setup and configuration, for example, post-installation activities, kernel patches, and the
SSL configuration. During this process, you must execute the predefined ABAP task list
SAP_SUPPORT_HUB_CONFIG using transaction STC01.

 Note

If you create your SAP Solution Manager 7.2 system with SPS 8, 9, or 10, running the
SAP_SUPPORT_HUB_CONFIG task list creates the HTTP destination SAP-SUPPORT_PARCELBOX. For
more information about the parcel box, see SAP Knowledge Base Article 2716729 .

If you create your SAP Solution Manager 7.2 system with SPS 9 or 10, running the
SAP_SUPPORT_HUB_CONFIG task list creates the HTTP destination SAP-SUPPORT_NOTE_DOWNLOAD.

● Configure SAP NetWeaver download service and configure Note Assistant to use SAP NetWeaver
download service. Follow the instructions in SAP Note 2554853 .
● Optional: Create a new productive client for the SAP Solution Manager ABAP system.
Perform a client copy with the SAP_CUST or SAP_UCSV profile from client 000. Use client 001 as the source
client for users. For more information about the profiles, see https://help.sap.com/viewer/product/
SAP_NETWEAVER_740 and search for Copy Profiles.
● For additional steps that you need to perform before you start with the configuration, see the Support
Backbone Update Guide.

Configuration Guide - SAP Solution Manager 7.2

Checklist for a Newly Installed System PUBLIC 7
5 Prerequisites for the Configuration

Before you configure SAP Solution Manager after an installation, upgrade, or import of a new support package
stack, make sure that you have prepared the following.

Prerequisites

● SAP Solution Manager and the license key are installed.

● Transport Management System (TMS) has been configured.
● You have started the load generator (transaction SGEN) for the following components to increase the
performance of your systems:
○ ST
○ SAP_BASIS
○ SAP_ABA
If you intend to run BW on your SAP Solution Manager system, you need to select the following
components as well:
○ ST-BCO
○ ST-PI
● You have a dialog user that is authorized for the configuration (transaction SOLMAN_SETUP).
● You have checked the Secure Configuation Security Guide at https://help.sap.com/viewer/product/
SAP_Solution_Manager/.

Creating Users

The first user creates the users for configuration. To do that, open transaction USR_MNGT and choose the Users
for Configuration tab.

You can create or edit one or several configuration users to perform the different scenarios.

To perform mass user creation or role updates for users, you can use Configuration User Management (choose
the link under Related Links).

Configuration Guide - SAP Solution Manager 7.2

8 PUBLIC Prerequisites for the Configuration
6 Configuring SAP Solution Manager

SAP Solution Manager Configuration (SOLMAN_SETUP transaction) guides you through the configuration of SAP
Solution Manager and assists you in connecting your managed systems to SAP Solution Manager. Its
configuration scenarios provide a standard customizing for most of the important basic functions in SAP
Solution Manager.

SAP Solution Manager Configuration is based on a guided procedure framework, which provides steps and
substeps with automatic and manual activities:

Navigation Overview of SAP Solution Manager Configuration

Follow the instructions in the guided procedures and in the on-screen help.

 Note

The guided procedures provide a separate log for each individual step.

Configuration Guide - SAP Solution Manager 7.2

Configuring SAP Solution Manager PUBLIC 9
7 Executing the Configuration Scenarios

The Mandatory Configuration and the Managed Systems Configuration scenarios build the foundation of further
configuration settings.

Mandatory scenarios
For new installations or upgrades, execute at least the following scenarios:

● System Preparation
If you have installed a new SAP Solution Manager system, you need to perform all steps of this guided
procedure, for example, define system roles and check prerequisites. If you have updated the SAP Solution
Manager system from SAP Solution Manager 7.1 to SAP Solution Manager 7.2, perform any open step in
this guided procedure. It may also be sufficient that you need to make some adjustments for the technical
users only.
● Infrastructure Preparation
In this guided procedure, you perform several steps, for example, configuring the System Landscape
Directory (SLD) and the landscape management database (LMDB) synchronization, as well as setting up
BW.
● Basic Configuration
Configure the most important functions, jobs, and users, for example, for root cause analysis and service
delivery.
● Managed Systems Configuration
In this scenario, you create all necessary connections to or from your managed systems. You need to
perform these steps for each managed system. After having executed the relevant steps, you can use
several functions for the managed systems, such as root cause analysis and SAP EarlyWatch Alert (which
SAP strongly recommends), as well as system and application monitoring.

 Note

Authorizations for SAP Solution Manager RFC users:

If you have implemented a scenario that uses READ RFC or TMW RFC and you experience authorization
problems, see SAP Note 1830640 .

Optional scenarios
Depending on your implementation, you can then configure other relevant scenarios, for example,
Requirements Management, Project Management, or Test Suite

Process

1. Start transaction SOLMAN_SETUP. If the SAP Solution Manager launchpad is already set up, open the
Configuration - All Scenarios application.
2. Select a scenario to open a guided procedure with the configuration steps. Each step contains a help tray,
one or more activities, and a log section at the bottom.

Configuration Guide - SAP Solution Manager 7.2

10 PUBLIC Executing the Configuration Scenarios
 In some steps, you can switch between standard mode and advanced mode. Some features are only
available in advanced mode.
Expand the help tray to display the help text.
3. Navigate through all steps of a scenario and perform the activities.
There are automatic or manual activities. For automatic activities, you select the activities you want to
perform and the system executes them without requiring more input from you. For manual activities, you
perform the configuration yourself according to the documentation provided in the Documentation
column.
An activity is either optional or mandatory, which affects status calculation. For more information, see
Status Calculation below.
When you install an upgrade or import a service package, the system automatically determines which
parts of the installation have to be reconfigured. If an activity needs to be performed again, the Updates
Needed check box is selected.
4. The Complete step of a scenario provides an overview of the activities performed in the scenario. You
choose Finish to save the settings and close the scenario.
To have the activity and status information and the help texts of all steps of a guided procedure in one
document, you can download them: In the Complete step, choose Export to HTML.

Status Calculation
● The status of steps and substeps is displayed by icons in the roadmap. The status is calculated based on
the activities belonging to the step as follows:
The status of mandatory activities affects the status calculation of the step, whereas the status of optional
activities does not.
In some cases, no status is displayed for a step, for example, if it is not relevant for the configuration.
A yellow status symbol with an exclamation point indicates that activities have to be repeated due to
changes to the system. The affected activities are marked in the Updates Needed column.
● The status of the activities is displayed by icons in the Status column.
Red icons are errors that must be resolved. See the log section for details.

 Recommendation

You can archive the SAP Solution Manger Configuration log. In SAP Solution Manager Configuration
Administration (transaction solman_setup_admin), choose Archive Administration, set up and display the
log for a selected scenario and step.

Configuration Guide - SAP Solution Manager 7.2

Executing the Configuration Scenarios PUBLIC 11
8 Using SAP Solution Manager as a Service
Provider

As a service provider, you provide services to your customers or subsidiaries using SAP Solution Manager. The
service-provider scenario extends the standard scenario setup for specific customer contexts, for example
special data separation and master data import.

If you use your SAP Solution Manager application for one of the above mentioned contexts, you can use it as a
service provider scenario. For this purpose, you also need to add some additional configuration and specific
authorizations for you, as the service provider, and your customers or subsidiaries.

Information on the service provider scenario and definition:

● Configuration guide for service providers and channel partners: https://help.sap.com/doc/

05b89f2beef041999b0678ace9e7e8f8/latest/en-US/SolMan72_partner_guide.pdf
● https://support.sap.com/solution-manager/partners/sp.html

Configuration Guide - SAP Solution Manager 7.2

12 PUBLIC Using SAP Solution Manager as a Service Provider
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Configuration Guide - SAP Solution Manager 7.2

Important Disclaimers and Legal Information PUBLIC 13
www.sap.com/contactsap

© 2020 SAP SE or an SAP affiliate company. 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 SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company 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
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN