You are on page 1of 4

SOLMAN Managed System Checklist

1. SAP Solution Manager Setup

2. Home
 Creado por Michael Kloeffer, modificado por última vez por Olivier MONTABERT el dic 12, 2016

Required Actions

Remind to comply with the prerequisistes applicable to both the SAP Solution Manager system and the managed systems -
depending on your release:

 SAP Solution Manager 7.1 : SAP note 1478974 - Diagnostics in SAP Solution Manager 7.1
 SAP Solution Manager 7.2 : SAP note 2248724 - Root Cause Analysis in SAP Solution Manager 7.2

Here below, find an overview of the usual work packages to be addressed.

Work Package Activity Valid More Information
Connect Managed All managed systems must be connected to SLD before
System to SLD starting the configuration
Maintain transaction RZ70. ABAP Connect Managed Systems to
Maintain Visual Administrator - SLD DS Configuration. J2EE Connect Managed Systems to
Plan port Establish network connectivity between the managed ALL Refer to user
availability system landscape and the managing landscape. ID MANAGED.ABAP.ADMIN
(Network/Firewall) see chapter 13.5 - Required
TCP/IP Ports
Plan user Users & Authorizations are needed as a prerequisite before ALL SAP Solution Manager guides
availability starting the managed system configuraton. Required Users / Operations / Security Guide
(User/Security) can be created automatically using the managed system
setup, however due to security reasons it can be necessary
to create these users manually beforehand
For automatic user creation an administration user on the SAP Solution Manager guides
managed system is required / Operations / Security Guide
Refer to user
For manual user creation, the following users are needed SAP Solution Manager guides
on the managed system and need to be created before the / Operations / Security Guide
execution of the managed system configuration: Refer to user ID mentioned on
 Technical Users for RFC - Connections READ and TMW the users in brackets to find
[MANAGED.ABAP.RFC] which roles and
 Technical User SM_COLL_<SIDof SolMan> authorizations are needed
 Technical User SMDAGENT_<SolManID> for Wily Host
 Dialog User for SAPSUPPORT
 Database User SAP<SID>DB [MANAGED.DB.USER] (is
created during the setup of the managed system, but
needs to be known for the DBA cockpit connection)
In order to create the BACK RFC destinations from the
managed system to the SAP Solution Manager system, the
following user is needed: Technical User for RFC -
connection BACK
RFC connectivity Normally, the RFC connections from the SAP Solution ABAP SAP Solution Manager guides
Manager to the managed system are created during the / Operations / Security Guide
managed system setup with SOLMAN_SETUP. If this is not
possible for any reason, you must create these RFC
Agents The rollout of the Agents is also a prerequesite for the
Managed Systems Configuration, as indciated below. The
Agents can be installed manually or automatically.
Diagnostics ALL
Determine where to install a Diagnostics Agent SAP Note 1365123 - Agent
Installation Strategy
Diagnostics Agents in HA environments Diagnostics Agent and HA
Manual installation of Diagnostics Agents SAP Note 1833501:
Diagnostics Agent - Installer
Versions: section "Installer
Notes" => "Current"
illustrated tours are available
 Installation of a Diagnostics
 Uninstallation of a Diagnostics
Automated installation of Diagnostics Agents SAP Note 1833501:
Diagnostics Agent - Installer
Versions: section "Mass
Deployment Notes" =>
[Relevant only with SAP Solution Manager 7.1] Setup Certificate Based
Enable certficate based authentication of Diagnostics Authentication for Diagnostics
Agents Agents
Install SAP Host Agent Install SAP HostAgent
SAP Note 1031096 - Installing
Enable central update of SAP Host Agent SAP Note 1473974- Automatic
Update of SAP Host Agent
Enable trusted connection between SAP Host Agent and Enable trusted connection
Diagnostics Agent
Plugins Implement latest plugins (ST-A/PI & ST-PI) ABAP
Plan restart During the execution of the managed system setup for J2EE
J2EE system, the Introscope Byte Code Adapter gets
deployed and a restart of the managed system is needed.
As it is not absoluetly necessary that this restart happens
during the configuration, it should be planned in advance.


To allow more efficient tracking, you can use the following checklist Managed System Setup Checklist.xlsx