SAP Solution Manager Setup
Page tree
Skip to end of metadata
Go to start of metadata

Convergent Mediation 4.x

All scenarios in SAP Solution Manager depend on the correct modelling of system information in the landscape databases. In a typical scenario, the technical system automatically reports information about itself to the productive SLD. As of SAP Solution Manager 7.1 and higher, technical system information from ideally one or several SLDs is synchronized with the new Landscape Management Database (LMDB).
Ususally, the technical systems report installed product versions and product instances (available with newer SAP NetWeaver installations) to the LMDB.
If no product versions and product instances are reported, this page shows you how to model different products in the LMDB of SAP Solution Manager.
Some very specific examples of product modeling are described in the guide Special Cases in Installation and Upgrade (adding Portal content to SAP NW, SAP SEM, update to SAP NW 7.3 hub, IDM ...).

  • SAP Solution Manager 7.1 and 7.2:

Generic Maintenance Information for Technical Systems in SAP Solution Manager 7.1 and 7.2

When talking about system in the context of SAP Solution Manager, you have to distinguish between Technical Systems and Product Systems. The term Technical System describes an entity that is installed standalone or as cluster on one or several hosts in order to get a an application running. It is more or less a technical description of the installation.
To operate any system landscape maintenance, with SAP Solution Manager 7.1, you model also so called Product System, representing the complete product that has been installed. It consists of one or more Technical Systems assigned via the relevant product instances. In the LMDB, product instances are marked as installed on technical systems. Then you can assign technical systems and product systems to product systems. With SAP Solution Manager 7.2 the Product Systems are no more relevant. Instead you shall define so called maintenance dependencies, using the maintenance planner within the SAP Support Portal. Find more information about system landscape maintenance planning here.

The focus of this Wiki is to provide the information how to maintain Technical Systems correctly.

For more information, see:

Use transaction LMDB in the SAP Solution Manager system for a direct access of the technical system or product system editors.

Generic Rules for Product Assignment

As general rule you should first check in the products section regarding the product you want to set up with your Technical System. Depending on the fact whether the affected Technical System has been created automatically via SLD content synchronization to Solution Manager or manually there are different rules for product assignment. Here is a rough overview by supported system type and how Technical Systems of each type need to be created with or without product information:

  • Application Server ABAP: Technical Systems are created automatically via SLD content synchronization. For Technical Systems running on a Netweaver version prior 7.02 the product version and product instance information is not provided and need to be added with the Managed System Setup. In case the SAP Solution Manager has been upgraded from version 7.0 to 7.1 and the affected ABAP system has been created during the data migration from SMSY the product information need also to be added manually in the Managed System Setup.
  • Application Server Java: Technical Systems of type Application Server Java are also created automatically via SLD content synchronization. Similar to type AS ABAP the product version and product instance information need to be maintained manually for all Technical Systems running on Netweaver prior 7.02.
  • Apache Tomcat Server: For this system type exists an SLD data supplier. Depending on the application and its version the product version, product instance and software component version information is also provided with SLD content synchronization.
  • Business Objects Cluster: All Technical Systems of type Business Objects Cluster are created via SLD data supplier and synchronized to the Solution Manager LMDB containing the complete set of product information.
  • liveCache: For releases 640 SPS23, 700 SPS17, 701, 702, 710 SPS07 and higher the Technical System is created automatically but the product information need to added during the Managed System Setup. For lower releases the complete Technical System has to be created manually with the Technical System Editor.
  • Master Data Management Server: All Technical Systems of type Master Data Management Server need to be created manually including the installed software information.
  • Microsoft Internet Information Services: The Technical System is created automatically in the LMDB but the product information need to be added manually during the Managed System Setup.
  • .Net System: Depending on the application the Technical System is created automatically including the product information or need to be created manually with the Technical System Editor
  • TREX System: For TREX systems a data supplier exists but it is necessary to maintain the product information.
  • Unspecific Standalone Application System: Unspecific Standalone Application System type is used for those Technical Systems which are not described by any of the other types and can exclusively installed on a single host without any clustering. Depending on the application the Technical System is created automatically including the product information or need to be created from scratch with the Technical System Editor.
  • Unspecific Cluster System: Technical Systems which are not described by any of the other system types and could be installed in a cluster need to be created as type Unspecific Cluster System. Similar to the type Unspecific Standalone Application System they are created automatically via SLD data supplier including all product information or need to be created manually.
  • Web Dispatcher: Web Dispatcher systems are created automatically via SLD data supplier but the product information need to be enhanced during the Managed System Setup.
  • IBM WebSphere Cell: The Technical System is created automatically via SLD data supplier and synchronized to the Solution Manager and depending on the application running on WebSphere it is necessary to maintain the product information during the Managed System Setup.

SAP Product and Solutions

SAP Solution Manager

Supported Versions?

SAP SOLUTION MANAGER 7.0, SAP SOLUTION MANAGER 7.0 EHP 1,
SAP SOLUTION MANAGER 7.1, SAP SOLUTION MANAGER 7.2

Automatic creation of Technical System?

Yes
Two Technical Systems are created - Application Server
ABAP and Application Server Java

Automatic entry of installed software?

Partly
For both Technical Systems installed software components
are provided automatically but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP SOLUTION MANAGER 7.0

Solution Manager ABAP Stack

AS ABAP

Yes



Solution Manager JAVA Stack

AS Java

Yes


SAP SOLUTION MANAGER 7.0 EHP 1

Solution Manager ABAP Stack

AS ABAP

Yes



Solution Manager JAVA Stack

AS Java

Yes


SAP SOLUTION MANAGER 7.1

Solution Manager ABAP Stack

AS ABAP

Yes



Solution Manager JAVA Stack

