1.

Application Cleanup
1.1 Clean System Monitoring data
In this activity, you remove the decommissioned system from all system monitoring scenarios. You do
this to avoid incorrect monitoring results and alerts or loading misleading data into the database
(availability monitoring for a system to be deleted, for example).

Note: During this activity execution, all Monitoring and Alerting Infrastructure (MAI) extractors of the
decommissioned system are removed.

1.2 Clean Sessions and Reports

In this activity, you clean up all sessions and reports, including EarlyWatch Alert (EWA), Data Volume
Management (DVM), and Service Level Reporting (SLR), for the decommissioned system. You do that to
delete on-going sessions and free disk space.

Note: This step can take several hours. Example: Removing 1000 periodic sessions takes about 1 hour.

1.3 Clean Exception Management

In this activity, you remove the decommissioned system from exception management configuration and
monitoring. You do that to avoid false monitoring results and alerts.

1.4 Stop System Recommendations

In this automatic activity, you unregister the technical system from the System Recommendations
service. When you decommission a technical system, we recommend that you unregister the system
from this service.

1.5 Clean System Recommendations Reports

In this automatic activity, you clean the SAP Solution Manager from all system recommendation data that
was stored for the decommissioned system. When you decommission a technical system, we recommend
that you delete all data of that system.

This is Option activity

2. Cross Application Cleanup

In this step, you do the following:

 To avoid orphan EFWK extractors, clean up extractors that monitor the decommissioned system.
 To avoid orphan DBA Cockpit connections, remove the decommissioned system from the DBA
Cockpit configuration.
 To avoid orphan remote function calls, clean up the RFC connections to the decommissioned
system.
 To avoid orphan transport targets, remove the decommissioning system from transport routes.
 To stop data collection from Introscope Enterprise Manager, deactivate the byte code adapter on the
Java stack of the decommissioned system.
 To stop data collection, remove the Diagnostics Agents from the decommissioned system.
 Clean up Diagnostics Agents roles for the decommissioned system.
3. Planning Projects and Solution Cleanup
3.1 Clean Projects and Solutions
In this activity, you identify the SAP Solution Manager projects and solutions containing the logical
components of the decommissioned system

3.2 Clean Logical Components

In this activity, you remove the decommissioned system from its logical components. You do that to
avoid invalid data and orphan artifacts.

4. Clean System Data from SMP

In this activity, you delete the decommissioned system from SAP Service Marketplace. You do that to
avoid being charged for inactive systems, and to ensure that your system data in SAP Support Portal
reflects your actual system landscape.

5. Landscape Management Cleanup

5.1 Deactivate Data Suppliers
In this activity, you deactivate the data suppliers.

If you do not remove the system physically, make sure that the SLD data suppliers point to another SLD
(for example, when you move the system to another SAP Solution Manager system), or shut down the
system including the data suppliers completely. This ensures that the system is not recreated in the SLD.

Besides removing the data supplier for the technical system, you must also deactivate the other data
suppliers, for example, the database system or the host.

5.2 Print Documentation

To be able to perform the following Remove System from LMDB and Remove System from SLD activities,
print the documentation of the activities.

Both activities must be executed with this guided procedure closed, because as soon as the
decommissioned system is removed from the LMDB, this guided procedure cannot be run any more.

5.3 Remove System from LMDB

In this activity, you delete the decommissioned technical system from the LMDB (Landscape
Management Database), including database and host.

Note: It is recommended to perform this activity before the Remove System from SLD activity in order to
remove Outside Discovery data enrichment and Additional Attributes (manual changes) related to the
decommissioned system.

5.4 Remove System from SLD

In this activity, you remove the decommissioned system from the SLD (System Landscape Directory).