SHORT OVERVIEW OF SOME TECHNICAL TERMS
LMDB
|
Landscape
Management Database Central storage and editor for system information in SAP
Solution Manager, supplied by a central SLD. In the LMDB, you manage
technical information (such as technical systems and hosts) and logical
information (such as product systems and technical scenarios). This data is
the basis for other applications, like monitoring and alerting, diagnostics,
maintenance transactions, and SAP Support Portal. As of SAP Solution Manager
7.1, the LMDB replaces the previous information storage SMSY
|
Maintenance
Optimizer (MOPz)
|
Application
within SAP Solution Manager that guides you through planning and downloading
stack XML files for enhancement packages, support packages, and additional
update packages. These files can be used as input files for the installation
by update tools like Software Update Manager.
|
|
System
Landscape Directory
Central
provider of information on technical systems, for consumers in the system
landscape and for external consumers. The SLD gets its information mainly
from SLD data suppliers, which are installed on the technical systems, and
from the SAP software catalog.
With
the SLD, you collect and edit system data that is required for system
landscape management. This information can be used by other consumers, such
as SAP Process Integration, WebDynpro for Java, and SAP Solution Manager.
|
|
|
The
SAP Solution Manager System Landscape collects information about the SAP
systems in the landscape. (SMSY is the name of the transaction in SAP
Solution Manager.) As of SAP Solution Manager 7.1, the new information
storage LMDB replaces SMSY.
|
|
Software
Provisioning Manager
|
|
A
tool that performs software provisioning processes such as installation,
uninstallation, system copy, or system transformation. The Software
Provisioning Manager is delivered with the Software Logistics Toolset.
|
|
|
The
stack configuration file is created by the Maintenance Optimizer and is
system-specific. Depending on the software components that are installed in
a system, the Maintenance Optimizer calculates the required software
components that have to be updated to reach a certain target configuration.
|
|
|
Software
Update Manager
|
A
software logistics tool that controls different kinds of implementation
processes, such as upgrading SAP systems, installing enhancement packages,
or applying Support Package stacks.
|
|
|
Release
offered after the beginning of the unrestricted shipment phase if required
and that contains a collection of all previously available support
packages.
|
|
|
The
SAP system on which you are going to install the enhancement package.
|
|
|
Describes
a part of a product's software that is installed on one or several physical
or virtual hosts.
A
technical system is installed and administered as a whole. It is identified
by a system ID (SID) or extended SID, a host, and an installation number.
There are different technical system types, for example Application Server
(AS) ABAP, AS Java, or TREX. Technical systems are central elements when it
comes to software component deployment and operational activities, such as
monitoring and alerting.
|
|
|
Activities
to maintain or enhance a system, such as installing enhancement packages,
installing add-ons, or applying Support Package stacks or Support Packages.
Note:
The tool for system maintenance tasks is the Software Update Manager (SUM).
In the SUM guide, the term "Update" is used as collective term
for all the tasks that can be performed using this tool (such as performing
release upgrades, installing enhancement packages, or updating a system
with Support Package Stacks).
|
|
|
The switch from an older
software version to a new version. Typically, both the server component of
a system landscape and other components are upgraded. Several different
technical upgrade procedures are used to upgrade the server component, such
as the Repository Switch upgrade or the System Switch upgrade.
|
|