AS Java

Yes


SAP SOLUTION MANAGER 7.1 on HANA
(* restricted availability)

Solution Manager ABAP Stack

AS ABAP

Yes



Solution Manager JAVA Stack

AS Java

Yes


SAP SOLUTION MANAGER 7.2

Solution Manager ABAP Stack

AS ABAP

Yes

Solution Manager JAVA Stack

AS Java

Yes
SAP NETWEAVER 7.X Application Server JavaAS JavaYesSome AS JAVA based extractors (e.g. CONFIGURATION (CENTRAL TECHNICAL CONFIGURATION)) will not be scheduled if "SAP NETWEAVER 7.X - Application Server Java" is not flagged as 'Diagnostics-relevant'.

Enterprise Portal

Supported Versions?

SAP NETWEAVER 04, SAP NETWEAVER 7.0, SAP EHP1 FOR SAP NETWEAVER 7.0

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server Java

Automatic entry of installed software?

Partly
Installed software components
are provided automatically but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP NETWEAVER 04

Enterprise Portal

AS Java

Yes


SAP NETWEAVER 7.0

Enterprise Portal

AS Java

Yes


SAP EHP1 FOR SAP NETWEAVER 7.0

Enterprise Portal

AS Java

Yes


CRM

Supported Versions?

SAP CRM 4.0, SAP CRM 5.0, SAP CRM 5.2,
SAP CRM 2007, SAP CRM 7.0, SAP CRM 7.0/NW7.01, EHP1 FOR SAP CRM 7.0

Automatic creation of Technical System?

Yes
Two Technical Systems are created - Application Server
ABAP and Application Server Java

Automatic entry of installed software?

Partly
For both Technical Systems installed software components
are provided automatically but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP CRM 4.0

CRM Application Server ABAP

AS ABAP

Yes



CRM IC Webclient_640

AS Java

Yes

Produc Instances to be selected on
system type AS Java are dependent on CRM scenario


CRM ICS WFM CS_640

AS Java

Yes



CRM Intelligence Connector_640

AS Java

Yes



IPC Web Applications_640

AS Java

Yes



E-Selling_640

AS Java

Yes



CRM_ICSS_640

AS Java

Yes


SAP CRM 5.0

CRM Application Server ABAP

AS ABAP

Yes



CRM Application Server Java

AS Java

Yes



Mapbox

AS Java

Yes


SAP CRM 5.2

CRM Application Server ABAP

AS ABAP

Yes



CRM Application Server Java

AS Java

Yes


SAP CRM 2007

CRM Application Server ABAP

AS ABAP

Yes



CRM Application Server Java

AS Java

Yes


SAP CRM 7.0

CRM Application Server ABAP

AS ABAP

Yes



CRM Application Server Java

AS Java

Yes


SAP CRM 7.0/NW7.01

CRM Application Server ABAP

AS ABAP

Yes



CRM Application Server Java

AS Java

Yes


EHP1 FOR SAP CRM 7.0

CRM Application Server ABAP

AS ABAP

Yes



CRM Application Server Java

AS Java

Yes


SAP ERP 6.0 & EhPx for ERP 6.0

Supported Versions?

SAP ERP 6.0 & EhPx for ERP 6.0

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server ABAP

Automatic entry of installed software?

Partly
Installed software components  are provided automatically but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP ERP 6.0

ECC Server

AS ABAP

Yes


EhPx for ERP 6.0

ABAP Technology for ERP EHP

AS ABAP

Yes


EhP5 for SAP ERP 6.0

EHP5 FOR SAP ERP 6.0: Central Applications

AS ABAP

Yes


REMARK:

It is also possible to treat ERP as a typical SAP NetWeaver installation and assign additionally the product instances which are relevant for the installed basis release of SAP NetWeaver. Please refer to the section on SAP NetWeaver ABAP / J2EE

SAP NetWeaver TREX

To publish TREX to the Landscape Directory (SLD), please follow the instructions in SAP Notes:

1147499  "Connection to the System Landscape Directory" → TREX

1018839  "Registering in the System Landscape Directory using sldreg"

http://help.sap.com/saphelp_nw70/helpdata/EN/42/e33ae230ba3ee2e10000000a1553f6/frameset.htm

Supported Versions?

SAP NETWEAVER 7.0, SAP NETWEAVER 7.3

Automatic creation of Technical System?

Yes
Technical Systems are created of type
TREX System

Automatic entry of installed software?

Partly
Installed software components
are provided automatically but product versions and product instances
need to be assigned manually according to the software component of TREX.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP NETWEAVER 7.0

Search and Classif. (TREX)

TREX System

Yes

TREX 7.0

SAP NETWEAVER 7.3

Search and Classif. (TREX)

TREX System

Yes

TREX 7.1

SRM

Supported Versions?

SAP SRM 5.0, SAP SRM 6.0, SAP SRM 6.0/NW7.01, SAP SAP SRM 7.0, SAP SRM 7.0/NW7.01

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server ABAP

Automatic entry of installed software?

Partly
Installed software components
are provided automatically but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP SRM 5.0

SRM Server

AS ABAP

Yes



CCM with SRM-MDM Catalog

AS Java

Yes


SAP SRM 6.0

SRM Server

AS ABAP

Yes



CCM with SRM-MDM Catalog

AS Java

Yes


SAP SRM 6.0/NW7.01

SRM Server

AS ABAP

Yes



CCM with SRM-MDM Catalog

AS Java

Yes


SAP SAP SRM 7.0

SRM Server

AS ABAP

Yes



CCM with SRM-MDM Catalog

AS Java

Yes


SAP SRM 7.0/NW7.01

SRM Server

AS ABAP

Yes



CCM with SRM-MDM Catalog

AS Java

