1

If the Solution SAP Solution already exists, this step is deactivated.

It is highly recommended to use the standard SAP Solution Manager BW environment which sets
up the BW in the same client as SAP Solution Manager.
If you do not use client 001 as Solution Manager client make sure you set the BW client in table
RSADMINA to the current Solution Manager client.
This is done using the function module RS_MANDT_UNIQUE_SET. To check f the client was set
successfully please check the field BWMANDT in table RSADMINA. The BW can only be
activated in this client!
If you use another BW systems as SAP Solution Manager BW system, please ensure that the
software components BI_CONT and ST-BCO are always on exact the same level as Solution
Managers. Do never mix up your business BW with the SAP Solution Manager BW.

In this step users are created for the further Basic Configuration.
The following users are created:
The user SAPSUPPORT is the support user for E2E tools. Instead of creating the default
users and generating password you can also specify password or specify an existing user and
password. It is recommended to specify the password for the user SAPSUPPORT.
The SEP_WEBSERV user is a system user which is used for the BMC Appsight License
Check Service in the Internet Communication Framework (ICF).
The SMD_RFC user is user for RFC communication between the ABAP and Java stack of
SAP Solution Manager.
The user CONTENTSERV is the user for HTTP services like Webdynpro and BSP.
The SM_EFWK starts the program E2E_EFWK_RESOURCE_MGR in the background job
EFWK RESOURCE MANAGER. The program starts the Extractor Framework.
This SMD_BI_RFC user is created in the BW client of your SAP Solution Manager system and
used in the same way than the SMD_RFC user in your productive client.
The user BI_CALLBACK is created in the SAP Solution Manager client.
BI_CALLBACK is used only if the BW is on a different client or system and if the BW needs to
read data from the Solution Manager client.

10

11

12

13

In this step, you connect existing CA Wily Introscope Enterprise Managers to SAP Solution
Manager. This data is required for Solution Manager Diagnostics to analyze the status of Java
systems, e.g. performance data and to enable SAP Solution Manager to alert on errors in the
Java system.
You can install additional CA Wily Introscope Enterprise Managers, if the capacity of existing
ones would be exceeded.
The Wily Introscope Enterprise Manager has to be installed on operating system level of SAP
Solution Manager or on a separate host, before it can be added here.
The Enterprise Manager (EM) acts as the central repository for all Introscope performance data
and metrics collected in an application environment. The Enterprise Manager processes
performance data and makes it available to users for monitoring and diagnosis.
CA and SAP have an agreement allowing customers to use Introscope with SAP-developed
dashboards and instrumentation as part of SAP Solution Manager. If you would like to increase
the benefits of Introscope through custom dashboards and instrumentation, or extend
Introscope's capabilities with Introscope Powerpacks, those services and products are available
from CA's Wily Technology Division.
The Enterprise Manager should always run on the system, therefore please ensure that the
server comes up again if you restart your server.
The Wily Introscope installation guide can be found under http://service.sap.com/diagnostics

14

Optional Step:
You can allow SAP Solution Manager to access the permission table saprouttab on the
SAProuter server via FTP. In this case, you do not need to maintain the permission table
manually.
You can specify the automatic update of the table SAPRouter. The system then automatically
updates all required entries in the saprouttab when you open a service connection.
To do this a FTP server must run on the SAPRouter server, this FTP server is configured here.

15

16

Refer to the activity documentation of the single activities to find detailed information on how to
perform the activity. The activity documentation can be accessed via the link Display in the
column Documentation.

17

18

19

20

In this step you start a job that performs several automatic activities in your Solution Manager
system. If an activity fails please refer to the log to find out more about the error and how to fix it.
If you cannot carry out an activity automatically, please refer to the activity documentation on how
to perform the activity manually.
The following issues are observed at customers regularly and should be noticed here briefly:
Make sure your client is not set to client role Production in transaction SCC4, since this
makes it impossible to import piece lists
Make sure the BW activation was finished successfully before activating any content. This can
be done using transaction RSTCO_ADMIN in the BW client. If it failed feel free to rerun it
directly from there. The BI_TCO_ACTIVATION job usually needs around 1000 seconds in a
new installation.
Several different content areas are activated in this step. Nevertheless you can only run one
CCMS_BI_SETUP job at one time in an BW system. If a BW content related activity fails, wait
until the currently active CCMS_BI_SETUP job finished and rerun the activity (via Execute
Selected). Always check the job log of the CCMS_BI_SETUP jobs, since they tend to finish
successfully, despite errors in the job log.

21

22

Optional Step
In this step you can maintain users that are used in the further configuration for the different SAP
Solution Manager scenarios (e.g. ChaRM, BPMon etc.). The users are created with the
authorizations necessary to successfully perform the scenario configuration.

