You are on page 1of 7

GettingStarted Newsletters























Part 1:
Solution Manager 7.2 Installation and Configuration I Installations
Part 2:
Solution Manager 7.2 Installation and Configuration II Configurations
Part 3: Solution Manager 7.2 Installation and Configuration III Changes from 7.1 to 7.2
Part 4:
Solution Manager 7.2 Installation and Configuration IV Managed System Config General Info
Part 5:
Solution Manager 7.2 Installation and Configuration V Managed System Config ABAP System

I want to give some general information about the related components for managed system configuration.

Let me start with the general architecture of Solution Manager, then list the components of the architecture
and give some details and related links.

Technical Architecture of Solution Manager

Indeed, I searched many pages, presentations through internet but I could not find a figure that reflects my
mind's figure for Solution Manager and Managed Systems.
I tried to figure it out like below.

More detailed technical overviews can be seen in Technical Infrastructure link according to scenarios of
the Solution Manager. The data flow, ports, users are defined in detail.
There is also a pdf document about the infrastructure information (Technical Infrastructure) that you can

We have below components related to managed system configuration on Solution Manager and Managed
Systems landscape;
Solution Manager (ABAP + Java Instances)
Managed System (ABAP, Java, Dual Stack, BOBJ, etc)
Software Provisioning Manager (SWPM)
SM Diagnostic Agent (SMD)





Introscope Enterprise Manager (IEM)

Introscope Java Agent
Support Tools (ST* Plugins)
System Landscape Directory (SLD)
Landscape Management Database (LMDB)
Extractor Framework
Solution Manager Busines Warehouse
SAP Support Backbone

First three blogs were about the Solution Manager so I will not give details again here.
The next blogs will be about the configurations of ABAP, Java, BOBJ, HANA etc managed systems so I will
not mention about them here either.

Here are the short descriptions of the other components and some useful links about them.

Software Provisioning Manager (SWPM)

Software Provisioning Manager offers relevant system provisioning procedures to install, copy, and
transform SAP systems in your landscape.
We use SWPM for installation of systems and especially SM Diagnostic Agents.

You can chek link Overview Software Provisioning Manager 1.0 for detailed overview.
You can download the tool itself, the Kernel for the tool the documentation from this link.
Central Release Note for SL Toolset 1.0 is SAP Note 1563579.
Help page for the tool is Software Logistics Toolset (SL Toolset)
Demo for Software Provisioning Manager 1.0.

SM Diagnostic Agent (SMD)

Normally SMD Agent is optionally installed when you are installing the SAP System.
I recommend to install the latest version of the tool before carrying out the managed system config.
So if it is installed with the SAP system together check whether it is the latest version. If it is not
uninstall the existing one using SWPM firstly and then reinstall the latest version.

Check the notes and wiki pages for the currnet information
1833501 Diagnostics Agent Installer Versions
1365123 Installation of Diagnostics Agents
Concerning Diagnostics Agents always pay attention to the 6 essential rules, as described in the
attached "AgentInstallationStrategy.pdf" document.
Note: Further details on recommended SAP Host Agent and SWPM versions, as well as existing
Diagnostics Agent maintenance procedures are available in the SCN wiki: "Diagnostics Agent
Maintenance Procedures.


SAP Host Agent is installed automatically when you install an SAP system.
You should keep this component also in the latest version.
You can use auto upgrade feature of the component.
Her is a figure of SAP Host Agent architecture. Saphostexec, saphostctrl services are the main
programs for the component.

Check the notes and wiki pages for detailed information

Have UpToDate SAP Host Agents
1031096 Installing Package SAPHOSTAGENT
1473974 Using the SAP Host Agent Auto Upgrade Feature

Introscope Enterprise Manager (IEM)

Introscope is an application management solution created to manage Java application performance.
The Right to View (RTV) version of CA Introscope is a restricted, readonly form of the full product and

is bundled with SAP Solution Manager.

The Enterprise Manager is typically installed on the Solution Manager host. Alternatively, you can
install the Enterprise Manager on a separate host.
You can find detailed information about the installation of Introscope Enterprise Manager in blog
Part 2.

Check the note and wiki page for detailed information

797147 Introscope Installation for SAP Customers

Introscope Java Agent (on managed systems)

The setup of the Java agent is typically done centrally via the managed setup in Solution Manager.
After activation by restarting the Java VM, the agent runs within the Java process of the monitored