Yes


SCM

Supported Versions?

SAP SCM 5.0, SAP SCM 2007, SAP SCM 7.0, SAP SCM 7.01

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server ABAP

Automatic entry of installed software?

Partly
Installed software components
are provided automatically but product versions and product instances
need to be assigned manually.
Comment: For SCM Add-On Products like SAP SNC, SAP EM, SAP F&R the
basis component (SAP Netweaver Release) has to be also assigned as relevant
Product Instance

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP SCM 5.0

SCM Server

AS ABAP

Yes


SAP SCM 2007

SCM Server

AS ABAP

Yes


SAP SCM 7.0

SCM Server

AS ABAP

Yes


SAP SCM 7.01

SCM Server

AS ABAP

Yes


SAP SCM 7.02

SCM Server

AS ABAP

Yes


SAP NetWeaver LiveCache / SAP LiveCache

Currently SAP LiveCache is supported mainly for SCM Systems.

Supported Versions?

SAP LiveCache 7.5 / LCA Build 4.1,
SAP LiveCache 7.6 / LCA Builds 5.0,
SAP LiveCache 7.7 / LCA Builds 6.0,
SAP Livecache 7.7 / LCA Builds 7.0, 
SAP LiveCache 7.8 / LCA Builds 8.0,
SAP Livecache 7.9 / LCA Builds 9.0,
SAP Livecache 7.10 / LCA Builds 10.0
 

Automatic creation of Technical System?

Yes
Technical Systems are created of type
SAP_LiveCache

Automatic entry of installed software?

Partly
Installed software components
are provided automatically but product versions and product instances
need to be assigned manually.
Comment: During the SetUp for the LiveCache you have to maintain the RFC
Connection to the corresponding ABAP System


Product VersionProduct InstanceDiagnostic RelevantSoftware Component Version
 SAP SCM 2007 LiveCache Yes SAPLC / LCAPPS 5.1
SAP SCM 7.0LiveCacheYesSAPLC / LCAPPS 7.0
EHP 1 for SCM 7.0LiveCacheYesSAPLC / LCAPPS 7.0
EHP 2 for SCM 7.0LiveCacheYesSAPLC / LCAPPS 10.0
EHP 3 for SCM 7.0LiveCacheYesSAPLC / LCAPPS 10.0


SAP NetWeaver Process Integration (PI / XI)

Supported Versions?

SAP NETWEAVER 7.0, SAP NETWEAVER PI 7.1, SAP EHP1 FOR SAP NW PI 7.1, SAP NETWEAVER 7.3, SAP EHP1 FOR SAP NETWEAVER 7.3

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server ABAP and Application Server Java.

Automatic entry of installed software?

Partly
Installed software components are automatically reported for all supported product versions. Since SAP Netweaver 7.3 also product version and
instances are reported automatically.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP NETWEAVER 7.0

Process Integration

AS ABAP

Yes

Required for Integration Server


Process Integration

AS JAVA

Yes

Required for Integration Server and Adapter Engine

SAP NETWEAVER PI 7.1

Process Integration

AS ABAP

Yes

Required for Integration Server


Process Integration

AS JAVA

Yes

Required for Integration Server and Adapter Engine

SAP EHP1 FOR SAP NW PI 7.1

Process Integration

AS ABAP

Yes

Required for Integration Server


Process Integration

AS JAVA

Yes

Required for Integration Server and Adapter Engine

SAP NETWEAVER 7.3

Process Integration

AS ABAP

Yes

Required for Integration Server in case of dual stack


Process Integration

AS JAVA

Yes

Required for Integration Server and Adapter Engine

SAP EHP1 FOR SAP NETWEAVER 7.3

Process Integration

AS ABAP

Yes

Required for Integration Server in case of dual stack


Process Integration

AS JAVA

Yes

Required for Integration Server and Adapter Engine

SAP NetWeaver Business Warehouse (BW / BI)

Supported Versions?

SAP NETWEAVER 04, SAP NETWEAVER 7.0, SAP EHPxx FOR SAP NETWEAVER 7.0,
SAP NETWEAVER 7.3, SAP EHPxx FOR SAP NETWEAVER 7.3

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server ABAP and Application Server Java.

Automatic entry of installed software?

Partly
Installed software components are automatically reported for all supported product versions. Since SAP Netweaver 7.3 also product version and
instances are reported automatically.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP NETWEAVER 04

Business Intelligence

AS ABAP

Yes


SAP NETWEAVER 7.0

Business Intelligence

AS ABAP

Yes



BI Java

AS JAVA

Yes


SAP EHPxx FOR SAP NETWEAVER 7.0

Business Intelligence

AS ABAP

Yes



BI Java

AS JAVA

Yes


SAP NETWEAVER 7.3

Business Intelligence

AS ABAP

Yes



BI Java

AS JAVA

Yes


SAP EHPxx FOR SAP NETWEAVER 7.3

Business Intelligence

AS ABAP

Yes



BI Java

AS JAVA

Yes


SAP Business Objects Data Services

Supported Versions?

SBOP DATA SERVICES 4.0, SAP DATA SERVICES 4.1, SAP DATA SERVICES 4.2

Automatic creation of Technical System?

Yes
Technical Systems are created of type Unspecific Cluster System.

Automatic entry of installed software?

Yes

For some release, the payload file need to be edit manually.



 

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SBOP DATA SERVICES 4.0

Access Server

Unspecific Cluster System

Yes



Job Server

Unspecific Cluster System

Yes


SAP DATA SERVICES 4.1

Access Server

Unspecific Cluster System

Yes



Job Server

Unspecific Cluster System

Yes


SAP DATA SERVICES 4.2

Access Server

Unspecific Cluster System

Yes



Job Server

