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 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=011000358700000482312011E

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 it’s 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 node concept was introduced.

Functionality

The agent node controller is a normal diagnostics agent installed on a physical or virtual host.

After activating the “agents on-the-fly” functionality these agents can 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 host A agent node controller

stops the agent instance for the logical host on host A and the host B agent node controller starts

up an instance for the logical host on host B.

With this approach, one diagnostics agent node controller 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

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 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 don’t 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 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.

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 don’t 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).

* 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

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.

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, e.g. as

alias. 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 node 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 node concept is based

on a so called agent node controller. The agent node controller is a normal diagnostics agent

installed on a physical or virtual host. After activating the “agents on-the-fly” functionality these

agent can 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 host A agent node controller

stops the agent instance for the logical host on host A and the host B agent node controller starts

up an instance for the logical host on host B.

With this approach, one diagnostics agent node controllers can dynamically manage several

logical hosts running on the same physical or virtual host.

45

46

In general you can use every agent version with SAP Solution Manager 7.1 SP 05. It is not

necessary to upgrade older agent version.

The agent applications and the agent core, which provide the agent functionality are updated

centrally from SAP Solution Manager together with the support package installation of the Java

component LMSERVICES.

You can use any agent to manage any system release. This means you could e.g. use an agent

of version 7.30 SP 02 to manage your SAP ERP system of release SAP Netweaver 7.0.

Nevertheless for any new installations of Diagnostics agent it is highly recommended to use the

newest available version. This is currently version 7.30 SP 02. You don’t have to worry about the

Java version or the kernel version of your managed SAP system. The Diagnostics agent includes

its own SAPJVM and it’s own kernel directory.

47

48

49

50

51

52

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

53

54

55

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

Manager’s. Do never mix up your business BW with the SAP Solution Manager BW.

56

57

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.

58

59

60

61

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

62

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.

63

64

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.

65

66

67

68

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.

69

70

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.

71

72

73

74

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.

75

76

77

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.

78

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

79

80

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)

81

Make sure that you assign an appropriate Diagnostics agent for every single instance listed in the

table. If you don’t 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.

82

83

84

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.

85

86

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.

87

88

89

90

91

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.

92

93

After finishing the managed system setup for your system make sure that you add it to a

Solution, to activate Early Watch alerts!

94

95

96

97

98

99

100

101

102

103

104

105