1

2
3
4
5
SAP Solution Manager is configured using a guided procedure called SAP Solution Manager
Configuration. It is entered via the transaction code SOLMAN_SETUP.
In the SAP Solution Manager Configuration tool not only the basic configuration is performed,
also the standard configuration of all other SAP Solution Manager scenarios is performed using
this tool.
All steps of the wizard have an consistently design which makes it easier for you to navigate. On
the top of the wizard you find a roadmap telling you where you are in the basic configuration.
Every wizard page contains a help section, which is marked in orange on the slide. The help
section provides detailed information to each step, such as what needs to be done and what will
happen in the background.
The activities section, which is marked blue on the slide, lists all single activities during each step
along with the documentation for the activity. The documentation from the activity describes what
exactly has to be done, e.g. in manual steps and also provides error handling procedures. If you
have to provide input values for a step you will enter them in the activities section as well.
The Log section shows detailed logs for every activity that was performed.
The automatic basic configuration consists of three scenarios.
The first scenario is the System Preparation. In the System Preparation, you make further
settings which are prerequisite for the configuration of SAP Solution Manager. The System
Preparation has to be performed fully for new installed systems. If the Solution Manager was
upgraded you have to perform to update dialog and system users, and assign the appropriate
default roles and to implement the appropriate Central Correction Note (CCN)
The Basic Configuration configures the basic scenarios of SAP Solution Manager. These basic
scenarios are necessary for every customer and hence need to be setup in basic configuration.
The scenarios are the Service Delivery, the Issue Management, Early Watch Alerts, Root Cause
Analysis and the Maintenance Optimizer. It needs to be performed after a new installation and
after support packages to perform delta configuration.
The Managed Systems Configuration deals with the connection and configuration of the
managed systems. You have to perform this scenario for each managed system separately.

7
The basic configuration and the managed systems configuration assures that important basic
functionalities are set up in SAP Solution Manager.
Furthermore it provides the basis for all further configuration.
The diagram on the slide shows the dependencies between the single scenarios.
The scenarios in SOLMN_SETUP provide a guided standard customizing for most functionality in
SAP Solution Manager. You can perform further expert customizing using the SAP Reference
IMG accessible via transaction SPRO.
8
9
10
To start with the automatic basic configuration call transaction SOLMAN_SETUP from your
productive client. If you start the SOLMAN_SETUP for the first time, you will be asked to activate
Web Dynpro Services to display the wizard in your browser screen. Confirm the popup. Because
the first load of the Web Dynpros may take some time you also could get a connection timeout. If
this happens please adjust the connection settings for the HTTP service in transaction SMICM.
The first screen you see after opening SOLMAN_SETUP is the Overview screen.
The overview shows the status of the SAP Solution Manager configuration. It tells you which
steps of the configuration have been performed when and by whom and which steps of the
configuration needs an update.
You can see the status of every configuration scenario or configuration step in the overview
screen. The following statuses of configuration scenarios or configuration steps require you to
take action:
Activity Not Yet Performed (Gray): Perform the configuration scenario or configuration step.
Performed With Error/Activity Errors (Red): Repeat the configuration scenario or configuration
step.
Performed With Warning (Yellow): Repeat the configuration scenario or configuration step, if
necessary.
If the field Updates Needed is selected, repeat the configuration step. This may be
necessary if, for example, a Support Package was installed after SAP Solution Manager was
configured.