Unspecific Cluster System

Yes



 For complete steps of configuring the managed system for Data Services, please refer to the following link.

Managed system setup of Data Services 4.x system in the Solution Manager 7.1 and 7.2

SAP BusinessObjects Enterprise

Supported Versions?

BOBJ ENTERPRISE XI 3.0 - 3.1, SBOP BI PLATFORM 4.0 - 4.2

Automatic creation of Technical System?

Partly
Technical Systems for SBOP BI PLATFORM 4.x are created automatically of type Business Objects Cluster.
Technical Systems for BOBJ ENTERPRISE XI 3.0 and 3.1 are created manually of type Unspecific Cluster System.

Automatic entry of installed software?

Partly
Installed software components are automatically reported for SBOP BI PLATFORM 4.x. 
For BOBJ ENTERPRISE XI 3.0 and 3.1, both product version, product instance and installed software components
are created manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

BOBJ ENTERPRISE XI 3.x

JOB SERVER

Unspecific Cluster System

Yes



REPORT APPLICATION SERVER

Unspecific Cluster System

Yes



MULTIDIMENSIONAL ANALY. SERVER

Unspecific Cluster System

Yes



CENTRAL MANAGEMENT SERVER

Unspecific Cluster System

Yes



CRYSTAL REPORTS SERVER

Unspecific Cluster System

Yes



DESKTOP INTELLIGENCE SERVER

Unspecific Cluster System

Yes



WEB INTELLIGENCE SERVER

Unspecific Cluster System

Yes



INPUT FILE REPOSITORY SERVER

Unspecific Cluster System

Yes



EVENT SERVER

Unspecific Cluster System

Yes



OUTPUT FILE REPOSITORY SERVER

Unspecific Cluster System

Yes



WEB APP CONTAINER SERVER

Unspecific Cluster System




ADAPTIVE PROCESSING SERVER

Unspecific Cluster System

Yes



ADAPTIVE JOB SERVER

Unspecific Cluster System

Yes



SERVER INTELLIGENCE AGENT

Unspecific Cluster System

Yes



CONNECTION SERVER

Unspecific Cluster System

Yes


SBOP BI PLATFORM 4.X

BOE WEB APPLICATION JAVA

Business Objects Cluster

Yes



Central Mgmt. Service

Business Objects Cluster

Yes



File Repository Service

Business Objects Cluster

Yes



Event Service

Business Objects Cluster

Yes



Multidimensional Analy. Serv.

Business Objects Cluster

Yes



Data Federator Services

Business Objects Cluster

Yes



Connectivity Services

Business Objects Cluster

Yes



CR Processing Services

Business Objects Cluster

Yes



CR Scheduling Services

Business Objects Cluster

Yes



CR 20XX Processing Services

Business Objects Cluster

Yes



CR 20XX Scheduling Services

Business Objects Cluster

Yes



WebI Processing Services

Business Objects Cluster

Yes



WebI Scheduling Services

Business Objects Cluster

Yes



BI Workspace Services

Business Objects Cluster

Yes



Platform Processing Services

Business Objects Cluster

Yes



Platform Scheduling Services

Business Objects Cluster

Yes



Dashboard Design Services

Business Objects Cluster

Yes



SERVER INTELLIGENCE AGENT

Business Objects Cluster

Yes


 For complete steps of configuring the managed system for BOE 3.x and BOE 4.x, please refer to the attached docs.

 Managed system setup of BOE 3.x system in Solman 7.1

 Managed System Setup of BOE 4.X system in Solman 7.1 and 7.2

Apache Tomcat

Supported Versions?

Apache Tomcat 5.5, 6.0, 7.0, 8.0

Automatic creation of Technical System?

Yes
Technical Systems for Apache Tomcat are created automatically of type Apache Tomcat Server.

Automatic entry of installed software?

Yes
Installed software components are automatically reported with SLD Data Supplier.

 For complete steps of configuring the managed system for Apache Tomcat , please refer to the SAP note 1633036

 https://service.sap.com/sap/support/notes/1633036


hybris Commerce Suite

Supported Versions?

hybris Commerce Suite 5.0,5.1,5.2,5.3,5.4,5.5,5.6,5.7, 6.0

Automatic creation of Technical System?

Yes
Technical Systems for hybris Commerce Suite are created automatically of type Apache Tomcat Server.

Automatic entry of installed software?

Yes
Installed software components are automatically reported with SLD Data Supplier.

For complete documentation on how to configure hybris Commerce Suite systems in SAP Solution Manager, please refer to the following Wiki page

System Monitoring and End-to-End Root Cause Analyis for hybris

IBM WebSphere

Supported Versions?

WebSphere 6.0, 6.1, 7.0, 8.0

Automatic creation of Technical System?

Yes Technical Systems for WebSphere are created automatically of type IBM WebSphere Application Server.

Automatic entry of installed software?

Yes Installed software components are automatically reported with SLD Data Supplier.

 For complete steps of configuring the managed system for IBM WebSphere, please refer to the attached docs.

 Managed System Setup of IBM WebSphere in Solman 7.1

Microsoft Internet Information Service (include ASP.NET)

Supported Versions?

MS IIS 6.0, MS IIS 7.0, MS IIS 7.5

Automatic creation of Technical System?

Yes Technical Systems for MS IIS are created automatically of type MSIISINST via Outside Discovery in LMDB

Automatic entry of installed software?

Yes Installed software components including .NET Framework versions are automatically reported

Outside Discovery will report all installed .NET Framework versions to the LMDB, please use the following rules to select which one to be marked as the diagnsotic relevant.

1. If interested IIS Application pools only use ASP.NET 2.0, please select the one highest product version among MSFT .NET 3.5, MSFT .NET 3.0 and MSFT .NET 2.0

