A technical system is a runtime system on top of a computer system (host). It is a set of software elements that are installed, configured and administered as a unit. A technical system offers services at service access points. The software that forms the technical system can be installed on a single host (standalone system) or distributed over several hosts (distributed system or cluster system). Individual product instances of product versions are installed on technical systems. A technical system often consists of sub-systems (technical instances or technical nodes).
Technical systems are the central element of the solution landscape in terms of software component deployment and operational activities, such as monitoring and alerting. They are typically created by installation and register themselves in the system landscape directory (SLD), which forwards the information to SAP Solution Manager. Technical systems are identified by their system ID, host name, and other attributes like the installation number. A technical system is of a certain type, for example, Application Server (AS) ABAP, AS Java, or TREX system.
Information about technical systems is maintained in the landscape management database (LMDB). For details see the following chapters:
In the LMDB, you can maintain the following technical system types:
Technical System Type | Source | Editor | Notes |
---|---|---|---|
.NET System | Manual creation | LMDB technical system editor | |
Apache Tomcat Server | SLD data supplier | LMDB technical system editor | No installed application product information |
Application Server ABAP | SLD data supplier | LMDB technical system editor | |
Application Server Java | SLD data supplier | LMDB technical system editor | |
SAP BusinessObjects Cluster | SLD data supplier | LMDB technical system editor | |
CA Introscope Enterprise Manager (Cluster) | Manual creation | SAP Solution Manager Configuration (transaction | SAP Solution Manager Configuration (transaction SOLMAN_SETUP) |
CA Introscope Enterprise Manager (Standalone) | Manual creation | see | SAP Solution Manager Configuration (transaction SOLMAN_SETUP) |
Database System | SLD data supplier, Outside Discovery | LMDB technical system editor | Outside Discovery enhances the system information of SLD data suppliers. |
Diagnostics Agent | SLD Data Supplier | LMDB technical system editor | |
External Service | Manual creation or download | LMDB technical system editor | You can create technical systems of type "external service" for external systems that host SAP Cloud Services. |
IBM WebSphere Application Server | SLD data supplier | LMDB technical system editor | No installed application product information |
SAP liveCache | SLD data supplier (AS ABAP) | LMDB technical system editor | |
SAP NetWeaver Master Data Management Server | SLD data supplier | LMDB technical system editor | |
Microsoft Internet Information Services | Outside Discovery, manual editing | LMDB technical system editor | No installed application product information |
SAP Web Dispatcher | SLD data supplier | LMDB Technical System Editor | |
SAP HANA Database | Either SLD data supplier | LMDB technical system editor | |
SAP Mobile Platform (Until version 2.2: Sybase Unwired Platform) | SLD data supplier | LMDB technical system editor | |
TREX System | SLD data supplier | LMDB technical system editor | |
Unspecific 3-Tier System | Manual creation | LMDB technical system editor | |
Unspecific Cluster System | SLD data supplier or manual creation | LMDB technical system editor | |
Unspecific Standalone Application System | SLD data supplier or manual creation | LMDB technical system editor |
Further LMDB Entities (Other than Technical System) | Source | Editor | Notes |
---|---|---|---|
Technical Scenario | Manual or automatic creation |
| stored in the LMDB When AS ABAP and AS JAVA with the same system ID have been registered, a dual-stack is recognized automatically. |
Host | SLD data supplier and Outside Discovery | LMDB host editor | stored in the LMDB Outside Discovery enhances the system information of SLD data suppliers. |
The following entities are registered and defined for each technical system:
Software Components and Software Component Versions
Software components are always described in versions. Software components versions are the smallest entity that can be installed on a technical system. A software component version can be part of several product instances. It can require other software component versions to be installed as well. There are smaller shippable software entities than software component versions like support packages, patches, and notes. They always refer to the software component version that they change.
Product Instances
A product instance is part of exactly one product version. A product instances bundles a set of software components that have to be installed as a unit. The individual software components cannot be distributed among different technical systems. The set must be installed and updated together, to reach a consistent state. (Note: In contrast to an update, patches can be applied to individual software components.) The product instances define the maximum allowed software component distribution of a product version.
A product instance can contain other product instances. Product instances can also be re-used across products and may contain one or more software components. One product instance (and the software component versions it contains) is always installed on one technical system, so it cannot be distributed across technical systems.
Products and Product Versions
SAP products are the applications that SAP delivers. A product groups a set of functions to solve a business need. The SAP product model (SAP software catalog) describes all SAP products. This model defines the possible product structure. A product consists of one or more product versions.
Examples of products are SAP ERP, SAP NetWeaver, and SAP Solution Manager.
A product version is a release of a product. It bundles the product instances and related software component versions available at the same time for a function. The bundle considers, for example, technical dependencies. Product versions typically have a name starting with “SAP …” and have characteristics like their application function and a maintenance period. Example: SAP ERP 6.0 is a product version of the product SAP ERP.