11
12
13
14
The S-user is a user for the customer to access the SAP Service Market Place. It is used by the SAP customer in
the following scenarios:
Exchange problem messages with SAP
Synchronize system data with Support Portal and send data about satellite systems
Service connection
Retrieve information about which messages have been changed at SAP
To send an up-to-date version of the component ST-SER for delivery of services by SAP Active Global
Support
Get some user documentation from SAP Market Place used by the Help Center within Diagnostics
SAP Solution Manager performs some of this activities automatically, e.g. the synchronization of support
messages and system data between Solution Manager and the support portal and the request of maintenance
certificates. It is also possible to open a service connection via Solution Manager and to send service messages
to SAP Support directly from Solution Manager Service Desk.
For security reasons it is recommended to maintain two S-Users for Solution Manager. One for the backend
connection. The S-user is needed to access SAP-internal systems via RFC destinations such as SAP-OSS and
SAP-OSS-LIST-O01. The S-user entered in these RFC - connections requires a password and has to be
assigned to your customer number. For security reasons it should have no authorizations since it could be
misused for direct logon.
The other S-User is needed to perform tasks like synchronize service messages and system data and to request
licenses. This S-user is used by the Solution Manager batch user and the Solution Manager administrator user
(these will be created later on) and assigned to this users in transaction AISUSER. This user needs more
extensive authorizations.
Also S-users belonging to named users in Solution Manager are assigned to this users in transaction AISUSER.
Which authorizations are needed for this S-users depends on the tasks the person performs. For information
please refer to the SAP Solution Manager security guide:
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000735220&_OBJECT=011000358700000482
312011E
15
To make sure the managed systems can be managed properly please check if the support
package levels of the Solution Manager and the satellite systems are up-to-date according to
SAP note 1274287.
To manage a satellite system with Solution Manager you need to apply two add-ons to the ABAP
stack of the satellite system.
One is the add-on Solution Tools Plug-in ST-PI. The Solution Tools Plug-In provides Basis
and Trace Tools required for service delivery and system monitoring. It contains the latest
version of: the Function modules for data collection, the Transaction SDCCN, Application
Specific Upgrade ASU-Toolbox and the Custom Development Management Cockpit (CDMC).
The other add-on is the Service Tools for Applications Plug-In (ST-A/PI). It contains the latest
versions of: transaction ST14 (the application monitor), Application Monitoring Infrastructure
for Business Process Monitoring, the Report RTCCTOOL (the Servicetools Update),
Transaction ST12 (the ABAP trace for EarlyWatch/GoingLive), Transaction ST13 (the
Launchpad for further analysis tools), new SDCC data collectors for BW APO CRM and
databases and collectors for E2E change management.

As of SAP Solution Manager 7.1 all data on the managed landscape like systems, hosts,
databases etc. is stored in the Landscape Management Database (LMDB). The LMDB works on
the similar data model (the CIM model) like the System Landscape Directory (SLD) but is
implemented in the Solution Manager ABAP stack. All managed systems must be
registered/known in the SLD. The landscape data is then synchronized from the SLD to the
LMDB by a batch job. A direct registration of systems in the LMDB is not possible.
To perform the synchronization successfully and to make sure that all data is up-to-date and
complete the SLD which is synchronized with the LMDB needs to have a certain CIM model
version and a certain CR content support package.
SAP recommends to run one central SLD that contains all systems belonging to your landscape.
This is also the SLD to be synchronized with the LMDB. It is not necessary to run a local SLD on
Solution Manager anymore, even though its possible. As some other products like PI, NWDI etc.
need a running SLD to function correctly you have to make sure, that these systems have their
own SLDs. If you run more than one SLD in your landscape you can use SLD bridging to keep
the technical system data in the SLD synchronized.
For more information on how to plan your SLD landscape see the SLD planning guide under
https://www.sdn.sap.com/irj/sdn/nw-sld -> Setting Up a System Landscape Directory -> Planning
Guide - System Landscape Directory