2. If interested IIS Application pools only use ASP.NET 4.0, please select the product version MSFT .NET 4.0 

3. If interested IIS Application pools use both, please select the one highest product version among MSFT .NET 3.5, MSFT .NET 3.0 and MSFT .NET 2.0 and MSFT .NET 4.0

Microsoft SharePoint (as Technical Scenario)

Supported Versions?

SharePoint by Microsoft 2010, SharePoint by Microsoft 2013

Automatic creation of Technical System?

Yes, each SharePoint server is modeled as a MSIISINST Technical System via Outside Discovery.  SharePoint Farm cluster is modeled as the Techncial Scenario via SLD Data Supplier. See SAP note 1683706

Automatic entry of installed software?

Yes Installed software components including Duet Enterprise versions are automatically reported


For complete steps of configuring the managed scenario for Microsoft SharePoint, please refer to the attached docs.

 Managed System Setup of SharePoint in Solman 7.1 

Oracle WebLogic

Supported Versions?

WebSphere 9.0, 10.0, 10.3

Automatic creation of Technical System?

No Technical Systems for WebLogic are created manually of type Unspecific Cluster System.

Automatic entry of installed software?

No Both product version, product instance and installed software components
are created manually.

 For complete steps of configuring the managed system for Oracle WebLogic, please refer to the attached docs.

 Managed System Setup of Oracle WebLogic in Solman 7.1


SAP BusinessObjects Information Steward

Supported Versions?

SAP BusinessObjects Planning and Consolidation, version for SAP NetWeaver

Automatic creation of Technical System?

Yes 
Technical Systems are created automatically of type Business Objects Cluster.

Automatic entry of installed software?

Yes
Installed software components are automatically reported.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SBOP INFORMATION STEWARD 4.0/4.1

Metadata Integrators

Business Objects Cluster

Yes



Service

Business Objects Cluster

Yes



Task Server

Business Objects Cluster

Yes




Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP INFORMATION STEWARD 4.2

Metadata Integrators

Business Objects Cluster

Yes



Service

Business Objects Cluster

Yes


Managed System Setup of Information Steward 4.2

SAP BusinessObjects Planning and Consolidation

Supported Versions?

SBOP PC 10.0 FOR SAP NW
SBOP PC 7.5 FOR SAP NW
SBOP PC 10.0 FOR MICROSOFT
SBOP PC 7.5 FOR MICROSOFT

Automatic creation of Technical System?

Partly,
Technical systems of Type AS ABAP are created automatically. The ones of Type Unspecific Cluster System are not.

Automatic entry of installed software?

Partly,
Entries of installed software for Type AS ABAP are created automatically. The ones for Type Unspecific Cluster System are not.

Product Version

Product Instance

System Type

Diagnostics Relevant

SBOP PC 10.0 FOR SAP NW

Application Server ABAP

AS ABAP

Yes


Business Intelligence     

AS ABAP

Yes


Business Plan.and Cons. ABAP

AS ABAP

Yes

SBOP PC 7.5 FOR SAP NW

Application Server ABAP

AS ABAP

Yes


Business Intelligence     

AS ABAP

Yes


Business Plan.and Cons. ABAP

AS ABAP

Yes


BPC .NET Server

Unspecific Cluster System

Yes

SBOP PC 10.0 FOR MICROSOFT

Business Plan.and Cons.

Unspecific Cluster System

Yes

SBOP PC 7.5 FOR MICROSOFT

Business Plan.and Cons.

Unspecific Cluster System

Yes


MS SQL Server Analysis Service    

Unspecific Cluster System

Yes


MS SQL Server Reporting Service    

Unspecific Cluster System

Yes


MS SQL Server Integration Service    

Unspecific Cluster System

Yes


For more detailed information, please refer to SAP Note 1461749 - E2E Root Cause Analysis for SBOP PC (BPC) and

Solution Manager Diagnostics Managed System Setup and Configuration Guide for SBOP PC 7.5/10 with SAP Solution Manager:

SAP BusinessObjects Financial Consolidation

Supported Versions?

SBOP Financial Cons. 10.0
BOBJ Financial Cons. 10.5
BOBJ Financial Cons. 7.5
BOBJ Financial Cons. 7.0

Automatic Creation of Technical System?

No

Automatic Entry of Installed Software?

No

Product Version

Product Instance

System Type

Diagnostics Relevant

SBOP Financial Cons. 10.0

BOBJ Fin Cons Web Site 10.0
BOBJ FINANCIAL CONS. 10.0

MS_IIS
Unspecific Cluster System

Yes
Yes

BOBJ Financial Cons. 10.5

BOBJ Fin Cons Web Site 10.5
BOBJ FINANCIAL CONS. 10.5

MS_IIS
Unspecific Cluster System

Yes
Yes

BOBJ Financial Cons. 7.5

BOBJ Fin Cons Web Site 7.5
BOBJ FINANCIAL CONS. 7.5

MS_IIS
Unspecific Cluster System

Yes
Yes

BOBJ Financial Cons. 7.0

BOBJ Fin Cons Web Site 7.0
BOBJ FINANCIAL CONS. 7.0

Unspecific Cluster System
Unspecific Cluster System

Yes
Yes

SAP Note 1365266 - RCA: Managed System Setup for BOBJ Financial Cons.

SAP BW Accelerator

To publish SAP BI Accelerator to the Landscape Directory (SLD), please follow the instructions in SAP Notes:

1147499  "Connection to the System Landscape Directory" → TREX

1018839  "Registering in the System Landscape Directory using sldreg"

http://help.sap.com/saphelp_nw70/helpdata/EN/42/e33ae230ba3ee2e10000000a1553f6/frameset.htm

