solution manager diagnostics - solman 7.1 configuration
TRANSCRIPT
Configuration of SAP Solution Manager
71
Active Global Support
2011
copy 2011 SAP AG All rights reserved 2
Disclaimer
This presentation outlines our general product direction and should not be relied on in
making a purchase decision This presentation is not subject to your license agreement
or any other agreement with SAP SAP has no obligation to pursue any course of
business outlined in this presentation or to develop or release any functionality
mentioned in this presentation This presentation and SAPs strategy and possible
future developments are subject to change and may be changed by SAP at any time for
any reason without notice This document is provided without a warranty of any kind
either express or implied including but not limited to the implied warranties of
merchantability fitness for a particular purpose or non-infringement SAP assumes no
responsibility for errors or omissions in this document except if such damages were
caused by SAP intentionally or grossly negligent
SAP Solution Manager Landscape Overview
copy 2011 SAP AG All rights reserved 4
Solution Manager Landscape Components
SAP Solution Manager
71
Managed System 1
ERP
Managed System 2
Enterprise Portal
copy 2011 SAP AG All rights reserved 5
SAP Solution Manager
Components on the Client PC
Client PC Components
Access to the Solution Manager with
Browser (Internet Explorerhellip)
SAPGui
NetWeaver Business Client
For the different applications some plugin
components are needed
Microsoft Silverlight (for Introscope WebView)
Adobe Flash
Java Runtime Environment
BMC Appsight BlackBox Console
copy 2011 SAP AG All rights reserved 6
SAP Solution Manager
Components on the Managing System
SAP Solution Manager 71
SAP
Business
Warehouse
CA Wily
Introscope
LMDB SMSYSolar
Directory
Workcenter
Data Stores
Repositories
Engines
Applications
EFWK CTS+ hellip
RCAService
Desk
Tech
Monhellip
Managing system components
SAP Solution Manager 71
Is a dual stack system (ABAP amp J2EE)
Includes SAP Business Warehouse
Includes CRM 70
Includes a license for CA Wily Introscope
(Right to View)
Uses SLD amp LMDB for landscape data
maintenance
Possible sizing options
Installation of SAP BW on separate host
Installation of Wily Introscope Enterprise
Manager on separate host
Sizing of Wily Introscope with Manager of
Manager Concept
copy 2011 SAP AG All rights reserved 7
SAP Solution Manager
Components On Managed System
Managed System
Diagnostics Agent
SAP Host
Agent
J2EE
IS BC
Agent
ABAP
Local
SLD
Central SLD
Wily Host
Agent
J2EE
Command
Console
OS
Command
Console
ST-PI
ST-API
(Extractors)
Managed system components
Managed System
Can be any kind of SAP non-SAP system
Can include a local SLD (eg Process
Integration)
Depending on system type (ABAPJavahellip)
different agents and plugins are needed
Agents amp Plugins
One Diagnostics Agent per virtual host
Agent applications are managed centrally from
Sap Solution Manager system
One SAP Host Agent per physical host
For ABAP systems the plugins need to be
installed depending on the managed system
product (ST-PI and ST-API)
For J2EE Java and Net systems the CA
Wily Introscope Byte Code Agent needs to be
deployed (can be done from SAP Solution
Manager)
copy 2011 SAP AG All rights reserved 8
Logical Landscape View
SAP Solution Manager 71
SAP
Business
Warehouse
CA Wily
Introscope
Solar
DirectorySMSY LMDB
Workcenter
Data Stores
Repositories
Engines
Applications
EFWK CTS+ hellip
RCAService
DeskChaRM hellip
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
SLD
copy 2011 SAP AG All rights reserved 9
Solution Manager ArchitectureSLD Data Distribution in a Typical Landscape
PI (non-prod) Systems (non-prod)NWDI
Other systems (prod)PI (prod)
Non-Production Environment
Production Environment
SLD
(design-time)
SLD
(runtime)
Systems Managing Systems
SAP Solution
Manager
LMDB
Front Ends
SAP NetWeaver
Developer Studio
Browser Access
SLD client access
SLD Sync (unidirectional)
Forwarding of data on Technical
Systems
Manual export import
Self registration of Technical
Systems
copy 2011 SAP AG All rights reserved 10
SAP Solution Manager 71
SLD amp LMDB
Solution Manager 71
Local SLD
(Not
required)
SLD1
(PI)
SLD2
(Data
Supplier)
SLD3
(NWDI)
SMSY LMDB
LMDB implications in 71
Flexible landscape database based on the
CIM data model
No local SLD required anymore but
supported
Full synchronization between Landscape
SLD‟s and LMDB
Automatic data migration from SMSY to
LMDB in the 71 upgrade where needed
for the respective Solution Manager
scenarios
copy 2011 SAP AG All rights reserved 11
SAP Solution Manager 71
Outside Discovery amp LMDB
Host B
Host A
DB
IIS
Virt Host A1
Virt Host B1
SolMan Host
SLD
OS Info
OS Info
SAP Host
Agent
Diagnostics
Agent
Diagnostics
Agent
SAP Host
Agent
Enhances available landscape information in LMDB in SAP
Solution Manager
Support also products where no SLD data supplier is available
eg
Databases amp Operating Systems
Microsoft components
Is aware of virtualization through information from SAP Host Agent
Works completely automatic with Diagnostics Agents
SAP Solution Manager 71
LMDB
copy 2011 SAP AG All rights reserved 12
Landscape scenariosWhere to install an agent
PhyHost2 PhyHost3
VHost1 VHost2VHost3
PhyHost1
C1 C2C3 C4 C5 C6
cluster
1 diagnostics agent per managed
bdquohost‟ represented by a name
physical or virtual
1 SAP HostAgent per physical host
1 agent per host supports several
managed systems running on the
same named host
C7 C8
Diagnostics Agent
Managed ComponentSAP Solution Manager
SAP HostAgent
SAP Host
Agent
Diagnostics
Agent 1
SAP Host
Agent
Diagnostics
Agent 2
Diagnostics
Agent 4
Diagnostics
Agent 3
SAP Host
Agent
Diagnostics
Agent 1
H
D1
copy 2011 SAP AG All rights reserved 13
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 14
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 2
Disclaimer
This presentation outlines our general product direction and should not be relied on in
making a purchase decision This presentation is not subject to your license agreement
or any other agreement with SAP SAP has no obligation to pursue any course of
business outlined in this presentation or to develop or release any functionality
mentioned in this presentation This presentation and SAPs strategy and possible
future developments are subject to change and may be changed by SAP at any time for
any reason without notice This document is provided without a warranty of any kind
either express or implied including but not limited to the implied warranties of
merchantability fitness for a particular purpose or non-infringement SAP assumes no
responsibility for errors or omissions in this document except if such damages were
caused by SAP intentionally or grossly negligent
SAP Solution Manager Landscape Overview
copy 2011 SAP AG All rights reserved 4
Solution Manager Landscape Components
SAP Solution Manager
71
Managed System 1
ERP
Managed System 2
Enterprise Portal
copy 2011 SAP AG All rights reserved 5
SAP Solution Manager
Components on the Client PC
Client PC Components
Access to the Solution Manager with
Browser (Internet Explorerhellip)
SAPGui
NetWeaver Business Client
For the different applications some plugin
components are needed
Microsoft Silverlight (for Introscope WebView)
Adobe Flash
Java Runtime Environment
BMC Appsight BlackBox Console
copy 2011 SAP AG All rights reserved 6
SAP Solution Manager
Components on the Managing System
SAP Solution Manager 71
SAP
Business
Warehouse
CA Wily
Introscope
LMDB SMSYSolar
Directory
Workcenter
Data Stores
Repositories
Engines
Applications
EFWK CTS+ hellip
RCAService
Desk
Tech
Monhellip
Managing system components
SAP Solution Manager 71
Is a dual stack system (ABAP amp J2EE)
Includes SAP Business Warehouse
Includes CRM 70
Includes a license for CA Wily Introscope
(Right to View)
Uses SLD amp LMDB for landscape data
maintenance
Possible sizing options
Installation of SAP BW on separate host
Installation of Wily Introscope Enterprise
Manager on separate host
Sizing of Wily Introscope with Manager of
Manager Concept
copy 2011 SAP AG All rights reserved 7
SAP Solution Manager
Components On Managed System
Managed System
Diagnostics Agent
SAP Host
Agent
J2EE
IS BC
Agent
ABAP
Local
SLD
Central SLD
Wily Host
Agent
J2EE
Command
Console
OS
Command
Console
ST-PI
ST-API
(Extractors)
Managed system components
Managed System
Can be any kind of SAP non-SAP system
Can include a local SLD (eg Process
Integration)
Depending on system type (ABAPJavahellip)
different agents and plugins are needed
Agents amp Plugins
One Diagnostics Agent per virtual host
Agent applications are managed centrally from
Sap Solution Manager system
One SAP Host Agent per physical host
For ABAP systems the plugins need to be
installed depending on the managed system
product (ST-PI and ST-API)
For J2EE Java and Net systems the CA
Wily Introscope Byte Code Agent needs to be
deployed (can be done from SAP Solution
Manager)
copy 2011 SAP AG All rights reserved 8
Logical Landscape View
SAP Solution Manager 71
SAP
Business
Warehouse
CA Wily
Introscope
Solar
DirectorySMSY LMDB
Workcenter
Data Stores
Repositories
Engines
Applications
EFWK CTS+ hellip
RCAService
DeskChaRM hellip
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
SLD
copy 2011 SAP AG All rights reserved 9
Solution Manager ArchitectureSLD Data Distribution in a Typical Landscape
PI (non-prod) Systems (non-prod)NWDI
Other systems (prod)PI (prod)
Non-Production Environment
Production Environment
SLD
(design-time)
SLD
(runtime)
Systems Managing Systems
SAP Solution
Manager
LMDB
Front Ends
SAP NetWeaver
Developer Studio
Browser Access
SLD client access
SLD Sync (unidirectional)
Forwarding of data on Technical
Systems
Manual export import
Self registration of Technical
Systems
copy 2011 SAP AG All rights reserved 10
SAP Solution Manager 71
SLD amp LMDB
Solution Manager 71
Local SLD
(Not
required)
SLD1
(PI)
SLD2
(Data
Supplier)
SLD3
(NWDI)
SMSY LMDB
LMDB implications in 71
Flexible landscape database based on the
CIM data model
No local SLD required anymore but
supported
Full synchronization between Landscape
SLD‟s and LMDB
Automatic data migration from SMSY to
LMDB in the 71 upgrade where needed
for the respective Solution Manager
scenarios
copy 2011 SAP AG All rights reserved 11
SAP Solution Manager 71
Outside Discovery amp LMDB
Host B
Host A
DB
IIS
Virt Host A1
Virt Host B1
SolMan Host
SLD
OS Info
OS Info
SAP Host
Agent
Diagnostics
Agent
Diagnostics
Agent
SAP Host
Agent
Enhances available landscape information in LMDB in SAP
Solution Manager
Support also products where no SLD data supplier is available
eg
Databases amp Operating Systems
Microsoft components
Is aware of virtualization through information from SAP Host Agent
Works completely automatic with Diagnostics Agents
SAP Solution Manager 71
LMDB
copy 2011 SAP AG All rights reserved 12
Landscape scenariosWhere to install an agent
PhyHost2 PhyHost3
VHost1 VHost2VHost3
PhyHost1
C1 C2C3 C4 C5 C6
cluster
1 diagnostics agent per managed
bdquohost‟ represented by a name
physical or virtual
1 SAP HostAgent per physical host
1 agent per host supports several
managed systems running on the
same named host
C7 C8
Diagnostics Agent
Managed ComponentSAP Solution Manager
SAP HostAgent
SAP Host
Agent
Diagnostics
Agent 1
SAP Host
Agent
Diagnostics
Agent 2
Diagnostics
Agent 4
Diagnostics
Agent 3
SAP Host
Agent
Diagnostics
Agent 1
H
D1
copy 2011 SAP AG All rights reserved 13
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 14
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
SAP Solution Manager Landscape Overview
copy 2011 SAP AG All rights reserved 4
Solution Manager Landscape Components
SAP Solution Manager
71
Managed System 1
ERP
Managed System 2
Enterprise Portal
copy 2011 SAP AG All rights reserved 5
SAP Solution Manager
Components on the Client PC
Client PC Components
Access to the Solution Manager with
Browser (Internet Explorerhellip)
SAPGui
NetWeaver Business Client
For the different applications some plugin
components are needed
Microsoft Silverlight (for Introscope WebView)
Adobe Flash
Java Runtime Environment
BMC Appsight BlackBox Console
copy 2011 SAP AG All rights reserved 6
SAP Solution Manager
Components on the Managing System
SAP Solution Manager 71
SAP
Business
Warehouse
CA Wily
Introscope
LMDB SMSYSolar
Directory
Workcenter
Data Stores
Repositories
Engines
Applications
EFWK CTS+ hellip
RCAService
Desk
Tech
Monhellip
Managing system components
SAP Solution Manager 71
Is a dual stack system (ABAP amp J2EE)
Includes SAP Business Warehouse
Includes CRM 70
Includes a license for CA Wily Introscope
(Right to View)
Uses SLD amp LMDB for landscape data
maintenance
Possible sizing options
Installation of SAP BW on separate host
Installation of Wily Introscope Enterprise
Manager on separate host
Sizing of Wily Introscope with Manager of
Manager Concept
copy 2011 SAP AG All rights reserved 7
SAP Solution Manager
Components On Managed System
Managed System
Diagnostics Agent
SAP Host
Agent
J2EE
IS BC
Agent
ABAP
Local
SLD
Central SLD
Wily Host
Agent
J2EE
Command
Console
OS
Command
Console
ST-PI
ST-API
(Extractors)
Managed system components
Managed System
Can be any kind of SAP non-SAP system
Can include a local SLD (eg Process
Integration)
Depending on system type (ABAPJavahellip)
different agents and plugins are needed
Agents amp Plugins
One Diagnostics Agent per virtual host
Agent applications are managed centrally from
Sap Solution Manager system
One SAP Host Agent per physical host
For ABAP systems the plugins need to be
installed depending on the managed system
product (ST-PI and ST-API)
For J2EE Java and Net systems the CA
Wily Introscope Byte Code Agent needs to be
deployed (can be done from SAP Solution
Manager)
copy 2011 SAP AG All rights reserved 8
Logical Landscape View
SAP Solution Manager 71
SAP
Business
Warehouse
CA Wily
Introscope
Solar
DirectorySMSY LMDB
Workcenter
Data Stores
Repositories
Engines
Applications
EFWK CTS+ hellip
RCAService
DeskChaRM hellip
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
SLD
copy 2011 SAP AG All rights reserved 9
Solution Manager ArchitectureSLD Data Distribution in a Typical Landscape
PI (non-prod) Systems (non-prod)NWDI
Other systems (prod)PI (prod)
Non-Production Environment
Production Environment
SLD
(design-time)
SLD
(runtime)
Systems Managing Systems
SAP Solution
Manager
LMDB
Front Ends
SAP NetWeaver
Developer Studio
Browser Access
SLD client access
SLD Sync (unidirectional)
Forwarding of data on Technical
Systems
Manual export import
Self registration of Technical
Systems
copy 2011 SAP AG All rights reserved 10
SAP Solution Manager 71
SLD amp LMDB
Solution Manager 71
Local SLD
(Not
required)
SLD1
(PI)
SLD2
(Data
Supplier)
SLD3
(NWDI)
SMSY LMDB
LMDB implications in 71
Flexible landscape database based on the
CIM data model
No local SLD required anymore but
supported
Full synchronization between Landscape
SLD‟s and LMDB
Automatic data migration from SMSY to
LMDB in the 71 upgrade where needed
for the respective Solution Manager
scenarios
copy 2011 SAP AG All rights reserved 11
SAP Solution Manager 71
Outside Discovery amp LMDB
Host B
Host A
DB
IIS
Virt Host A1
Virt Host B1
SolMan Host
SLD
OS Info
OS Info
SAP Host
Agent
Diagnostics
Agent
Diagnostics
Agent
SAP Host
Agent
Enhances available landscape information in LMDB in SAP
Solution Manager
Support also products where no SLD data supplier is available
eg
Databases amp Operating Systems
Microsoft components
Is aware of virtualization through information from SAP Host Agent
Works completely automatic with Diagnostics Agents
SAP Solution Manager 71
LMDB
copy 2011 SAP AG All rights reserved 12
Landscape scenariosWhere to install an agent
PhyHost2 PhyHost3
VHost1 VHost2VHost3
PhyHost1
C1 C2C3 C4 C5 C6
cluster
1 diagnostics agent per managed
bdquohost‟ represented by a name
physical or virtual
1 SAP HostAgent per physical host
1 agent per host supports several
managed systems running on the
same named host
C7 C8
Diagnostics Agent
Managed ComponentSAP Solution Manager
SAP HostAgent
SAP Host
Agent
Diagnostics
Agent 1
SAP Host
Agent
Diagnostics
Agent 2
Diagnostics
Agent 4
Diagnostics
Agent 3
SAP Host
Agent
Diagnostics
Agent 1
H
D1
copy 2011 SAP AG All rights reserved 13
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 14
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 4
Solution Manager Landscape Components
SAP Solution Manager
71
Managed System 1
ERP
Managed System 2
Enterprise Portal
copy 2011 SAP AG All rights reserved 5
SAP Solution Manager
Components on the Client PC
Client PC Components
Access to the Solution Manager with
Browser (Internet Explorerhellip)
SAPGui
NetWeaver Business Client
For the different applications some plugin
components are needed
Microsoft Silverlight (for Introscope WebView)
Adobe Flash
Java Runtime Environment
BMC Appsight BlackBox Console
copy 2011 SAP AG All rights reserved 6
SAP Solution Manager
Components on the Managing System
SAP Solution Manager 71
SAP
Business
Warehouse
CA Wily
Introscope
LMDB SMSYSolar
Directory
Workcenter
Data Stores
Repositories
Engines
Applications
EFWK CTS+ hellip
RCAService
Desk
Tech
Monhellip
Managing system components
SAP Solution Manager 71
Is a dual stack system (ABAP amp J2EE)
Includes SAP Business Warehouse
Includes CRM 70
Includes a license for CA Wily Introscope
(Right to View)
Uses SLD amp LMDB for landscape data
maintenance
Possible sizing options
Installation of SAP BW on separate host
Installation of Wily Introscope Enterprise
Manager on separate host
Sizing of Wily Introscope with Manager of
Manager Concept
copy 2011 SAP AG All rights reserved 7
SAP Solution Manager
Components On Managed System
Managed System
Diagnostics Agent
SAP Host
Agent
J2EE
IS BC
Agent
ABAP
Local
SLD
Central SLD
Wily Host
Agent
J2EE
Command
Console
OS
Command
Console
ST-PI
ST-API
(Extractors)
Managed system components
Managed System
Can be any kind of SAP non-SAP system
Can include a local SLD (eg Process
Integration)
Depending on system type (ABAPJavahellip)
different agents and plugins are needed
Agents amp Plugins
One Diagnostics Agent per virtual host
Agent applications are managed centrally from
Sap Solution Manager system
One SAP Host Agent per physical host
For ABAP systems the plugins need to be
installed depending on the managed system
product (ST-PI and ST-API)
For J2EE Java and Net systems the CA
Wily Introscope Byte Code Agent needs to be
deployed (can be done from SAP Solution
Manager)
copy 2011 SAP AG All rights reserved 8
Logical Landscape View
SAP Solution Manager 71
SAP
Business
Warehouse
CA Wily
Introscope
Solar
DirectorySMSY LMDB
Workcenter
Data Stores
Repositories
Engines
Applications
EFWK CTS+ hellip
RCAService
DeskChaRM hellip
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
SLD
copy 2011 SAP AG All rights reserved 9
Solution Manager ArchitectureSLD Data Distribution in a Typical Landscape
PI (non-prod) Systems (non-prod)NWDI
Other systems (prod)PI (prod)
Non-Production Environment
Production Environment
SLD
(design-time)
SLD
(runtime)
Systems Managing Systems
SAP Solution
Manager
LMDB
Front Ends
SAP NetWeaver
Developer Studio
Browser Access
SLD client access
SLD Sync (unidirectional)
Forwarding of data on Technical
Systems
Manual export import
Self registration of Technical
Systems
copy 2011 SAP AG All rights reserved 10
SAP Solution Manager 71
SLD amp LMDB
Solution Manager 71
Local SLD
(Not
required)
SLD1
(PI)
SLD2
(Data
Supplier)
SLD3
(NWDI)
SMSY LMDB
LMDB implications in 71
Flexible landscape database based on the
CIM data model
No local SLD required anymore but
supported
Full synchronization between Landscape
SLD‟s and LMDB
Automatic data migration from SMSY to
LMDB in the 71 upgrade where needed
for the respective Solution Manager
scenarios
copy 2011 SAP AG All rights reserved 11
SAP Solution Manager 71
Outside Discovery amp LMDB
Host B
Host A
DB
IIS
Virt Host A1
Virt Host B1
SolMan Host
SLD
OS Info
OS Info
SAP Host
Agent
Diagnostics
Agent
Diagnostics
Agent
SAP Host
Agent
Enhances available landscape information in LMDB in SAP
Solution Manager
Support also products where no SLD data supplier is available
eg
Databases amp Operating Systems
Microsoft components
Is aware of virtualization through information from SAP Host Agent
Works completely automatic with Diagnostics Agents
SAP Solution Manager 71
LMDB
copy 2011 SAP AG All rights reserved 12
Landscape scenariosWhere to install an agent
PhyHost2 PhyHost3
VHost1 VHost2VHost3
PhyHost1
C1 C2C3 C4 C5 C6
cluster
1 diagnostics agent per managed
bdquohost‟ represented by a name
physical or virtual
1 SAP HostAgent per physical host
1 agent per host supports several
managed systems running on the
same named host
C7 C8
Diagnostics Agent
Managed ComponentSAP Solution Manager
SAP HostAgent
SAP Host
Agent
Diagnostics
Agent 1
SAP Host
Agent
Diagnostics
Agent 2
Diagnostics
Agent 4
Diagnostics
Agent 3
SAP Host
Agent
Diagnostics
Agent 1
H
D1
copy 2011 SAP AG All rights reserved 13
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 14
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 5
SAP Solution Manager
Components on the Client PC
Client PC Components
Access to the Solution Manager with
Browser (Internet Explorerhellip)
SAPGui
NetWeaver Business Client
For the different applications some plugin
components are needed
Microsoft Silverlight (for Introscope WebView)
Adobe Flash
Java Runtime Environment
BMC Appsight BlackBox Console
copy 2011 SAP AG All rights reserved 6
SAP Solution Manager
Components on the Managing System
SAP Solution Manager 71
SAP
Business
Warehouse
CA Wily
Introscope
LMDB SMSYSolar
Directory
Workcenter
Data Stores
Repositories
Engines
Applications
EFWK CTS+ hellip
RCAService
Desk
Tech
Monhellip
Managing system components
SAP Solution Manager 71
Is a dual stack system (ABAP amp J2EE)
Includes SAP Business Warehouse
Includes CRM 70
Includes a license for CA Wily Introscope
(Right to View)
Uses SLD amp LMDB for landscape data
maintenance
Possible sizing options
Installation of SAP BW on separate host
Installation of Wily Introscope Enterprise
Manager on separate host
Sizing of Wily Introscope with Manager of
Manager Concept
copy 2011 SAP AG All rights reserved 7
SAP Solution Manager
Components On Managed System
Managed System
Diagnostics Agent
SAP Host
Agent
J2EE
IS BC
Agent
ABAP
Local
SLD
Central SLD
Wily Host
Agent
J2EE
Command
Console
OS
Command
Console
ST-PI
ST-API
(Extractors)
Managed system components
Managed System
Can be any kind of SAP non-SAP system
Can include a local SLD (eg Process
Integration)
Depending on system type (ABAPJavahellip)
different agents and plugins are needed
Agents amp Plugins
One Diagnostics Agent per virtual host
Agent applications are managed centrally from
Sap Solution Manager system
One SAP Host Agent per physical host
For ABAP systems the plugins need to be
installed depending on the managed system
product (ST-PI and ST-API)
For J2EE Java and Net systems the CA
Wily Introscope Byte Code Agent needs to be
deployed (can be done from SAP Solution
Manager)
copy 2011 SAP AG All rights reserved 8
Logical Landscape View
SAP Solution Manager 71
SAP
Business
Warehouse
CA Wily
Introscope
Solar
DirectorySMSY LMDB
Workcenter
Data Stores
Repositories
Engines
Applications
EFWK CTS+ hellip
RCAService
DeskChaRM hellip
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
SLD
copy 2011 SAP AG All rights reserved 9
Solution Manager ArchitectureSLD Data Distribution in a Typical Landscape
PI (non-prod) Systems (non-prod)NWDI
Other systems (prod)PI (prod)
Non-Production Environment
Production Environment
SLD
(design-time)
SLD
(runtime)
Systems Managing Systems
SAP Solution
Manager
LMDB
Front Ends
SAP NetWeaver
Developer Studio
Browser Access
SLD client access
SLD Sync (unidirectional)
Forwarding of data on Technical
Systems
Manual export import
Self registration of Technical
Systems
copy 2011 SAP AG All rights reserved 10
SAP Solution Manager 71
SLD amp LMDB
Solution Manager 71
Local SLD
(Not
required)
SLD1
(PI)
SLD2
(Data
Supplier)
SLD3
(NWDI)
SMSY LMDB
LMDB implications in 71
Flexible landscape database based on the
CIM data model
No local SLD required anymore but
supported
Full synchronization between Landscape
SLD‟s and LMDB
Automatic data migration from SMSY to
LMDB in the 71 upgrade where needed
for the respective Solution Manager
scenarios
copy 2011 SAP AG All rights reserved 11
SAP Solution Manager 71
Outside Discovery amp LMDB
Host B
Host A
DB
IIS
Virt Host A1
Virt Host B1
SolMan Host
SLD
OS Info
OS Info
SAP Host
Agent
Diagnostics
Agent
Diagnostics
Agent
SAP Host
Agent
Enhances available landscape information in LMDB in SAP
Solution Manager
Support also products where no SLD data supplier is available
eg
Databases amp Operating Systems
Microsoft components
Is aware of virtualization through information from SAP Host Agent
Works completely automatic with Diagnostics Agents
SAP Solution Manager 71
LMDB
copy 2011 SAP AG All rights reserved 12
Landscape scenariosWhere to install an agent
PhyHost2 PhyHost3
VHost1 VHost2VHost3
PhyHost1
C1 C2C3 C4 C5 C6
cluster
1 diagnostics agent per managed
bdquohost‟ represented by a name
physical or virtual
1 SAP HostAgent per physical host
1 agent per host supports several
managed systems running on the
same named host
C7 C8
Diagnostics Agent
Managed ComponentSAP Solution Manager
SAP HostAgent
SAP Host
Agent
Diagnostics
Agent 1
SAP Host
Agent
Diagnostics
Agent 2
Diagnostics
Agent 4
Diagnostics
Agent 3
SAP Host
Agent
Diagnostics
Agent 1
H
D1
copy 2011 SAP AG All rights reserved 13
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 14
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 6
SAP Solution Manager
Components on the Managing System
SAP Solution Manager 71
SAP
Business
Warehouse
CA Wily
Introscope
LMDB SMSYSolar
Directory
Workcenter
Data Stores
Repositories
Engines
Applications
EFWK CTS+ hellip
RCAService
Desk
Tech
Monhellip
Managing system components
SAP Solution Manager 71
Is a dual stack system (ABAP amp J2EE)
Includes SAP Business Warehouse
Includes CRM 70
Includes a license for CA Wily Introscope
(Right to View)
Uses SLD amp LMDB for landscape data
maintenance
Possible sizing options
Installation of SAP BW on separate host
Installation of Wily Introscope Enterprise
Manager on separate host
Sizing of Wily Introscope with Manager of
Manager Concept
copy 2011 SAP AG All rights reserved 7
SAP Solution Manager
Components On Managed System
Managed System
Diagnostics Agent
SAP Host
Agent
J2EE
IS BC
Agent
ABAP
Local
SLD
Central SLD
Wily Host
Agent
J2EE
Command
Console
OS
Command
Console
ST-PI
ST-API
(Extractors)
Managed system components
Managed System
Can be any kind of SAP non-SAP system
Can include a local SLD (eg Process
Integration)
Depending on system type (ABAPJavahellip)
different agents and plugins are needed
Agents amp Plugins
One Diagnostics Agent per virtual host
Agent applications are managed centrally from
Sap Solution Manager system
One SAP Host Agent per physical host
For ABAP systems the plugins need to be
installed depending on the managed system
product (ST-PI and ST-API)
For J2EE Java and Net systems the CA
Wily Introscope Byte Code Agent needs to be
deployed (can be done from SAP Solution
Manager)
copy 2011 SAP AG All rights reserved 8
Logical Landscape View
SAP Solution Manager 71
SAP
Business
Warehouse
CA Wily
Introscope
Solar
DirectorySMSY LMDB
Workcenter
Data Stores
Repositories
Engines
Applications
EFWK CTS+ hellip
RCAService
DeskChaRM hellip
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
SLD
copy 2011 SAP AG All rights reserved 9
Solution Manager ArchitectureSLD Data Distribution in a Typical Landscape
PI (non-prod) Systems (non-prod)NWDI
Other systems (prod)PI (prod)
Non-Production Environment
Production Environment
SLD
(design-time)
SLD
(runtime)
Systems Managing Systems
SAP Solution
Manager
LMDB
Front Ends
SAP NetWeaver
Developer Studio
Browser Access
SLD client access
SLD Sync (unidirectional)
Forwarding of data on Technical
Systems
Manual export import
Self registration of Technical
Systems
copy 2011 SAP AG All rights reserved 10
SAP Solution Manager 71
SLD amp LMDB
Solution Manager 71
Local SLD
(Not
required)
SLD1
(PI)
SLD2
(Data
Supplier)
SLD3
(NWDI)
SMSY LMDB
LMDB implications in 71
Flexible landscape database based on the
CIM data model
No local SLD required anymore but
supported
Full synchronization between Landscape
SLD‟s and LMDB
Automatic data migration from SMSY to
LMDB in the 71 upgrade where needed
for the respective Solution Manager
scenarios
copy 2011 SAP AG All rights reserved 11
SAP Solution Manager 71
Outside Discovery amp LMDB
Host B
Host A
DB
IIS
Virt Host A1
Virt Host B1
SolMan Host
SLD
OS Info
OS Info
SAP Host
Agent
Diagnostics
Agent
Diagnostics
Agent
SAP Host
Agent
Enhances available landscape information in LMDB in SAP
Solution Manager
Support also products where no SLD data supplier is available
eg
Databases amp Operating Systems
Microsoft components
Is aware of virtualization through information from SAP Host Agent
Works completely automatic with Diagnostics Agents
SAP Solution Manager 71
LMDB
copy 2011 SAP AG All rights reserved 12
Landscape scenariosWhere to install an agent
PhyHost2 PhyHost3
VHost1 VHost2VHost3
PhyHost1
C1 C2C3 C4 C5 C6
cluster
1 diagnostics agent per managed
bdquohost‟ represented by a name
physical or virtual
1 SAP HostAgent per physical host
1 agent per host supports several
managed systems running on the
same named host
C7 C8
Diagnostics Agent
Managed ComponentSAP Solution Manager
SAP HostAgent
SAP Host
Agent
Diagnostics
Agent 1
SAP Host
Agent
Diagnostics
Agent 2
Diagnostics
Agent 4
Diagnostics
Agent 3
SAP Host
Agent
Diagnostics
Agent 1
H
D1
copy 2011 SAP AG All rights reserved 13
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 14
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 7
SAP Solution Manager
Components On Managed System
Managed System
Diagnostics Agent
SAP Host
Agent
J2EE
IS BC
Agent
ABAP
Local
SLD
Central SLD
Wily Host
Agent
J2EE
Command
Console
OS
Command
Console
ST-PI
ST-API
(Extractors)
Managed system components
Managed System
Can be any kind of SAP non-SAP system
Can include a local SLD (eg Process
Integration)
Depending on system type (ABAPJavahellip)
different agents and plugins are needed
Agents amp Plugins
One Diagnostics Agent per virtual host
Agent applications are managed centrally from
Sap Solution Manager system
One SAP Host Agent per physical host
For ABAP systems the plugins need to be
installed depending on the managed system
product (ST-PI and ST-API)
For J2EE Java and Net systems the CA
Wily Introscope Byte Code Agent needs to be
deployed (can be done from SAP Solution
Manager)
copy 2011 SAP AG All rights reserved 8
Logical Landscape View
SAP Solution Manager 71
SAP
Business
Warehouse
CA Wily
Introscope
Solar
DirectorySMSY LMDB
Workcenter
Data Stores
Repositories
Engines
Applications
EFWK CTS+ hellip
RCAService
DeskChaRM hellip
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
SLD
copy 2011 SAP AG All rights reserved 9
Solution Manager ArchitectureSLD Data Distribution in a Typical Landscape
PI (non-prod) Systems (non-prod)NWDI
Other systems (prod)PI (prod)
Non-Production Environment
Production Environment
SLD
(design-time)
SLD
(runtime)
Systems Managing Systems
SAP Solution
Manager
LMDB
Front Ends
SAP NetWeaver
Developer Studio
Browser Access
SLD client access
SLD Sync (unidirectional)
Forwarding of data on Technical
Systems
Manual export import
Self registration of Technical
Systems
copy 2011 SAP AG All rights reserved 10
SAP Solution Manager 71
SLD amp LMDB
Solution Manager 71
Local SLD
(Not
required)
SLD1
(PI)
SLD2
(Data
Supplier)
SLD3
(NWDI)
SMSY LMDB
LMDB implications in 71
Flexible landscape database based on the
CIM data model
No local SLD required anymore but
supported
Full synchronization between Landscape
SLD‟s and LMDB
Automatic data migration from SMSY to
LMDB in the 71 upgrade where needed
for the respective Solution Manager
scenarios
copy 2011 SAP AG All rights reserved 11
SAP Solution Manager 71
Outside Discovery amp LMDB
Host B
Host A
DB
IIS
Virt Host A1
Virt Host B1
SolMan Host
SLD
OS Info
OS Info
SAP Host
Agent
Diagnostics
Agent
Diagnostics
Agent
SAP Host
Agent
Enhances available landscape information in LMDB in SAP
Solution Manager
Support also products where no SLD data supplier is available
eg
Databases amp Operating Systems
Microsoft components
Is aware of virtualization through information from SAP Host Agent
Works completely automatic with Diagnostics Agents
SAP Solution Manager 71
LMDB
copy 2011 SAP AG All rights reserved 12
Landscape scenariosWhere to install an agent
PhyHost2 PhyHost3
VHost1 VHost2VHost3
PhyHost1
C1 C2C3 C4 C5 C6
cluster
1 diagnostics agent per managed
bdquohost‟ represented by a name
physical or virtual
1 SAP HostAgent per physical host
1 agent per host supports several
managed systems running on the
same named host
C7 C8
Diagnostics Agent
Managed ComponentSAP Solution Manager
SAP HostAgent
SAP Host
Agent
Diagnostics
Agent 1
SAP Host
Agent
Diagnostics
Agent 2
Diagnostics
Agent 4
Diagnostics
Agent 3
SAP Host
Agent
Diagnostics
Agent 1
H
D1
copy 2011 SAP AG All rights reserved 13
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 14
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 8
Logical Landscape View
SAP Solution Manager 71
SAP
Business
Warehouse
CA Wily
Introscope
Solar
DirectorySMSY LMDB
Workcenter
Data Stores
Repositories
Engines
Applications
EFWK CTS+ hellip
RCAService
DeskChaRM hellip
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
Managed System
Diagnostics
Agent
SLD
copy 2011 SAP AG All rights reserved 9
Solution Manager ArchitectureSLD Data Distribution in a Typical Landscape
PI (non-prod) Systems (non-prod)NWDI
Other systems (prod)PI (prod)
Non-Production Environment
Production Environment
SLD
(design-time)
SLD
(runtime)
Systems Managing Systems
SAP Solution
Manager
LMDB
Front Ends
SAP NetWeaver
Developer Studio
Browser Access
SLD client access
SLD Sync (unidirectional)
Forwarding of data on Technical
Systems
Manual export import
Self registration of Technical
Systems
copy 2011 SAP AG All rights reserved 10
SAP Solution Manager 71
SLD amp LMDB
Solution Manager 71
Local SLD
(Not
required)
SLD1
(PI)
SLD2
(Data
Supplier)
SLD3
(NWDI)
SMSY LMDB
LMDB implications in 71
Flexible landscape database based on the
CIM data model
No local SLD required anymore but
supported
Full synchronization between Landscape
SLD‟s and LMDB
Automatic data migration from SMSY to
LMDB in the 71 upgrade where needed
for the respective Solution Manager
scenarios
copy 2011 SAP AG All rights reserved 11
SAP Solution Manager 71
Outside Discovery amp LMDB
Host B
Host A
DB
IIS
Virt Host A1
Virt Host B1
SolMan Host
SLD
OS Info
OS Info
SAP Host
Agent
Diagnostics
Agent
Diagnostics
Agent
SAP Host
Agent
Enhances available landscape information in LMDB in SAP
Solution Manager
Support also products where no SLD data supplier is available
eg
Databases amp Operating Systems
Microsoft components
Is aware of virtualization through information from SAP Host Agent
Works completely automatic with Diagnostics Agents
SAP Solution Manager 71
LMDB
copy 2011 SAP AG All rights reserved 12
Landscape scenariosWhere to install an agent
PhyHost2 PhyHost3
VHost1 VHost2VHost3
PhyHost1
C1 C2C3 C4 C5 C6
cluster
1 diagnostics agent per managed
bdquohost‟ represented by a name
physical or virtual
1 SAP HostAgent per physical host
1 agent per host supports several
managed systems running on the
same named host
C7 C8
Diagnostics Agent
Managed ComponentSAP Solution Manager
SAP HostAgent
SAP Host
Agent
Diagnostics
Agent 1
SAP Host
Agent
Diagnostics
Agent 2
Diagnostics
Agent 4
Diagnostics
Agent 3
SAP Host
Agent
Diagnostics
Agent 1
H
D1
copy 2011 SAP AG All rights reserved 13
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 14
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 9
Solution Manager ArchitectureSLD Data Distribution in a Typical Landscape
PI (non-prod) Systems (non-prod)NWDI
Other systems (prod)PI (prod)
Non-Production Environment
Production Environment
SLD
(design-time)
SLD
(runtime)
Systems Managing Systems
SAP Solution
Manager
LMDB
Front Ends
SAP NetWeaver
Developer Studio
Browser Access
SLD client access
SLD Sync (unidirectional)
Forwarding of data on Technical
Systems
Manual export import
Self registration of Technical
Systems
copy 2011 SAP AG All rights reserved 10
SAP Solution Manager 71
SLD amp LMDB
Solution Manager 71
Local SLD
(Not
required)
SLD1
(PI)
SLD2
(Data
Supplier)
SLD3
(NWDI)
SMSY LMDB
LMDB implications in 71
Flexible landscape database based on the
CIM data model
No local SLD required anymore but
supported
Full synchronization between Landscape
SLD‟s and LMDB
Automatic data migration from SMSY to
LMDB in the 71 upgrade where needed
for the respective Solution Manager
scenarios
copy 2011 SAP AG All rights reserved 11
SAP Solution Manager 71
Outside Discovery amp LMDB
Host B
Host A
DB
IIS
Virt Host A1
Virt Host B1
SolMan Host
SLD
OS Info
OS Info
SAP Host
Agent
Diagnostics
Agent
Diagnostics
Agent
SAP Host
Agent
Enhances available landscape information in LMDB in SAP
Solution Manager
Support also products where no SLD data supplier is available
eg
Databases amp Operating Systems
Microsoft components
Is aware of virtualization through information from SAP Host Agent
Works completely automatic with Diagnostics Agents
SAP Solution Manager 71
LMDB
copy 2011 SAP AG All rights reserved 12
Landscape scenariosWhere to install an agent
PhyHost2 PhyHost3
VHost1 VHost2VHost3
PhyHost1
C1 C2C3 C4 C5 C6
cluster
1 diagnostics agent per managed
bdquohost‟ represented by a name
physical or virtual
1 SAP HostAgent per physical host
1 agent per host supports several
managed systems running on the
same named host
C7 C8
Diagnostics Agent
Managed ComponentSAP Solution Manager
SAP HostAgent
SAP Host
Agent
Diagnostics
Agent 1
SAP Host
Agent
Diagnostics
Agent 2
Diagnostics
Agent 4
Diagnostics
Agent 3
SAP Host
Agent
Diagnostics
Agent 1
H
D1
copy 2011 SAP AG All rights reserved 13
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 14
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 10
SAP Solution Manager 71
SLD amp LMDB
Solution Manager 71
Local SLD
(Not
required)
SLD1
(PI)
SLD2
(Data
Supplier)
SLD3
(NWDI)
SMSY LMDB
LMDB implications in 71
Flexible landscape database based on the
CIM data model
No local SLD required anymore but
supported
Full synchronization between Landscape
SLD‟s and LMDB
Automatic data migration from SMSY to
LMDB in the 71 upgrade where needed
for the respective Solution Manager
scenarios
copy 2011 SAP AG All rights reserved 11
SAP Solution Manager 71
Outside Discovery amp LMDB
Host B
Host A
DB
IIS
Virt Host A1
Virt Host B1
SolMan Host
SLD
OS Info
OS Info
SAP Host
Agent
Diagnostics
Agent
Diagnostics
Agent
SAP Host
Agent
Enhances available landscape information in LMDB in SAP
Solution Manager
Support also products where no SLD data supplier is available
eg
Databases amp Operating Systems
Microsoft components
Is aware of virtualization through information from SAP Host Agent
Works completely automatic with Diagnostics Agents
SAP Solution Manager 71
LMDB
copy 2011 SAP AG All rights reserved 12
Landscape scenariosWhere to install an agent
PhyHost2 PhyHost3
VHost1 VHost2VHost3
PhyHost1
C1 C2C3 C4 C5 C6
cluster
1 diagnostics agent per managed
bdquohost‟ represented by a name
physical or virtual
1 SAP HostAgent per physical host
1 agent per host supports several
managed systems running on the
same named host
C7 C8
Diagnostics Agent
Managed ComponentSAP Solution Manager
SAP HostAgent
SAP Host
Agent
Diagnostics
Agent 1
SAP Host
Agent
Diagnostics
Agent 2
Diagnostics
Agent 4
Diagnostics
Agent 3
SAP Host
Agent
Diagnostics
Agent 1
H
D1
copy 2011 SAP AG All rights reserved 13
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 14
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 11
SAP Solution Manager 71
Outside Discovery amp LMDB
Host B
Host A
DB
IIS
Virt Host A1
Virt Host B1
SolMan Host
SLD
OS Info
OS Info
SAP Host
Agent
Diagnostics
Agent
Diagnostics
Agent
SAP Host
Agent
Enhances available landscape information in LMDB in SAP
Solution Manager
Support also products where no SLD data supplier is available
eg
Databases amp Operating Systems
Microsoft components
Is aware of virtualization through information from SAP Host Agent
Works completely automatic with Diagnostics Agents
SAP Solution Manager 71
LMDB
copy 2011 SAP AG All rights reserved 12
Landscape scenariosWhere to install an agent
PhyHost2 PhyHost3
VHost1 VHost2VHost3
PhyHost1
C1 C2C3 C4 C5 C6
cluster
1 diagnostics agent per managed
bdquohost‟ represented by a name
physical or virtual
1 SAP HostAgent per physical host
1 agent per host supports several
managed systems running on the
same named host
C7 C8
Diagnostics Agent
Managed ComponentSAP Solution Manager
SAP HostAgent
SAP Host
Agent
Diagnostics
Agent 1
SAP Host
Agent
Diagnostics
Agent 2
Diagnostics
Agent 4
Diagnostics
Agent 3
SAP Host
Agent
Diagnostics
Agent 1
H
D1
copy 2011 SAP AG All rights reserved 13
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 14
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 12
Landscape scenariosWhere to install an agent
PhyHost2 PhyHost3
VHost1 VHost2VHost3
PhyHost1
C1 C2C3 C4 C5 C6
cluster
1 diagnostics agent per managed
bdquohost‟ represented by a name
physical or virtual
1 SAP HostAgent per physical host
1 agent per host supports several
managed systems running on the
same named host
C7 C8
Diagnostics Agent
Managed ComponentSAP Solution Manager
SAP HostAgent
SAP Host
Agent
Diagnostics
Agent 1
SAP Host
Agent
Diagnostics
Agent 2
Diagnostics
Agent 4
Diagnostics
Agent 3
SAP Host
Agent
Diagnostics
Agent 1
H
D1
copy 2011 SAP AG All rights reserved 13
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 14
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 13
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 14
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 14
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 15
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededRCA No
Monitoring Yes
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 16
Typical Agent Layout
SAP Solution Manager Host
SAP Solution
Manager 71
Wily
Introscope
Enterprise
Manager
DAA 98
SAP Host
Agent
SLD Host
SLD
J2EE
ABAP
Managed System Phyiscal Host 1
VHost1 VHost2
Enterprise Portal ERP
DAA 95
SAP Host
Agent
IS BC
Agent
DAB 96
IS Host Adapter IS Host Adapter
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 17
Preparing for InstallationUpgrade
Installation How Upgrade
Plan implementation of missing software components agent
and possible restarts for managed systemsMaster Guide
Plan implementation of missing software components agent
and possible restarts for managed systems
Plan user amp port availability Security Guide Plan user amp port availability
Check hardware prerequisites for SAP Solution Manager 71 Sizing Guide Check hardware prerequisites for SAP Solution Manager 71
Obtain the Installation Software
DVD‟s or
servicesapcoms
wdc
Obtain the Upgrade Software
Install SAP Solution Manager including support package
update
Inst Upgr
GuidesUpgrade to SAP Solution Manager 71
Update SLD Content to latest available version
Connect managed systems to SLDSWDC SDN
Update SLD Content to latest available version
Check the connection of managed systems to SLD
Install Diagnostics agent and SAP HostAgent on all managed
systems Inst Guides
Install Diagnostics Agent and SAP HostAgent on all managed
systems
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
servicesapcoms
wdc
Implement missinglatest software requirement on managed
systems (ST-API amp ST-PI)
Install Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
servicesapcoms
wdc + Guides
Upgrade Introscope Enterprise Manager
Install Diagnostics Agent and Host Agent on all Enterprise
Manager hosts
Perform configuration of SAP Solution Manager and managed
systems
SOLMAN_SETU
P
+ add guides
Perform configuration of SAP Solution Manager and
managed systems
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 18
Hardware pre-requisitesSizing Tool kit
SAP Solution Manager sizing Toolkit provides information on infrastructure
requirements including SAPs Memory Databases and Disk Spaces needed to
implement selected ALM scenarios for a set of Managed Systems
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 19
Check Prerequesites
Update SLD CR Content amp Model
LMDB requires some minimun version of the CR Content and the model installed in
at least one connected SLD
bull CR Content latest available
bull Model Version minimum 1616 better latest available
To check open SLD
httpsldhostsldportsld
Go to Administration Details Data
Check Note 669669 for further
information on CR Content amp Model
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 20
Check Prerequesites
Minimum SLD Versions
In order to be able to connect a SLD to the LMDB the SLD needs to have a
minimum version
bull SAP NetWeaver 640 ndash System Landscape Directory not supported
bull SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP1 for SAP NetWeaver 70 ndash System Landscape Directory not supported
bull EHP2 for SAP NetWeaver 70 ndash System Landscape Directory SP6 Patch 5
bull SAP NetWeaver 71 ndash System Landscape Directory SP9
bull EHP1 for SAP NetWeaver 71 ndash System Landscape Directory all SPs
bull SAP NetWeaver 72 ndash System Landscape Directory all SPs
bull SAP NetWeaver 73 ndash System Landscape Directory all SPs
If your central SLD is not on one of the required support package levels you
have to forward the data supplier information from your central SLD to a SLD
which fulfills the requirements Then connect this SLD to the LMDB (You can
also use the SLD on your SAP Solution Manager 71 system for this
forwarding)
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 21
Check Prerequisites
SAP Solution Manager Profile Parameters
Parameters Description Recommended value
abapbuffersize Program buffer size 500000
abapshared_objects_size_MB Size of Shared Objects Memory in MB 100
rsdbntabentrycount Number of nametab entries administrated 30000
rsdbntabftabsize Data area size for field description buffer 60000
rsdbntabirbdsize Data area size for initial records buffer 15000
rtbbbuffer_length Size of single record table buffers 60000
rsdbcuabuffersize CUA Buffer Size 10000
zcsatable_buffer_area Size of generic table buffer 100000000
zcsadb_max_buftab Directory entries in generic table buffer 10000
zcsapresentation_buffer_area Size of the buffer allocated for screens 20000000
sapbufdir_entriesMaximum number of entries in the
presentation buffer10000
rsdbobjbuffersize Size of exportimport buffer 50000
rsdbobjmax_objects Max no of exportingimporting objects 20000
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 22
Check PrerequisitesRFC Destination SAPOSS
SAP Solution Manager needs a working connection to the SAP support backbone
Check if RFC destination SAPOSS is working properly in SM59
If there are connection problems with SAPOSS check and maintain the connection settings in transaction
OSS1 the configuration changes will be adapted automatically
You can find detailed information
about transaction OSS1 and RFC
connection SAPOSS in SAP Note
17285
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 23
Check PrerequisitesS-User in SAP Service Market Place
Make sure that the S-User planned to be assigned to Solution Manager has the right
authorizations in SAP Service Market Place
Call URL httpservicesapcomuser-admin and log on to SMP
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 24
Check PrerequisitesSupport Package Levels
Ensure that all support package levels for the managing system (Solution Manager)
and the managed systems are up to date
The most important components on SAP Solution Manager are ST and ST-SER
The most important ABAP add-ons on SAP Solution Manager and in the managed systems are ST-PI and
ST-API see SAP note 539977 and 69455 for more details
Example Only
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 25
Check PrerequisitesOptional Client Copy
You can use the SAP delivered client 001 as productive client for SAP Solution
Manager
If you want to create an own productive client
Create a new client and perform a local client copy using profile SAP_ALL with 001 as the source client
and as the source client for users
Afterwards convert the Java UME to the new productive clientPlease ensure that you entered 001 as
ldquoSource Client User Mastersrdquo for your
client copy Without the standard Java
users from 001 the Java engine will not
start after converting UME
To convert the UME open the AS Java
User Management and change to
Configuration ABAP System
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 26
Installation amp Upgrade
Where To Find The Software
httpsservicesapcomswdc
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
Configuration of SAP Solution Manager using
SolMan Setup
Overview
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 28
SAP Solution Manager Configuration with
SOLMAN_SETUP
SAP Solution Manager 71 is configured using an Automatic Basic Configuration
Accessible via transaction code SOLMAN_SETUP
Allows an easy fast and step-by-step configuration of SAP Solution Manager
Single easy to use wizard for system
preparation amp basic configuration
Highly automated configuration
Integrated documentation for each
step
Easy access to open tasks and
postponed activities
Configuration of all managed systems
from one central entry point
Configuration of other scenarios like
Technical Monitoring Data Volume
Managementhellip
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 29
Automatic Basic Configuration UI components
Help Section
Provides detailed information
to each step such as what
needs to be done and what
will happen in the background
Activities
Lists all single activities
during each step along with
the documentation for the
IMG activity
Log
Shows detailed logs per
activity
Navigation
Guided procedure with all
steps for the basic
configuration
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 30
Automatic Basic Configuration Configuration Roadmap
Prepares the system for the configuration
Needs to be performed fully after a new installation
After patches and upgrades needed to update dialog and system users and assign
the appropriate default roles and to implement the appropriate Central Correction
Note (CCN)
System
Preparation
Configures the basic scenarios in SAP Solution Manager (Service Delivery Issue
Management Early Watch Alerts Maintenance Optimizer Root Cause Analysis hellip)
Needs to be performed after new installations and after support packages to perform
delta configuration
Overview screen tells you which configuration needs update
Basic
Configuration
Connection and configuration of managed systems
Sets up SAP Solution Manager Diagnostics to perform Root Cause Analysis on
SAP Solution Manager
Creation of Logical Components for managed systems
Managed
Systems
Configuration
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 31
SAP Solution Manager ConfigurationOverview Screen
The overview shows the status of the SAP Solution Manager configuration
Which steps of the configuration have been performed when and by whom
Which steps of the configuration needs an update
Check bdquoUpdate Needed
Flagldquo to see which
activities need to be
reperformed after a SP
update
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 32
The new roadmaphellip
hellipprovides detailed status information for each step of a guided configuration
scenario So you can decide if a step has been performed successfully or if a
reconfiguration is needed for a complete procedure
Step was
performed
successfully
Step was
performed with
errors (check and
reexecution
needed)
Step was
performed with
warnings (check
needed)
Step needs reexecution
because of changes in the
system (SP Update
configuration changeshellip)
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 33
SAP Solution Manager Configuration
System preparation New steps in 71
Automatic
Central
Correction
Note Check
Configuration
of needed
WebServices
Configuration
SLD amp LMDB
Connect
SMD agents
to Solution
Manager
Install and
configure
SAHostAgent
Configure
LMDB
Click on the box to get step details
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 34
SAP Solution Manager Configuration
Basic Configuration New steps in 71
CUA Support
for all users
Support for Introscope
Installation over
Diagnostics Agent amp
Introscope User
Management
Configuration of
MailSMS for
Solution Manager
notification
95 of steps
are now
automated
Click on the box to get step details
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 35
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Support for all technical system
types (incl selected 3rd party like
Websphere)
Technical Scenarios (multiple
systems like double stacks)
And standalone databases
Detailed Status overview
- RFC working
- Configuration status
- System well defined
- ST-API amp PI checks
Integration of LMDB
Technical System
maintenance
ABAPJAVA double
stack scenario are
automatically created
Click on the box to get step details
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 36
SAP Solution Manager Configuration
Managed Systems Configuration New steps in 71
Create and
check RFCs
for Managed
Systems
Assign
Diagnostics
Agents to
Server Name
All Users
managed by
the Wizard
CTS+ and
DBA cockpit
support
Click on the box to get step details
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
Configuration of SAP Solution Manager using
SolMan Setup
System Preparation
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 38
System Preparation Steps
The System Preparation consists of
the following steps
Create Users
Check Installation
Implement SAP Note
Configure ABAP
Configure Web Service
Prepare Landscape
Complete
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 39
System PreparationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles
Select the user you want to
create or update
You can create a new user or
update the authorizations of
an existing user
You can update the
authorization either
automatically or manually
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 40
System PreparationCheck Installation
This is an automatic installation check for configuration-relevant parts of the
installation
If a check status turns red check the Documentation for information on how to solve the problem
Repeat the check to make sure the problem is fixed
You can exclude checks by setting Execution Status to Postpone or Manual
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 41
System PreparationImplement SAP Note
In this step you can download and implement the central correction note (CCN)
The CCN comprises all corrections
for the configuration scenarios of
the basic configuration
You must implement the central
correction SAP Note manually with
the SAP Note Assistant (transaction
SNOTE)
Check the CCN for notes which
require manual activities
Perform the required manual
activities
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 42
System PreparationConfigure ABAP
In this step you automatically perform the following activities
Create the SAP Solution Manager system in the system landscape (transaction SMSY)
Create logical systems for the SAP Solution Manager
Activate the Service Data Control Center (SDCCN)
To avoid manual changes to the definition of the SAP Solution
Manager being overwritten in the System Landscape do not repeat
this step after having set up SAP Solution Manager
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 43
System PreparationConfigure Web Service
In this step you explicitly allow SAP Solution Manager to create web services using
the following authentication types
Basic Authentication
X509 Certificate Authentication
Ticket Authentication
The activity has to be performed manually as
described in the Documentation column
The link in the Navigation column lead you to
the Web Dynpro application SOA_MANAGER
there you can perform the required setting
Set the Execution Status to ldquoPerformedrdquo
afterwards
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 44
System PreparationPrepare Landscape
In the sub-steps of this step
you make SAP Solution Manager known to the system landscape
you make sure that all relevant information can be transferred from the system landscape to SAP Solution
Manager
Before configuring the SLD you need to consider the SLD Landscape Design Make sure that all systems are known
to the central (runtime) SLD
Important Do not use the local SLD in
SAP Solution Manager as runtime SLD
together with SAP NetWeaver PI or Web
Dynpro Java applications in your system
landscape
More information on SLD landscape design
httpwwwsdnsapcomirjsdnnw-sld
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 45
System PreparationSelect SLD
In this step you enable SAP Solution Manager to access to the System Landscape
Directory (SLD)
If SLDs exist specify all of them to which either managed systems or Diagnostics agents are connected
For the central SLD select the ldquoTarget of SAP Solution Manager DS ldquo field
If no SLD yet exists you can set up one in the SAP Solution Manager system automatically
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 46
System PreparationLogical Ports Creation
In this step you perform the following activities automatically and check the results
Create logical ports and end points for web services communication between the ABAP and Java stack of
SAP Solution Manager and between the Diagnostics agents and SAP Solution Manager
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 47
System PreparationPrepare Outside Discovery
In this step you prepare the connection of the systems in your landscape to SAP
Solution Manager
You install the agents on all hosts on which one
or more of the following systems is running
Managed system which should be connected
to SAP Solution Manager
CA Wily Introscope Enterprise Manager
Standalone database
Third party product not registered to an SLD
On each virtual host perform the following steps
Install Diagnostics Agent
On each physical host perform the following steps
Install SAPHost Agent
Establish trusted connection
On each physical host you need exactly 1 SAP
Host Agent
On each host (virtual or physical) you need 1
Diagnostics Agent
1 agent can support several managed systems
running on the same named host
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 48
Using a direct connection
to the message server
No additional configuration steps
necessary
Is primarily targeted for manual
rollout in small landscapes
Agent can be installed and
connection is available
instantaneous
Connecting Agents to the Solution ManagerAvailable connection options
Using the SLD connection
(Agent Candidate
Management)
Agent can be installed without
having access or credentials to the
Solution Manager system
Agent can be provided with new
connection data even when not
connected to the Solution Manager
system
Standard when agent is installed
together with SAP NetWeaver
based product
Connecting the agent to the
Solution Manager system can take
up to 30 minutes
Recommendation Connect the agent
during the installation directly to the
Solution Manager but also enable the
registration in SLD to be able to use the
extended connection features (available
with Diagnostics Agent 720)
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 49
Required Agent Versions
Diagnostic Agent
bull You can use any version of the Diagnostics Agent (already installed agents do not need to
be updated)
bull The agent applications are updated automatically from the Solution Manager
bull For new installations use the latest available version of the diagnostics agent from
httpservicesapcomswdc Browse Download Catalog SAP Technology Components SAP
SOLUTION MANAGER SAP SOLUTION MANAGER 71 Agents for managed systems
SAP Host Agent
bull You need to install at least patch level 55 of the SAP Host Agent 720
bull The installation files are available from httpservicesapcomswdc Support Packages and
Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP
HOST AGENT 720
bull This is installation procedure is described in SAP Note 1031096
It is recommended to enable the automatic update feature of the
SAP Host Agent so that you can update the Host Agent
centrally This is described in SAP Note 1473974
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 50
70 701 SR1 711 720 702 730
Integrated in NW DVDrsquos Yes Yes Yes Yes
Standalone Version available No Yes Yes Yes
JVM JDK 142 SAPJVM SAPJVM SAPJVM
Default System ID Instance SMD J98 DAA SMDA97 DAA SMDA97 DAA SMDA97
Support for SLD amp direct
connection (simultaneously)No No Yes Yes
SSL Support No No Yes Yes
SAProuter Support No No Yes Yes
SAP Host Agent neededNo (saposcol is
used)
Yes (manual
install)
Yes (auto
install)
Yes (auto
installed
updated)
Differences of the available Diagnostics Agent Versions
Recommended
for new installations
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 51
System PreparationConnect Diagnostics Agents via SLD
In this step you connect all necessary diagnostics agents to the Solution Manager
system which are using the SLD connection method
Select the SLD Server and click bdquoGet Agentsldquo to retrieve all agents from the selected SLD The list of
SLDbdquos is maintained in step 61
The agents of the following systems need to
be connected
Managed Systems
Introscope Enterprise Manager
Solution Manager itself (Self-Monitoring)
Select the agents you want to connect from
the list and click bdquoconnectldquo
The status of each agent indicates if the
connection data has been written
successfully to the SLD
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 52
System PreparationSet Up LMDB ndash Overview
In this step you can transfer system landscape data to the LMDB
The Landscape Management Database (LMDB) is used as a landscape repository for the Diagnostics
Infrastructure and the work center Technical Monitoring
Setup of LMDB
1 The central SLD provides data via a full content sync
2 Data is migrated from SMSY
Important The activation
can take a long time when
performed initially
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 53
System PreparationSet Up LMDB ndash Details 1
The default input values for the configuration wizard (suitable for most customers) is shown below
For the synchronization process you need a
user in the source (by default an SLD) with the
following authorizations
If the source is an SLD with a release as of
SAP NetWeaver 71 the user needs the role
SAP_SLD_CONTENT_SYNC
If the source is an SLD with a release SAP
NetWeaver 70 update the support package
stack to at least SPS 12 The user needs the
role SAP_SLD_GUEST
You can select the connection type (Remote or
Local) and the synchronization direction
(Unidirectional or Bidirectional)
If you set the Notification (YN) indicator the
source will synchronize with the target
whenever there is a content change in the
source The sources and the target
synchronize faster but at the expense of
higher network load
If the source is an SLD then the URL is
httpltSLD hostnamegtltSLD portgt
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 54
System PreparationSet Up LMDB ndash Details 2
The default input values for the configuration wizard (suitable for most customers) is shown below
The rank is a positive whole number which determines the ranking within a
synchronization landscape the higher the number the higher the ranking
For an SLD the standard
namespace is sldactive which you
should use if you have not created
your own namespaces
For an LMDB the standard
namespace is active which you
should use if you have not created
your own namespaces
The rank you enter here should
be higher than the rank of the
source
In the sixth step of the wizard (Summary) all settings and entries of the previous
steps will be displayed Choose the button Finish to add the new synchronization
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 55
System PreparationComplete
In this step the status of all steps of the System Preparation scenario is displayed
Log off the SAP Solution Manager and log on again with the Solution Manager administration user (default
SOLMAN_ADMIN) which you have created to start Basic Configuration
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
Configuration of SAP Solution Manager using
SolMan Setup
Basic Configuration
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 57
Basic Configuration
The Basic Configuration consists of
the following steps
Specify Project
Specify User amp Connectivity Data
Specify Landscape Data
Configure Manually
Configure Automatically
Complete
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 58
Basic ConfigurationSpecify Project
In this step you create a solution for the configuration of SAP Solution Manager
Additional a logical component for SAP Solution Manager and a Solution will be created
SAP Solution Manager automatically includes all production systems of your landscape which are known
to the solution and which are not already part of another solution This makes sure that
ndash You can perform Service Delivery for all production systems
ndash SAP EarlyWatch Alert is scheduled for all production systems
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 59
Basic ConfigurationSpecify User amp Connectivity Data
In the sub-steps of this step you make sure that SAP Solution Manager can be
connected to SAP and to other systems
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 60
Basic ConfigurationSpecify Connectivity Data
In this step you make sure that SAP Solution Manager can be connected to SAP
Service Marketplace
Enter the S-User that you created as a prerequisite for the SAP Solution Manager Configuration
The S-User for SAP Backend will be
maintained as the Solution Manager
user in the global settings of Solution
Manager and it will be used for the RFC
connections SAP-OSS and SAP-OSS-
LIST-O01
The S-User for Communication is the S-
User that will be maintained in
transaction AISUSER together with the
Solution Manager administration user
(default SOLMAN_ADMIN)
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 61
Basic ConfigurationSpecify SAP BW System
In this step you specify how the SAP Netweaver Business Warehouse (BW) is set
up
You can use the SAP Solution Manager productive client as BW client (recommended)
You can use another client of SAP Solution Manager as BW client to do that you need to perform an
additional client copy first
You can use the BW in a separate system in this case you have to make sure that
ndash The level of BI_CONT is always the same as in Solution Manager
ndash The BW works with the ldquoObsolete Concept with RSR Authorization Objectsrdquo
Recommendation To minimize the
effort to maintain users select Use
Standard SAP Solution Manager BW
environment This option assumes that
the BW is set up in the client you are
currently logged on to which is the
SAP Solution Manager productive
client See SAP note 1487626 for
more details
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 62
Basic ConfigurationSet Up Credentials
In this step you assign or create administrator users which can be used for further
automatic activities
Recommendation Use your previously created administrative user (default SOLMAN_ADMIN) as the
SAP Solution Manager administrator This ensures that the administrator has the required authorizations
Note If you have set up SAP
NetWeaver Business Warehouse (BW)
in a separate SAP Solution Manager
client or in a separate system you have
to create an SAP Solution Manager
administrator on the BW system or
update the role profile of an existing BW
administrator
You can use the ldquoTest Loginrdquo pushbutton
the test the credentials of your users
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 63
Basic ConfigurationCreate Users
In this step you have to create or update dialog and system users and assign the
appropriate default roles SAPSUPPORT enables Active Global Support to provide
support in the SAP Solution Manager system
SEP_WEBSERV user for the BMC Appsight License
Check Service in the Internet Communication Framework
(ICF)
CONTENTSERV user for services in the Internet
Communication Framework (ICF)
SMD_RFC and SMD_BI_RFC user for RFC
communication between the ABAP and Java stack of SAP
Solution Manager (also in BW client if BW is in a
separate clientsystem)
SAPSUPPORT and SMD_BI_RFC are created also in BW
client if BW is in a separate clientsystem
BI_CALLBACK user for communication from BW
clientsystem to productive client of SAP Solution
Manager
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 64
Basic ConfigurationSolution Manager Internal Connectivity
In this step you perform the following activities automatically and check the results
Create RFC connections between the ABAP and Java stack of SAP Solution Manager
Create the URLs for the web services and store the URLs in the configuration store of the Diagnostics
agents
Attention You have to reperform this step
each time you change the users created in the
previous step
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 65
Basic ConfigurationSpecify Landscape Data
In the sub-steps of this step you set up of CA Wily Introscope Enterprise Managers
and you enable SAP Solution Manager to send notifications via e-mail and SMS
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 66
Basic ConfigurationConfigure CA Wily Introscope ndash Prerequesites
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers
or you can install an additional Enterprise Manager using an already installed diagnostic agent
Important prerequesites
- In the System Preparation scenario
you have installed and connected
Diagnostics agents on all hosts of
your CA Wily Introscope Enterprise
Managers (EM)
- You need to ensure that the
Diagnostics Agent user
(smdadmdaaadmSapServiceDAA)
has read write access to the
Introscope installation directory
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 67
Basic ConfigurationConfigure CA Wily Introscope ndash Connect existing Wily EMs
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can connect existing CA Wily Introscope Enterprise Managers by discovering an existing installation
You need to assign a connection user to each CA Wily Introscope Enterprise Manager
ndash By default the administration user of the CA Wily Introscope Enterprise Manager is assigned as the
connection user
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 68
Basic ConfigurationConfigure CA Wily Introscope ndash Install a new Wily EM
In this step you connect CA Wily Introscope Enterprise Manager to SAP Solution
Manager
You can install additional CA Wily Introscope Enterprise Managers if the capacity of existing ones would
be exceeded
Typically CA Wily Introscope Enterprise Manager are installed as standalone collector nodes
In complex system landscapes several CA Wily Introscope Enterprise Managers (collector nodes) can
be assigned to a Manager of Managers (MoM)
Prerequisite for installation
You need to download the Introscope
Installation files as well as the OSGI
and Eula files and place them in a
directory which is accessible to the
agent which should install the new
instance
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 69
Basic ConfigurationConfigure SAProuter
In this optional step you can allow SAP Solution Manager to access the permission
table saprouttab on the SAProuter server via FTP
You do not need to maintain the permission table manually
Caution Unsecured data
transfer is used to maintain
the saprouttab The
saprouttab permission table
is security-relevant If you
allow access via FTP FTP
user names and passwords
are transmitted
unencrypted
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 70
Basic ConfigurationConfigure SAPconnect
In this step you set up the infrastructure which enables SAP Solution Manager to
send notifications via e-mail and SMS
Node field enter the name of the SMTP node which
handles outgoing e-mail
Host field enter the name of your mail server
Port field enter the port number at which your mail
server can be accessed
SMTP Active field enable SAP Solution Manager to
send notification via e-mail
FaxPager Active field enable SAP Solution Manager
to send notification via SMS
Domain field enter the domain name of your
organization if you want to restrict the scope of
possible recipients
Recommendation Choose the default
value to ensure that notifications can
be sent to any domain
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 71
Basic ConfigurationConfigure Manually
In this step you have to perform some manual activities in the Solution Manager
Every activity has an IMG documentation were you can find details on what has to be done during the
activity
Maintain logical systems
in transaction SCC4
Specify Transaction Type for Incidents
Configure Service Content Update
Generate entries in extraction framework
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 72
Basic ConfigurationConfigure Automatically
In this step some automatic activities are performed by SAP Solution Manager
If the security regulations of your organization require you to do so you can perform the activities
manually or you can postpone the automatic configuration activities
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 73
Basic ConfigurationComplete
In this step the status of all steps of the Basic Configuration of your SAP Solution
Manager system is displayed
To make yourself familiar with the functions now available in SAP Solution Manager choose the Go to
SAP Solution Manager Demo Launch Pad link
To connect systems to SAP Solution Manager choose the Go to Managed Systems Configuration link
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
Configuration of SAP Solution Manager using
SolMan Setup
Managed System Configuration
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 75
Managed Systems Configuration
The Managed System Configuration
consists of the following steps
Select Product
Check Prerequisites
Connect Managed System
Assign Diagnostics Agent
Enter System Parameters
Enter Landscape Parameters
Configure Automatically
Configure Manually
Create Logical Components
Check Configuration
Complete
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 76
Managed Systems ConfigurationConfiguration of a managed system
With the Managed Systems Configuration you connect systems to SAP Solution
Manager
To configure a single system choose the Technical System tab page
To configure a double (ABAP and Java) stack system choose the Technical Scenario tab page
ndash Technical scenarios need to be created manually first
To configure a standalone database choose the Database tab page
If the system that you want to connect is not contained in the technical system list connect the system to an
SLD to minimize the effort for maintenance
If required create the technical system manually For more information see SAP Note 1472465
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 77
Managed Systems ConfigurationStatus Overview
In the Managed Systems Configuration you have the following options
Check the status via the traffic lights next to the managed system
ndash RFC Status (only ABAP) indicated the RFC connection status
ndash Auto Configuration Status indicates the status of the auto configuration step of the managed system
configuration
ndash Plug-in Status (only ABAP) indicates if the ABAP add-ons ST-PI and ST-API are on the fulfill the
version requirements in the managed system
Via the bdquoShow Detailsldquo link you can show detailed status information on the selected system(s) in SAP
Solution Manager
To change the information about technical systems and scenarios select the system or scenario and click
on the ldquoSystem Operations Maintain System or Scenario Operations Maintain Scenariordquo button
Via the ldquoConfigure SystemScenarioDatabaserdquo button you open a guided procedure to perform the
configuration that connects the technical system technical scenario or database to SAP Solution Manager
Via the ldquoExportrdquo button you can export the list to Microsoft Excel
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 78
Managed Systems ConfigurationCreate Technical Scenarios
To configure a double stack system it must be maintained as Technical Scenario
Technical scenarios group ABAP Java and databases that belong together logically
To create a technical scenario choose ldquoCreate Scenariordquo push button on the ldquoTechnical Scenariosrdquo tab
1 Make sure that all needed technical
systems hellip
2 hellip and the database are known to
SAP Solution Manager
3 Create a new scenario
4 Maintain name type and description
of the technical scenario
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 79
Managed Systems ConfigurationCreate Technical Scenarios
5 Select technical systems hellip
6 hellip Review your entries and save
7 To delete a scenario enter the Technical
Scenario Wizard under the Related Links
section of the Solution Manager
Administration Workcenter
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 80
Managed Systems Configuration Roadmap Overview
The roadmap of the managed system configuration is dependent on the type
product of the selected managed system scenario or database
To get more information about the selected system scenario choose the Technical
System Details link in the roadmap
Database only
J2EE system
Dual stack system
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 81
Managed Systems Configuration Select Product (12)
In this step you define which product is used for the diagnostics configuration
Based on this selection the appropriate extractors are scheduled
To find out the correct product versions and main
instances see SAP Note1472465
1 Select the technical system
2 Choose the Edit Products
pushbutton
You go to the Technical
System Editor screen
3 On the Product Instances tab
page choose the Add
pushbutton to select the
applicable product version
and product instance
4 Save and exit
5 Repeat steps 1 - 4 for all
technical systems
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 82
Managed Systems Configuration Select Product (22)
In this step you create a product system
Based on this selection the usage of the system in logical components and solutions is determined
1 Select the technical system
2 Choose the Goto
Landscape Verification
Wizard pushbutton
3 Landscape Verification Wizard ndash Create the Product System and assign Technical System
Alternative Create Product Systems with the Edit Product Systems pushbutton to call SMSY
Transaction in ABAP Stack
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 83
Managed Systems Configuration Check Prerequisites
In this step you automatically check the prerequisites for the configuration of SAP
Solution Manager
Diagnostics Prerequisites Depending on the version of SAP Solution Manager and the version of the
managed system a minimum version for different software components need to be provided
Fetch system from LMDB to SMSY This activity ensures the consistency of ABAP systems between
SMSY and LMDB The selected ABAP system is transferred from LMDB into SMSY
To perform the configuration activities
automatically choose Execute All
In the Log screen area the system
displays messages for the selected
prerequisites check
To perform the configuration activities
manually do the following
In the Documentation column
choose the Display link
To perform the activity choose
the link in the Navigation column
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 84
Managed Systems Configuration Connect Managed System
In this step you create RFC connections to each managed system
For each managed system you have to create at least one READ RFC connections to any client
Additionally you activate the Service Data Control Center (SDCCN) in the managed system
Login Destination access with logon screen
Trusted Destination without additional authentication
Prerequisites user exists in both systems with
authorization object ldquoS_RFCACLrdquo
In the Clients and existing RFCs screen area select the
client you want to connect
Select the RFCs to be created
Mandatory RFC Destination and User for Read
Access To enable basic SAP Solution Manager
functions you are required to explicitly allow read
access
Recommended TMW Destination and User for Change
Manager enables change requests
Optional RFC Destination for Solution Manager
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 85
Managed Systems Configuration Assign Diagnostics Agent
In this step you assign the diagnostics agents to the managed systems
You assign a diagnostics agent to each server (virtual host) on which the managed system is running
If the applicable diagnostics agent is not displayed in the list choose the SLD Agent Candidates tab
page select the applicable agent from the list and choose the Connect pushbutton
1 On the Agent Assignment tab page select a server
2 Choose the Assign pushbutton and select the
applicable agent from the list
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 86
Managed Systems Configuration Enter System Parameters
In this step you specify all system parameters required to configure the managed
system
The parameters to be specified
depend on the type of
managed system you
configure for example ABAP
Java database systems
To display help on how to enter
a value you do the following
Position the cursor on the
field
In the context menu select
Display Quick Help
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 87
Managed Systems Configuration Enter Landscape Parameters
In this step you verify or add landscape parameters
Attention To avoid time-consuming error search verify the landscape parameters carefully
In the Landscape Objects hierarchy check the status of each parameter
ndash The status is set to No Parameters No input required
ndash The status is set to Default used Verify the parameter
ndash The status is set to Input missing Enter the parameter
ndash The status is set to Agent offline Restart the diagnostics agent
To change or enter values choose the parameter in the Status column
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 88
Managed Systems Configuration Create Users
In this step SAP Solution Manager creates the users in the managed system needed
for connection and support
Select user from the list
Select Action
ndash Create new user
ndash Update authorizations of existing
user
ndash Provide existing user
Choose Execute
SAPSUPPORT
SMDAGENT_SI7
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 89
Managed Systems Configuration Configure Automatically
In this step SAP Solution Manager performs automatic configuration activities
To start automatic configuration choose the Execute All pushbutton
Note The automatic execution of the configuration activities can take a few minutes
After the configuration messages and other detailed information for a selected automatic activity are
displayed in the Log screen area
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 90
Managed Systems Configuration Configure Manually
In this step you perform manual configuration activities
Maintain SAPRouter data maintain the SAProuter data for the managed system in the Service Market
Place to open the service connection for the maintenance case
Adjust HTTP Log Parameter set parameter to enable the analysis of logs written by the Internet
Communication Manager
Activate Flight Recorder set the parameter for J2EE based systems to collect data also in case the J2EE
system is crashing
Restart of the Java stack is required to enable Wily metric collection
In the Documentation column choose the Display link
To perform the activity choose the link in the Navigation column
Follow the instructions in the documentation
In the Execution Status column select Performed
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 91
Managed Systems Configuration Create Logical Components
To use your system in solutions and projects you assign the selected system to one
or more logical components in this step
Depending on the product version of the selected system usable logical components are displayed
You can assign the system to an existing logical component by selecting system and client in the
respective column
You can also create a new logical component by choosing the New Logical Component pushbutton
To save you entries choose Save in the navigation bar
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 92
Managed Systems Configuration Check Configuration
In this step you automatically check whether the system is configured correctly and
you update the statuses in the overview of the Managed Systems Configuration
If you have errors in one of the checks please check the details in the log area
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 93
Managed Systems Configuration Complete
In this step the status of all steps of the Managed Systems Configuration of your
SAP Solution Manager system is displayed
Now you can start using Work Centers
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
copy 2011 SAP AG All rights reserved 94
Additional Information
Application Lifecycle Management with SAP Solution Manager
httpservicesapcomalm
SolMan_Setup Wiki in SDN
httpwikisdnsapcomwikidisplaySMSETUP
Solution Manager Authorizations Wiki in SDN
httpwikisdnsapcomwikidisplaySMAUTH
Guides for SAP Solution Manager (Master Guide Installation Guides Upgrade Guides Security Guides Sizing Toolkit hellip)
httpservicesapcominstguides SAP Solution Manager Release 71
Where to get the software
httpservicesapcomswdc Installation amp Upgrades A-Z Index SAP Solution Manager SAP Solution Manager 71
Thank You
Thank You