23

24

25

26

If you miss a managed system make sure it is visible in LMDB. If it is not visible in LMDB please
connect the system to the SLD to automatically create it in LMDB.
Please allow some time for the system to show up here, since it has to be replicated to this view,
via the landscape browser.

27

28

29

The right product version is very important for the setup of Root Cause Analysis. If you select
only a product versions for a system as diagnostics relevant that are not supported you will not
be able to finish the managed system setup successfully. Please make sure that at least one
product version selected as diagnostics relevant is supported as of SAP note 1478974.

30

Up to SAP Solution Manager 7.1 SP 04 product systems were maintained in Solution Manager
system landscape SMSY. With SP 05 this functionality moved to LMDB.
A technical system has to be assigned to a product system, to be able to continue with the
managed system setup successfully.
For more information on the purpose of product systems please refer to:
https://help.sap.com/saphelp_sm71_sp05/helpdata/en/2f/f0a5a230e54d62921a282622536916/fr
ameset.htm

31

32

The following RFC destinations can be created:

READ Destination: on Solution Manager to read system data from managed system to
enable basic SAP Solution Manager functions

TMW Destination: on Solution Manager, will be used for the Change Request Management
(ChaRM) functionality. You only need to create this one if you plan to use ChaRM.

RFC Destination for Solution Manager: TRUSTED or LOGIN RFC Destination to jump to
satellite system for analysis purposes. If a TRUSTED RFC destination is created, also a
TRUSTED RFC destination from the managed system to SAP Solution Manager is created

BACK Destination: on managed system to send data to Solution Manager (for EWA data,
Service Desk messages)

33

Make sure that you assign an appropriate Diagnostics agent for every single instance listed in the
table. If you dont assign an agent, you will loose of monitoring functionality for the affected
instance.
You can use the button Check Host Agents to check the SAP Hostagent installed in the host of
the Diagnostics agent. In case of a problem with the SAP Hostagent an error message will be
shown in the log area.

Remark: If you want to use diagnostics agents that are created by an diagnostics agent as
agents on-the-fly, please be aware that you have to set up and activate agents on-the-fly for the
physical/virtual host the SAP systems logical host is running on, before the managed system
setup. For the setup procedure please refer to the appendix of this document.

34

35

36

In this step you create users in the managed system, to enable the Diagnostics agent to gather
data and to provide a user for SAP Support.
The following users are created:
SAPSUPPORT: The user SAPSUPPORT enables Active Global Support to support in the
managed system. The user can only read data. Enter the password manually.
SMDAGENT_<SID>: The SMDAGENT_<SID> user is used by the Wily Host Agent
Application on the Diagnostics Agent to connect to managed systems of type ABAP for data
retrieval.
SMCOLL_<SID>: The SMCOLL_<SID> user is used by the Wily Host Agent Application on the
Diagnostics Agent to connect to managed systems of type Java for data retrieval.

37

In this step you start a job that performs several automatic activities in the managed system. If
an activity fails please refer to the log to find out more about the error and how to fix it.
If you cannot carry out an activity automatically, please refer to the activity documentation on how
to perform the activity manually.

38

39

40

41

42

In this step you have to create a logical component or assign your system to an existing logical
component.
Usually the customers have a three system landscape for there products. That means they have
one system of product version SAP ERP as development system, one as quality assurance
system and one as productive system. Even if the systems are physically separated they belong
together in a logical way building a development line.
This relation is modeled by a logical component. Logical components are necessary to be able to
use systems in project and solution and also for certain functionalities in SAP Solution Manager
like ChaRM and Business Process Monitoring.

43

44

After finishing the managed system setup for your system make sure that you add it to a
Solution, to activate Early Watch alerts!

45

46

For the diagnostics agent installed on the physical/virtual SAP recommends to use a freshly
installed Diagnostics Agent. It is not recommendable to try to re-use older/former existing agents
for the agents on-the-fly setup.
2

This will help you to determine where the agents on-the-fly are currently located (on which
physical/virtual host they are currently running)
Currently we do not provide a dedicated UI showing where the agents on the fly are
currently located, instead you can use the Agent Admin UI (see slide Identifying agents
on-the-fly in the Agent Administration of this document)
In the Agent Admin UI the on-the-fly agents are identified by <SID>/<Instance>/<logical
host name> so to identify on which physical host an agent on-the-fly is currently
running, it is recommendable to use different SIDs or instance numbers for all agents
participating in one switch-over group (the group of physical hosts between which one
managed component can switch)
Example:

47

Host type:
P = physical
V = virtual
L = logical
U = unknown (you may want to check the SAP Hostagent for this host)

48

49

50

51

52

53

54

55

56