Supported Versions?

SAP BI Accelerator 7.0, SAP BW Accelerator 7.2

Automatic creation of Technical System?

Yes
Technical Systems are created of type
TREX System

Automatic entry of installed software?

Partly
Installed Software components are automatically reported for all supported product versions but
product versions and instances need to be added manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP BI Accelerator 7.0

BI Accelerator

TREX System

Yes


SAP BW Accelerator 7.2

BI Accelerrator

TREX System

Yes


Please check alsoSAP Note:  1264540   "Workload Data Collection for BWA (BIA) in Solution Manager"

SAP NetWeaver ABAP / J2EE

For a generic SAP NetWeaver ABAP or J2EE system you need at least to select the following product instances as installed and diagnostics relevant. Depending on the installed SAP NetWeaver release or enhancement Package, it could be one the following:

Supported Versions?

SAP NETWEAVER 7.0, SAP EHPX FOR SAP NETWEAVER 7.0, SAP NETWEAVER 7.1, SAP NETWEAVER 7.2, SAP NETWEAVER 7.3, SAP EHPX FOR SAP NETWEAVER 7.3, SAP NETWEAVER 7.4

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server ABAP and Application Server Java.

Automatic entry of installed software?

Partly
Installed software components are automatically reported for all supported product versions. Since SAP Netweaver 7.3 also product version and
instances are reported automatically.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP NETWEAVER 7.0

Application Server ABAP

AS ABAP

Yes



Application Server Java

AS JAVA

Yes


SAP EHPX FOR SAP NETWEAVER 7.0

Application Server ABAP

AS ABAP

Yes



Application Server Java

AS JAVA

Yes


SAP NETWEAVER 7.11

Application Server Java

AS JAVA

Yes


SAP NETWEAVER 7.2

Application Server Java

AS JAVA

Yes


SAP NETWEAVER 7.3

Application Server ABAP

AS ABAP

Yes



Application Server Java

AS JAVA

Yes


SAP EHPxx FOR SAP NETWEAVER 7.3

Application Server ABAP

AS ABAP

Yes



Application Server Java

AS JAVA

Yes


SAP NETWEAVER 7.4

Application Server ABAP

AS ABAP

Yes



Application Server Java

AS JAVA

Yes


Adobe Document Services

Supported Versions?

SAP NETWEAVER 7.0, EHPX for SAP Netweaver 7.0

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server Java

Automatic entry of installed software?

Partly 
Installed software components
are provided automatically but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP NETWEAVER 7.0

Adobe Document Services

AS Java

Yes


EHPX FOR SAP NETWEAVER 7.0

Adobe Document Services

AS Java

Yes


SAP HANA

Supported Versions?

SAP HANA 1.0 >= SP2

Automatic creation of Technical System?

yes
Technical System will be created automatically by outside discovery
When using SAP HANA 1.0 >= SP4 and Solution Manager >= SP5
the technical system is delivered via SLD

Automatic entry of installed software?

No
Installed software must be assigned manually

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP HANA ENTERPRISE EDIT. 1.0

SAP HANA database


Yes


SAP HANA ENTERPRISE EXT. 1.0

SAP HANA database


Yes


Managed System Setup of SAP HANA in Solution Manager

SAP HANA XSA

Supported Versions?

SAP HANA 1.0 >= SP2

Automatic creation of Technical System?

yes

Same as SAP HANA Database.

Automatic Diagnostic Relevant?

No

On Product Instances (Details), “XS Advanced Runtime” should have “Diagnostic Relevant” checked; “SAP EXTENDED APP SERVICES 1” should have “Used in System”. Checked.

XSA System Monitoring



SAP NetWeaver Composition Environment (CE)

Supported Versions?

SAP NETWEAVER CE 7.1, SAP NETWEAVER CE 7.2

Automatic creation of Technical System?

Yes
Technical Systems are created of type
Application Server Java

Automatic entry of installed software?

Partly 
Installed software components
are provided automatically but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP NETWEAVER CE 7.1

Composite Applications

AS Java

Yes


SAP NETWEAVER CE 7.2

Application Server Java

AS Java

Yes


Duet

Web Dispatcher

Supported Versions?

SAP WebDispatcher 7.0, SAP WebDispatcher 7.10, SAP WebDispatcher 7.11, SAP WebDispatcher 7.20

Automatic creation of Technical System?

Yes
Technical Systems are created of type
SAP Web Dispatcher

Automatic entry of installed software?

Partly 
Installed software components might be provided automatically by the SLD data supplier, but product versions and product instances
need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP EHP2 FOR SAP NETWEAVER 7.0

SAP Web Dispatcher

SAP Web Dispatcher

Yes


To add missing software component/product information open the SAP Solution Manager Configuration (transaction SOLMAN_SETUP), choose Managed Systems Configuration > Technical Systems > System Operations > Maintain System. Then select the node “Software” in the n avigation tree and open the “Product Instances (Details)” on the right tab panel. Add the appropriate product version, product instance and, if missing, software component information. For example,  the software component version SAP WEB DISPATCHER 7.20, product version SAP EHP2 FOR SAP NETWEAVER 7.0 in the product instance SAP Web Dispatcher.

Note:

SAP Netweaver MDM 7.1


Supported Versions?

SAP NETWEAVER MDM 7.1

Automatic creation of Technical System?

Yes
Technical Systems are created of type
MDM

Automatic entry of installed software?

Yes  

Prerequisites:
Ensure that you installed diagnostics agents on all hosts of the MDM system.
Execute the  activities described in SAP Solution Manager Work Center -> System Preparation -> Step 5.5 Prepare Outside Discovery and Connect Diagnostics Agent for the MDM Server database hosts.

SLD registration