HostLevel Introscope Agent (on the managed systems) The socalled Introscope Host Adapter
runs as part of the Diagnostics Agent in the Diagnostics Agent process to collect data on operating
system level, e.g., from saposcol, GC logs, ABAP instances, and TREX. The host adapter generates less
load on the Enterprise Manager than a normal agent.
Wiki for Introscope Host Adapter.

Support Tools (STPI and STA/PI)

We see these plugins on EWA reports as seen below. In order to have better service you should keep
these plugins up to date on managed systems.

Solution Tools PlugIn STPI : This addon or plugin contains Service Data Control Center (SDCCN)
that controls the data collection and transfer of analysed data for a service session.
Service Tools for Applications PlugIn STA/PI: This plugin contains applicationspecific data
collectors providing data to SDCCN. It has also service preperation check RTCCTOOL feature.
Check the notes and help page for detailed information
539977 Release strategy for addon STPI
69455 Servicetools for Applications STA/PI (ST14, RTCCTOOL, ST12)

System Landscape Directory (SLD)

The System Landscape Directory of SAP NetWeaver (SLD) serves as a central information repository
for your system landscape. A system landscape consists of a number of hardware and software
components that depend on each other with regard to installation, software updates, and demands on
SAP Systems inside a landscape report data automatically to the SLD.
The figure below shows the flow of data between the SLD and other components.

As it can be seen above figure component information is provided by SAP. It is recommended that you
always use the latest version of SAP CR Content. The note 669669 Update of SAP System Component
Repository in SLD can be used for details.
Check below help document, blogs, presentation and pdf document for detailed information
System Landscape Directory (
System Landscape Directory (SLD) (blog)
SCN blogs and docs on SLD and LMDB (blog)
System Landscape Directory of SAP Netweaver by Boris Zarske (presentation)
Planning Guide System Landscape Directory (pdf document about the details, topologies etc. )

Landscape Management Database (LMDB)

The Landscape Management Database (LMDB) is an index of the elements in a system landscape.
LMDB uses the SAP enhancement of the Distributed Management Task Force (DMTF) Common
Information Model (CIM) to describe the landscape elements, analogously to the System Landscape

Directory (SLD). Typical model elements are computers, systems, products and software
LMDB was introduced in SAP Solution Manager 7.1, and is required since then.

Useful links about LMDB;

Documentation for Landscape Management Database LMDB (For a list of system landscape
management documentation)
Guidance to Best Practices in SLD and LMDB
SLDLMDB Topology Connections, Valid, and Invalid Data Exchange Between SLD and LMDB of SAP
Solution Manager
Landscape Management Database (LMDB)
Landscape Management Database (LMDB) FAQ

Extractor Framework (EFWK)

Below short overview of EFWK is taken from EFWK_Home > EFWK_OVERVIEW.
The picture below shows the high level architecture of the EFWK.

On the left side you find the different data sources for the extractors. Extractors dont only run in
Solution Manager, but also in the managed systems. Usually extractors are functions in function
modules (mainly shipped with STPI and STA/PI for ABAP) or part of the aglets of the diagnostics

There are links on mentioned wiki pages about Setup & Administration, How Tos, Troubleshooting,
Frequently Asked Questions (FAQ) of EFWK.

Solution Manager Busines Warehouse

E2E Monitoring and Alerting Infrastructure (MAI) data is put in the SAP Solution Manager BW by the
Extractor Framework (EFWK), and in particular, the Alerting Framework. No process chains and
DataSources are used, the data is written directly to DSOs by extractors.
BI Content for SAP Solution Manager

Mostly BW data is kept in Solution Manager System but you can use external BW system for this
purpose. When the mandatory configuration is done most of the BI structures are activated and
infocubes, dsos, web templates are generated. There could be errors in extractors that are pointing to
not generated BI objects. EWA reports for BOBJ, Java systems can also refer these kind of errors.

SAP Support Backbone

Support Backbone integrates the SAP Solution Manager, the SAP Service Marketplace, and the SAP
service infrastructure. Integration includes access to support processes and tools, which both SAP
Support staff and SAP partners can access.
You use wizards to set up service connections to SAP for the managed systems in your solution. You
open a service connection for a specified period so that a member of SAP Support staff can log on to
your system and provide support directly.

Managed System Configuration of an ABAP, Java, BOBJ and HANA Systems are coming next.

Thanks for your interests.