Show TOC

Procedure documentationMigrating System Information from SMSY to LMDB Locate this document in the navigation structure

 

If you maintained product system information manually in the SAP Solution Manager System Landscape tool (transaction SMSY) in earlier releases, you may want to migrate this data to the Landscape Management Database (LMDB), which is the central storage for landscape information, for both technical systems and product systems, as of release 7.1 SP05. (For information about the differences between LMDB and SMSY, see SAP Note 1679673.)

For new installations of SAP Solution Manager, migration from SMSY is unnecessary because there is no data to be migrated.

Migration from SMSY to LMDB is a one-time activity during the LMDB setup. Do not maintain data manually in SMSY subsequently.

There are two ways of migrating data from SMSY to the LMDB:

  • Aspect-oriented migration (not critical, recommended)

    Transfers only particular aspects of technical system information that could only be maintained manually in SMSY and cannot be provided by an SLD. It does not create the complete system information. It only completes existing technical system information in the LMDB, for example the product system descriptions and custom attributes (called “other attributes” in SMSY).

    All system types used in SMSY are supported.

  • System-oriented migration (handle with care)

    Transfers the complete technical system information and does not only add to existing systems. This option must only be used if the complete technical system description cannot be provided by the SLD. Otherwise, you risk creating system duplicates in the LMDB, with one system that was migrated from SMSY and the other one automatically synchronized from the SLD.

Procedure

Aspect-Oriented Migration

Prerequisites:

  • You have set up the SLD synchronization as described under Connecting the LMDB to System Landscape Directory (SLD).

  • The technical systems to be considered for migration exist in both SMSY and LMDB. The migration process checks this based on the extended system ID (extended SID).

  • You have maintained the product systems in SMSY.

  • Clean-up SMSY before the migration. Start transaction SMSY and delete any product system that does not need to be migrated to the LMDB.

  • The aspect to be migrated is maintained in SMSY. For example, a system has values under Other Attributes.

    The aspect must not yet be maintained in the LMDB. For example, a system in the LMDB must not have values under   System Overview   Attributes  Additional Attributes. (If you already had entered any values in the LMDB manually, they would have already been synchronized into SMSY, and migration of SMSY data would be superfluous.)

Procedure:

  1. Start SAP Solution Manager Configuration (transaction SOLMAN_SETUP) and choose   System Preparation   Prepare Landscape Description   Migrate Data into LMDB  .

  2. Switch to Edit mode and choose the activity for the information you want to migrate.

    Start all existing activities, consecutively:

    • Migrate Product Systems (recommended)

      A SMSY product system should be either migrated to the LMDB or explicitly be deleted in transaction SMSY.

    • Migrate Installed Product Instances (optional)

      Migrate the SMSY product assignment of systems whose assignments you are sure are correct. The data is migrated from the SMSY product system to the corresponding LMDB technical systems.

    • Migrate Custom Attributes (optional)

      Migrate the custom attributes of systems for which you have maintained any.

    • Migrate Host Router Data (optional)

      Migrate SAP router configurations if they were maintained in SMSY.

    • Migrate Diagnostics-Relevant Flags (optional)

      Migrate diagnostics-relevant flags of systems, if you want to keep them.

    • Migrate Logical Component Data

      For more information, see Managing Logical Components.

    Depending on the number of systems and their size, migration can take some time.

  3. Check the log section for details.

System-Oriented Migration

System-oriented migration transfers the complete technical system description including most aspects from the SMSY to the LMDB.

Note Note

Avoid system—oriented migration

  • Only migrate systems for which you cannot configure data suppliers, for example because of a firewall. Automatically supplied data is usually more reliable than manually created data. And data suppliers ensure that changes in a technical system are reflected in SLD and the LMDB automatically.

    For more information, see Registering Technical Systems Automatically by Data Suppliers.

  • Only system descriptions that are sufficient to create an LMDB entry are migrated.

  • To avoid superfluous effort, only migrate system descriptions that are really necessary. Clean up SMSY before migration.

End of the note.

System-oriented migration is supported for the following system types:

  • System-Oriented Migration for AS ABAP

    System-oriented migration is supported for AS ABAP technical systems and all system entities, for example, clients, instances, software components, and other attributes.

    Prerequisites:

    • You have performed the basic configuration of the LMDB.

    • You have initially synchronized SLD and LMDB.

    • You have maintained at least maintained the following data in SMSY for ABAP application servers (ABAP):

      • Installation Number

      • Message Server

      • Database is assigned to the system

      • The server of the assigned database

      • The manufacturer of the assigned database

  • System-Oriented Migration of Master Data Management Server (MDM)

    Migration of instances, databases, software components, and other attributes is supported for technical systems of type MDM.

    Prerequisites for MDM Layout Server, Import Server, and Syndication Servers:

    • You have assigned the technical system to the product system by assigning the product instances.

    • The extended system IDs of technical systems and product systems must match.

    • The software components for the technical instances, for example the MDM_SERVER software component in the MDM Server server role, must be in the technical system.

    • The technical system has an instance in the MDM Server server role.

    • You have maintained the instance number and server.

    • You have maintained the instance according to the SMSY naming convention: <servername> <sid> <instance number>.

    • A database must be assigned to the system.

    • You have maintained the server of the assigned database.

    • You have maintained the manufacturer of the assigned database.

    Example: You have a technical system of type MDM with a technical instance with server role MDM Server, and a product system with product version SAP MDM 5.5. In this case, the technical system must be assigned to the Master Data Server product instance.

  • System-Oriented Migration of Unspecific Cluster System (UNSPECIFIC)

    Migration of instances, databases, software components, and other attributes is supported for Unspecific Cluster Systems.

    Prerequisites:

    • You have assigned a database to the system in transaction SMSY.

    • You have maintained the server of the database.

    • You have maintained the manufacturer of the database.

    • You have assigned one or more product instances of a product system to the technical system.

    • The extended system IDs of technical systems and product systems must match. Software components must be maintained.

Procedure:

  1. Start SAP Solution Manager Configuration (transaction SOLMAN_SETUP) and choose   System Preparation   Prepare Landscape Description   Set Up LMDB  .

  2. Switch to Edit mode and choose Migrate Technical Systems from SMSY.

  3. Select the systems to migrate, and choose Migrate Selected Rows. The migration runs as a background job and takes a few minutes per system, depending on their type and size.

  4. When the background job has finished, you can choose Display Log for details.