For SAP Netweaver MDM 7.1SP 01 - SP 09 please register the System to SLD as explained in SAP Note 1798643. Do not use the SLD registration mechanism that is part of the MDM system.
As of SAP Netweaver MDM 7.1SP 10 please register the MDM system using the MDM specific SLD registration mechanism. Please see note 1018839 - Registering in the System Landscape Directory using sldreg.

After successful SLD registration the database systems used by the MDM system need to be added manually to the system definition in SAP Solution Manager.
Please proceed as follows:

1. Call the “SAP Solution Manager Configuration Work Center”.
2. Select “Managed System Configuration”.
3. Select the MDM System in Question.
4. Select System Operations --> Maintain System.
5. Select Assigned DB systems.
6. Select Add and add the databases used by the MDM system.

Please consider the following for SRM/MDM Catalog:

If you installed an SRM/MDM Catalog you have installed in fact two different technical systems:
One MDM Server storing the catalog data and
one Application Server Java to display the  catalog UI.
The defintion of the MDM Server in is explained in this chapter.
Additionally the Application Server Java needs to be registered to SLD. Please refer to the relevant section.

 Managed System Setup

Perform the managed system configuration as follows:'
1. Call the “SAP Solution Manager Configuration Work Center”.
2. Select “Managed System Configuration”.
3. Select the MDM System in Question.
4. Select Configure System.
4. Select Configure System.
5. Execute all activities in the guided procedure.


Sybase Unwired Platform 

Managed System Setup for Sybase Unwired Platform 2.1  

Managed System Setup for Sybase Unwired Platform 2.2

SAP Router

Supported Versions?

SAP ROUTER 7.2

Automatic creation of Technical System?

No, Technical Systems for SAP Router are created manually of type Unspecific Standalone Application System.

Automatic entry of installed software?

No, Both product version, product instance and installed software components are created manually

For complete steps of configuring the managed system for SAP ROUTER, please refer to the following page.

Managed System Setup of SAP Router in SAP Solution Manager 7.1

SAP Business Connector System 

Supported Versions?

SAP Business Connector 4.8

Automatic creation of Technical System?

No, Technical Systems for Business Connector are created manually of type Unspecific Standalone Application System.

Automatic entry of installed software?

No, Both product version, product instance and installed software components are created manually

For complete steps of configuring the managed system for SAP Business Connector System, please refer to the following page.

Managed System Setup of SAP Business Connector in SAP Solution Manager 7.1

SAP Convergent Charging

Supported Versions?

SAP Convergent Charging 3.0

Automatic creation of Technical System?

Yes, SAP Solution Manager 7.1 relies on the landscape information in the Solution Landscape Directory (SLD) and in its connected LMDB. SAP Convergent Charging provides an automatic registration procedure to the SAP System Landscape Directory (SLD)..

Automatic entry of installed software?

Yes, The SAP Solution Manager will automatically import the SAP CC 3.0 system from the SLD into the LMDB. However, due to issues with the SLD Data Supplier in SAP CC 3.0, it is necessary to review resp. correct the SAP CC system data in the SAP Solution Manager.

For complete steps of configuring the managed system for SAP Convergent Charging System, please refer to the following page.

Managed System Setup of SAP Convergent Charging System in SAP Solution Manager 7.1

To set up SAP Convergent Charging 4.3~ 4.6, 5.0, and 2020 systems in SAP Solution Manager 7.2,  you will have to import the Diagnostics template attached to the SAP Note 1875021 - System Monitoring Setup for SAP Convergent Charging.

Sybase Afaria System

Supported Versions?

Sybase Afaria 7.0

Automatic creation of Technical System?

No, Technical Systems for SAP Afaria are created manually of type Unspecific Cluster System.

Automatic entry of installed software?

No, Both product version, product instance and installed software components are created manually

 For complete steps of configuring the managed system for Sybase Afaria System, please refer to the following page.

Managed System Setup of Sybase Afaria in SAP Solution Manager 7.1

SAP Partner Products

For detailed information about which Partner Products are currently supported by the Right to View version of Introscope that comes with SAP Solution Manager, please refer to SAP Note 1852015.

SAP Productivity Pak by Ancile

Supported Versions?

SAP Productivity Pak 4.5, SAP Productivity Pak 5.0

Automatic creation of Technical System?

Yes
Technical Systems are created of type Apache Tomcat Server

Automatic entry of installed software?

Yes
Installed software components product versions and product instances are provided automatically, but product versions and product instances need to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP Productivity Pak by Ancile 4.5

Productivity Pak Server

Apache Tomcat

Yes


SAP Productivity Pak by Ancile 5.0

Productivity Pak Server

Apache Tomcat

Yes


Refer to   SAP Note 1864308 for further instructions on running Managed System Setup 

Refer to  SAP Note  1779892   for further instructions on integrating of SAP Productivity Pak by Ancile with CA Introscope 

 

SAP Convergent Mediation by DigitalRoute

 

Supported Versions?

SAP Convergent Mediation 3.0 and above (a.k.a. MediationZone 7.0 and above)

Automatic creation of Technical System?

Yes
Before SAP Convergent Mediation 3.3, use the generic SLD Data Supplier program to register the UnspecificClusterSystem to SLD server. As of 3.3 or above, the SLD Data Supplier logic is built-in with SAP Convergent Mediation product and triggered during the startup. 

Automatic entry of installed software?

Yes
Before SAP Convergent Mediation 3.3, use the generic SLD Data Supplier program to register the UnspecificClusterSystem to SLD server. As of 3.3 or above, the SLD Data Supplier logic is built-in with SAP Convergent Mediation product and triggered during the startup. 

 

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP Convergent Mediation 3.0

CM Platform

CM Execution Context