* For details on the supported SLD versions see:
https://help.sap.com/saphelp_sm71_sp05/helpdata/en/a5/971735dd184f5c8d943c6cf423d13a/fra
meset.htm
16
17
SAP Solution Manager needs a working RFC destination to the SAP support backbone. The RFC
destination SAPOSS allows you the log on to the SAP online service system from the SAP
Solution Manager. Additionally SAPOSS is the used as the copy master for other RFC
destinations in Solution Manager.
To check if the RFC destination is working properly call transaction SM59, expand the sub tree
for the ABAP connections and double-click on the SAPOSS RFC destination. Use Utilities Test
Authorization Test to test if the RFC destination is working. If the test is not successful you
need to adjust the RFC destination.
This is done in the transaction OSS1. Here you can check and maintain the connection settings
of SAPOSS. The configuration changes will be adapted automatically. To maintain the values for
the SAP routers at customer side please contact your local SAP administrator. Depending on
your location you will have to use different entries for the entry SAP router at SAP. Enter the
server name for your location or select SAProuter at SAP from the menu, and choose the
appropriate location. You can find detailed information on SAPOSS and error handling
procedures in SAP note 17285 in the SAP service market place.
18
* With Solution Manager 7.1 SP 05 a new agent on-the-fly feature was introduced.
Functionality
For standard diagnostics agent installed on a physical or virtual host, you can activate the
agents on-the-fly functionality. These agents can then start and stop agent instances
dynamically for logical hosts running on the physical or virtual host.
If a logical host moves from physical host A to physical host B, the diagnostics agent installed on
the physical host A stops the agent instance (agent on-the-fly) for the logical host on host A and
then the diagnostics agent installed on host B starts up an agent on-the-fly for this logical host on
host B.
With this approach, one diagnostics agent can manage several logical hosts running on the same
physical or virtual host. This decreases the installation effort and the resources required for
diagnostics agents remarkably.
More information on diagnostics agent installations will follow in sections System Preparation
and in the Appendix of this document.
Please also refer to SAP note 1365123.
19
While Wily Introscope Enterprise Manager was a pure expert monitoring tool for Root Cause
Analysis with SAP Solution Manager 7.0, now its role became more important.
As of SAP Solution Manager 7.1 Wily Introscope Enterprise Manager additionally pushes metrics
to SAP Solution Manager which are then used for monitoring and alerting in the new Monitoring
and Alerting Infrastructure (MAI).
Hence it is mandatory to install and run Wily Introscope EM to use the Technical Monitoring
functionality in SAP Solution Manager 7.1.
20
21
Optional Step
SAP delivers a standard Solution Manager configuration in clients 000 and 001. You can use
client 001 as productive client, but if necessary you can also create a new productive client.
To create a new client please perform a client copy with profile SAP_ALL from 001 and use 001
as the source client for users. Information on how to create a new client can be found in the SAP
reference IMG in the cross-scenario settings under client copy.
After the creation of the new productive client you have to make sure that the Java UME uses the
user store of the new client. Otherwise newly created users in the ABAP system will not be able
to log on to the java stack even if they have the appropriate authorization. This is because they
are not known to the java stack which uses the wrong user store.
Please ensure that you entered 001 as Source Client User Masters for your client copy. Without
the standard Java users from 001, e.g. the user SAPJSF, the Java engine will not start after
converting UME.
To convert the UME log on the java stack using the URL
http://<solmanhost>:<solmanport>/useradmin . Change to Configuration, switch to the tab
ABAP System and set the Client property to your new productive client.
You have to restart the Java stack to make the changes take effect.

22
During the basic configuration and the managed system setup several technical and
administrative users are created by SOLMAN_SETUP.
As of SAP Solution Manager 7.1 the usage of a Central User Administration (CUA) for user
management is fully supported with SOLMAN_SETUP. To enable CUA to work with
SOLMAN_SETUP you have to assign some specific authorizations to your CUA_ADM user,
which is usually used in the RFC destination from the managed system to CUA.
The SAP Solution Manager Security Guide
(http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000735220&_OBJECT=01100
0358700000482312011E ) describes possible CUA scenarios and how they are set up.
If you dont want SOLMAN_SETUP to create users in your landscape or you use another external
user management system you can also create or maintain the required users manually and
provide them to SOLMAN_SETUP during the setup step.
The user creation steps of SOLMAN_SETUP provide documentation which users are needed
and which role have to be assigned. You can also refer to the SAP Solution Manager Security
Guide for more details.


