What is the best procedure to migrate the SAP Solution Manager system? We have the migration key and are using R3load and Jload to export and import. What is the best procedure for configuring the data in SAP Solution Manager, for example:
- How can we change the data? (i.e., how can we modify the technical system landscape, business landscape, etc.)
- How do we manage the SLD information?
- How can we manage all the data residing in the database tables or schemas?
I would avoid the changing the system ID (SID), when migrating SAP Solution Manager or back-end systems involved in Solution Manager scenarios such as Change Request Management (ChaRM). Changes to the hostname and system number are captured automatically as they are updated in the Central System Landscape Directory (SLD) as soon as the systems connects for the first time, after the migration.
If SAP Solution Manager uses the central SLD as primarily source of environment, the new hostname and instance number are automatically picked up and all entries in the SMSY updated. Using the central SLD as primarily source of information is recommended by SAP.
Also, remember to adapt and verify the RFC connections used in SMSY if the hostname and/or instance number changes. The RFC connections in the back-end systems need to be corrected as well.
Transaction SECSTORE can be used to verify the username/passwords in the RFC connections. Passwords are invalid after an operating system or database migration or Unicode conversion. They can easily be recovered all at once via transaction SECSTORE. This surely beats the re-entering of the password in every RFC connection in SAP Solution Manager. As you know, Solution Manager has many of these.
This was first published in November 2009