UnspecificClusterSystem

Yes

SAP Convergent Mediation 3.1

CM Platform

CM Execution Context

UnspecificClusterSystem

Yes

SAP Convergent Mediation 3.2

CM Platform

CM Execution Context

UnspecificClusterSystemYes
SAP Convergent Mediation 
4.X

CM Platform

CM Execution Context

UnspecificClusterSystemYes

      

Refer to SAP Note 2258229 and 2718475 for further info on integrating of SAP Convergent Mediation by DigitalRoute 

Refer to    SAP Note 2021921 for further info on generic SLD Data Supplier program

 


Vertex O-Series

See Managed System Setup of Vertex O-Series in SAP Solution Manager 7.1

  

  

  

SAP Central Process Scheduling by Redwood

 

Supported Versions?

SAP CPS 8.0 BY REDWOOD (M33.x), SAP CPS FOR SAP NETWEAVER 7.0 (M33.x), SAP CPS FOR NW 7.0 (FULL) (M28.x), SAP BPA 9.0 BY REDWOOD

Automatic creation of Technical System?

Yes
Technical Systems are created of type Application Server Java

Automatic entry of installed software?

Yes
Installed software components product versions and product instances are provided automatically, but product versions and product instances need to be assigned manually.

 

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP Netweaver 7.4

SAP CPS 8.0 BY REDWOOD

Application Server Java

Yes

SAP Netweaver 7.4

SAP CPS 8.0 BY REDWOOD

AS Java Extensions

Yes

SAP Netweaver 7.4

SAP CPS 8.0 BY REDWOODCentral Process SchedulingYes

SAP Netweaver 7.4

SAP BPA 9.0 BY REDWOOD Buisness Process Automation Yes

      

Refer to  SAP Note 1852015 for further info on integrating of SAP CPS by Redwood and SAP BPA 9.0 by Redwood with CA Introscope 

Refer to SAP BPA Technical Monitor setup in SAP Solution Manager 7.1

1852015 - CA Introscope Instrumentation for SAP Partner Products

 


SAP Talent Visualization and SAP Org Visualization by Nakisa

Supported Versions?

SAP NETWEAVER 7.1X, , SAP NETWEAVER 7.3X, SAP NETWEAVER 7.4X

Automatic creation of Technical System?

Yes 
Technical Systems are created of type 
Application Server Java

Automatic entry of installed software?

Partly 
Installed software components 
are provided automatically but product versions and product instances 
need to be assigned manually.

 

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP Org Visualization 3.x

Org Chart Java, OrgModeler_Java

AS Java

Yes


SAP Org Visualization 4.x

Org Chart, OrgModeler,OrgAudit

AS Java

Yes


SAP Talent Visualization 3.x

Succession Planning Java, CareerPlanning_Java,TalentFramework_Java

AS Java

Yes


SAP Talent Visualization 4.xTalentHubEmployee,TalentHubManager,TalentHubHRExecAS JavaYes


SAP Portal Site Management by OpenText and SAP Portal Content Management by OpenText

Automatic creation of Technical System?

Yes 

Technical Systems are created of type Application Server Java

Automatic entry of installed software?

Partly 

Installed software components are provided automatically.

Product versions and product instances needs to be assigned manually.

Product Version

Product Instance

System Type

Diagnostics Relevant

Remarks

SAP PSM BY OPEN TEXT 10.0 (add-on)

OT WSM Portal Mgr-SAP NW Portl

AS Java

No


SAP PCM BY OPEN TEXT 10.0 (add-on)

Portal Content Management

AS Java

No



Other Products

You might want to make a minimal monitoring of systems which do not belong to the above mentioned SAP Products or Partner Products.
With this minimal monitoring it is possibe to make at least Host Monitoring. These Products have to be defined as 'Unspecific Cluster System'.
This Technical System has to be created manually with the help of LMDB.


One example would be the SCM Optimizer:

SCM Optimizer


Technical System TypeTechnology TypeUse of Standard Product InstanceTechnical Instance
Unspecific Cluster SystemOthersYES

Server Name: <Name>

Technology Type: Others

Host: use the Host on which the SMD Agent is installed

Add Standard Product Instance: should be flagged

  


SAP Product Engine (MSG.PM), part of SAP Insurance Policy Management (FS-PM)

SAP Product Engine (MSG.PM) is a partner solution from MSG Systems AG which is part of SAP Insurance Policy Management.

MSG.PM component can be monitored using Introscope. This is C/C++ based component and Introscope integration has specific configuration steps related to MSG.PM.

Refer to SAP Note 1840351 for further instructions to monitor MSG.PM component.





  • No labels

5 Comments

  1. Unknown User (rolrbns)

    Hi Michael,

    Thanks for the info, I'll keep struggling with SLD/LMDB/SMSY but this helps. Is the section for "SAP ERP 6.0 & EhPx for ERP 6.0" intentionally left blank or an oversight? I assume that's what most people have and would like to set up correctly. Thank you,

    David

  2. Unknown User (tbimcu5)

    Hi Michael, thanks for the useful info, but how can we connect Content Server to Solution Manager 7.1?

    Yohanes

  3. Former Member

     

    Do we also have info on the SMP 2.3 setup and is there an update to SAP Note 1762741: Setup for SUP 2.2 with SolutionManager 7.1 SP05) available that

    would have an updated SMP 2.3 XML in the template zip ? (CVTemplates71SP05.zip)

    1. Kobe Lu

      Hello Klaus,

      The template for SMP 2.3 has not been released yet, if you have further question please send me a mail.

       

      BR,

      Kobe

  4. Madi Tatubayev

    Hi Michael,

    How can we connect OpenText Extended ECM 10.5 to Solution Manager 7.1 SP11?

    Madi