23
24
In the first step you have to create or update dialog and system users, and assign the appropriate
default roles. During this process, the system automatically creates users, generates the needed roles
using authorization templates and assigns the roles to the created users.
The first user you have to create is an Solution Manager administration user. The default name for
the user is SOLMAN_ADMIN. If an administrative user already exists you can use that user and
update the authorizations of the existing user automatically or manually.
The second user is the user SMD_ADMIN. This user is used by the Solution Manager Diagnostics
agents to connect to SAP Solution Manager. This user is very important. Please remember its
password, because you will need it during the agent installation, to assign the agent to SAP Solution
Manager.
The third user is the user SOLMAN_BTC. This user is used to run all Solution Manager and system
standard jobs. You will never need the password of this user, hence for security reasons it is
generated. If you urgently need it, e.g. for company policy reasons you can change it to a password
of your choice using the Update Password option later on.
The SM_EXTERN_WS user is used for external web services communication between Diagnostics
Agents and SAP Solution Manager.
The SM_INTERN_WS user is used for internal web services communication between the ABAP
and Java stack of SAP Solution Manager.

All user names can be adjusted to meet your companies naming conventions.
To make sure that the credentials of a system user are correct, choose the Test Login pushbutton in
the last row of the user table.
25
In the next step an installation check is performed for configuration-relevant parts of the installation. The
installation check runs the following checks
1. Check Transport Management System (TMS) configuration. If the check TMS configuration is not successful,
the Transport Management System is not yet configured and you should configure a transport domain
controller for the Solution Manager system. To do this call transaction STMS in client 000. In addition the
production system and the development system must be in the same transport domain. If they are in two
different transport domains there must be a domain link between them, so that the export history from the
development system can be seen from the production system.
For more information on how to configure the transport management system, please refer to SAP Help
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/44/b4a09a7acc11d1899e0000e829fbbd/frameset.htm
2. Check profile parameters. In this check it is checked if certain profile parameters meet the requirements. See
SAP note 1582842 for details.
3. Check license key. This check verifies if a valid license is installed in the Solution Manager. If this check fails
request a license key for Solution Manager in SAP Service Market Place and apply it using the transaction
SLICENSE.
4. Check Software Prerequisites. This activity checks if the Solution Manager System satisfies all the
prerequisites for End-to-End Diagnostics. Depending on the version of SAP Solution Manager and the
version of the managed system, a minimum version for different software components and the corresponding
correction notes are required. Go to SAP Note 1483508 and select the attached note relevant for your SP
level of SAP Solution Manager.
5. Check system landscape parameters. This activity checks if the value Synchronize is set for the Cross-
System Synchronization Settings field in SMSY. This setting allows the corresponding system data
maintained in Solution Manager to be synchronized with SAP Support Portal.
6. Check service connection to SAP. Here is checked if the RFC SAPOSS works and the distribution group is
set to EWA
If a check status turns red, check the IMG 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 the execution status to
Postpone or Manual to run only the checks that turned red during the last run.
26
In the third step, you have to download and implement the central correction note (CCN). The
CCN contains all important corrections notes currently created for Solution Manager.
The CCN has to be implemented manually using the transaction SNOTE. Read the CCN
carefully BEFORE implementing it, to make sure that you do not miss any manual steps. The
notes with manual steps are listed in section two of the CCN. It can also be manual preparation
steps, so dont miss to check these notes first. If these notes contain an x in the column auto the
manual steps can be performed automatically in the third sub step of this step.

27
28
The reason why you need a Web Dispatcher if you run more than one instance are the several
Web Service calls that are made between:
a) Solution Manager ABAP Solution Manager Java stack
b) Diagnostics Agent Solution Manager ABAP stack
These calls must be load balanced (especially b))
Before Solution Manager 7.1 SP 03 the Message Server was used for this load balancing, but
since SP03 the HTTP redirect, which was used by the Message Server is forbidden/prohibited.
Therefore the Message Server cannot be used anymore.
Instead you have to install/use a Web Dispatcher, which is doing HTTP forwards (to the various
Solution Manager instances).
With Solution Manager 7.1 SP 06 you also can find additional information and useful hints on
what to consider when configuring HTTPS in the step help area.

* For more information on how to configure a web dispatcher please refer to:
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/48/6a82a684f4350ce10000000a42189d/fra
meset.htm

29
The activation of authentication types is a security relevant step and hence to be performed
explicitly and manually by the customer.
30
31
* This tab will only contain agents that connected at least once to SAP Solution Manager after the
update to SP 05 (and therefore received the updated agent applications)
The authentication change will not affect agents that didnt connect to Solution Manager (offline
agents) anymore, e.g. due to invalid credentials. These agents need to be restarted and if
necessary the agent credentials have to be corrected using the smdsetup script on OS level.


32
33
In this step you connect one or more SLD to SAP Solution Manager and you set up the data
supplier target for Solution Manager itself, to register it in an existing SLD.
If you want to use the local SLD of SAP Solution Manager you can set it up here.
You should connect all SLDs that contain diagnostics agents for this Solution Manager.
Please see the step help of this step for further details.
34
A system landscape description is required by different SAP Solution Manager applications, like
Monitoring and Alerting, diagnostics, and for calculations of updates and upgrades with the
Maintenance Optimizer.
SAP Solution Manager collects and stores detailed information like about the entire system
landscape, for example:
technical system information
logical information, for example about product systems and information about the usage and
the relation between technical systems and the software installed on these systems
This information is mostly based on the software descriptions as provided by the SAP software
catalog (CR content) and on the information that is automatically sent by technical systems via
the System Landscape Directory (SLD).
The Landscape Management Database (LMDB) of SAP Solution Manager is the central
landscape information repository. The LMDB uses the same standard (the Common Information
Model, CIM) as the SLD to represent system information.
In this step, you can add and change synchronization connections to SLD. A synchronization
connection is defined between the LMDB CIM target namespace (active) and the SLD CIM
source namespace (default: sld/active).
You can synchronize more than one SLD with the LMDB but please consider the following points:
Make sure the different SLD do not contain duplicate or redundant data, since this leads to
inconsistencies and overwrites
The different sync operations are performed sequentially, this can lead to high workload and
long running jobs in Solution Manager


35
Please refer to the SAP Help for more details on setting up the connection between LMDB and
SLD:
https://help.sap.com/saphelp_sm71_sp05/helpdata/en/a5/971735dd184f5c8d943c6cf423d13a/fra
meset.htm
Connecting to Several SLDs
The unique-path-principle for data must be fulfilled when the LMDB is synchronized with more
than one SLD system. System landscape descriptions are always imported from all connected
SLDs. Therefore, they must not overlap. This can only be ensured if SLD systems connected to
the LMDB run in separated landscapes.
36
You can activate and deactivate a connection. The very first activation starts an initial, full,
automatic synchronization to import all SLD system information to the LMDB, which takes
several hours (usually 4 12 hours). If you experience performance issues please refer to SAP
note 1555955.
After this, incremental synchronization imports new changes every 10 minutes.
A rank defines how to proceed in case of conflicting changes. If the same data record is found in
both repositories but with different versions, the system with the higher rank wins. The LMDB
rank must be higher than the SLD rank to protect manual changes in the LMDB from being
overwritten by the SLD. For the LMDB sync the higher rank means, if a data record differs
between SLD and LMDB the data record is not overwritten by SLD.
37
You can also configure an additional SLD change notification to propagate SLD content changes.
In this case the SLD actively notifies the LMDB of changes. To do this you SLD must meet a
certain minimum release, please refer to SAP note 1546079 for details.
If more than one SLD is synchronized with the LMDB 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 same SLD will provide the CIM model to be
used by the LMDB.
We recommend that you enter this SLD first, because the first synchronization connection is
automatically selected as CR source.
38
Migrate Technical Systems from SMSY (only to be used in exceptional cases)
With this function, you can migrate complete descriptions of selected technical systems. This
synchronization is called System-Oriented Migration. This can be required for systems that
were manually created in transaction SMSY in earlier in SAP Solution Manager releases.
Avoid system-oriented migration: Only migrate systems for which you cannot configure data
suppliers, for example because of a firewall. Automatically supplied data is usually more reliable
than manually created data. Furthermore, data suppliers ensure that changes in a technical
system are reflected in SLD and LMDB automatically.

With the next work step, Migrate Data into LMDB, you can migrate system landscape information
that had to be manually defined in SMSY in earlier releases and that cannot be provided by an
SLD, such as product system information and custom attributes. (Aspect-Oriented Migration)

** This step is only valid for upgraded system, since a new installed system should not contain
manual data in SMSY. As on Solution Manager 7.1 you cannot delete/edit system in SMSY,
hence they need to be migrated to be used further or created in LMDB manually.
For more information on migrating data from SMSY to LMDB please refer to:
https://help.sap.com/saphelp_sm71_sp05/helpdata/en/e7/101fc81c0642df8c75b0e15111b2a4/fra
meset.htm

39
The Landscape Management Database (LMDB) is the central storage for system landscape
information in the SAP Solution Manager. Most of the LMDB content is provided by a System
Landscape Directory (SLD). Until SAP Solution Manager 7.0, the SAP Solution Manager System
Landscape (SMSY) was the central storage of landscape information.
In this step, you can migrate system landscape information that was defined in SMSY in earlier
releases and that cannot be provided by an SLD. This migration is called Aspect-Oriented
Migration is necessary after an update or upgrade from SAP Solution Manager below 7.1 SP
04 to avoid manual recreation.
Especially product system migration is strongly recommended.

40
In this step several automatic activities are performed:
Create logical System: This activity creates a logical system entry for the current SAP Solution
Manager client.
Update RFC: This activity ensures that at least one RFC destination (type READ) is
maintained in table SCDTSYSRFC (contains information on READ, TMW and
TRUSTED/LOGIN RFCs to managed systems).
Activate SDCCN: This activity activates the Service Data Control Center (SDCCN) in the
managing system.
Turn Off maintenance mode: Before an Update or Upgrade of SAP Solution Manager, the
maintenance mode of SAP Solution Manager must be switched on. After the process is
finished the maintenance mode must be switched back to off so that the Diagnostics agents
can be used again.
Read LMDB: This activity is scheduling a job that reads the LMDB and writes the changes into
the Solution Manager System Landscape (transaction SMSY). This job will be scheduled daily.
Remark: As SAP Solution Manager is not flagged as diagnostics relevant automatically anymore
with SP 05, please check the diagnostics relevant status for SAP Solution Manager in LMDB
(transaction LMDB) and make sure it is set to Diagnostics Relevant. This flag is necessary to
make sure that e.g. all extractors can be scheduled successfully during basic configuration.

41
SAP Solution Manager uses different agents for monitoring. In this step you install these agents
and make sure that they communicate with each other.
The following slides provide details regarding SAP Hostagents and Diagnostics agents.
Some assumptions are made regarding the naming of different host types.
A physical host and a virtual host are hosts that are the actual hardware or a virtual machine on
which the OS is running (SAP system can be installed with physical host names).
A logical host is an additional hostname, that runs on a box with a physical hostname. This
hostname is usually assigned to an SAP component and can move from one physical/virtual host
to another.

42
SAP Hostagent is installed per default under /usr/sap/hostctrl on Unix-based operating systems
and under C:\Program Files\SAP\hostctrl on Windows operating system.
Some programs of SAP Hostagent run under user root (Unix) or under the Local System Account
(Windows). This is necessary to enable the collection of e.g. operating system relevant data with
SAPOScol.
To enable the Diagnostics Agent to gather this information from SAP Hostagent, the OS user of
the Diagnostics Agent has to be added as service user to the host_profile file of SAP Hostagent.
The examples above show how such host_profile file should look like (under the assumption that
the Diagnostics agent is installed with the SID DAA)
43

44
With SAP Solution Manager 7.1 SP 05 a new functionality was added to Diagnostics agent.
Addressing the growing need of more flexible agents in the growing and more complex and
virtualized environments of our customers, the agents on-the-fly concept was introduced.
This allows immense saving regarding installation effort in landscapes with several logical
hostnames on one physical host and switchover environments. The agent on-the-fly concept is
based on a normal diagnostics agent installed on a physical or virtual host. After activating the
agents on-the-fly functionality this agent can start and stop agent on-the-fly instances
dynamically for logical hosts running on the physical or virtual host.
If a logical host moves from physical host A to physical host B, the diagnostics agent installed on
the physical host A stops the agent instance (agent on-the-fly) for the logical host on host A and
then the diagnostics agent installed on host B starts up an agent on-the-fly for this logical host on
host B.
45
46
47
48
49