Decommissioning

WARNING: Decommissioning operations result in non-reversible loss of data.

Decommissioning involves the removal of managed objects such as hosts, databases and technical systems. This includes removal of all related artefacts such as customer network, LMDB namespace, data from Monitoring and Alerting Infrastructure (MAI), reporting data, configuration data, logs, alerts and work-modes.

Removing a host or a technical system from the LMDB will remove all data related to the corresponding LMDB object (identified by its GUID); therefore, the LMDB cleanup is the last step of the decommissioning operation. Decommissioning requires permissions for the RSRSM_SSI_CLEANUP report and administrative access for the technical system.

If you plan to move a technical system from one customer network to another, you must first decommission this system from the old customer network.

The general approach for decommissioning is to:

  • First decommission the technical system (like AS ABAP, AS JAVA)
  • Then decommission the database used by the technical system, if it is not used by other technical systems
  • Then decommission the hosts
  • Databases and hosts can only be deleted if they are no longer used by other managed objects

Automatic Decommissioning

WARNING: Decommissioning operations result in non-reversible loss of data.

Follow this general procedure for automatic decommissioning of technical systems, including a HANA single DB:

1.    If you want to remove the technical system from the data center

a.    Plan a downtime work-mode for the technical system

b.    Shut down the technical system and all its hosts

2.    If you want to keep the technical system in your data center, but you want to remove the technical system from your SAP Focused Run installation

a.    Disable all SLD data suppliers for the technical system

b.    Disable outside discovery for all hosts of the technical system

3.    Trigger cleanup of the technical system via SA38 Report RSRSM_SSI_CLEANUP (or using the SSI Web Services) to:

a.    Cleanup all SAP Focused Run feature-specific data stores

b.    Delete the technical system from the LMDB

4.    If the technical system is still used in other SAP Focused Run or SAP Solution Manager installations, in order to avoid sending landscape data to the current SAP Focused Run installation, from which you have just removed the technical system

a.    Reconfigure and enable all SLD data suppliers for the technical system, to no longer send data to the current SAP Focused Run installation

b.    Reconfigure and enable the outside discovery for all hosts of the technical system, to no longer send data to the current SAP Focused Run installation

c.     Remove users on the technical system, which were created for data collection (see section “Technical Users in Managed Systems” in the SAP Focused Run Security Guide)

If you want to decommission a HANA MDC system, or just a HANA tenant DB, note that:

1.    SAP Note 2883329 must be implemented on your SAP Focused Run test and production systems

2.    The HANA system DB can only be decommissioned after all HANA tenant DBs have been decommissioned

3.    The HANA system DB and each HANA tenant DB must be decommissioned individually

Decommission a HANA tenant DB as follows:

1.    If you want to remove the HANA tenant DB from the data center

a.    Plan a downtime work-mode for the HANA tenant DB

b.    Disable the data supplier for the HANA system DB where the HANA tenant DB is running

2.    Trigger cleanup of the HANA tenant DB via SA38 Report RSRSM_SSI_CLEANUP (or using the SSI Web Services) to:

a.    Cleanup all SAP Focused Run feature-specific data stores

b.    Delete the HANA tenant DB from the LMDB

3.    If you want to keep the HANA system DB (since it is still used by other HANA tenant DBs)

a.    Delete the HANA tenant DB from the HANA system DB (skipping this step will cause the HANA tenant DB to reappear in the SAP Focused Run system)

b.    Enable the data supplier for the HANA system DB where the HANA tenant DB was running

Decommission a HANA system DB using the above described general procedure.

Manual Decommissioning

WARNING: Decommissioning operations result in non-reversible loss of data.

The cleanup will occur top-down, starting with the applications followed by the infrastructure components. SLG1 logs are written to provide details about the progress and result (the log UI starts automatically after report execution). The report performs some basic consistency checks.

1 - Manual Application Deactivation

Set the Lifecycle status to 'disused':

  1. From the Launchpad, open LMDB Object Maintenance UI
  2. Search for the Technical System in the right Customer Network
  3. Click 'Display' then click the 'Edit' button
  4. Change the Lifecycle Status to 'Disused'

Remove the Technical System Monitoring applications:

  1. In the SAPGUI, execute transaction MAI_TOOLS (Monitoring and Alerting Analysis Tools).
  2. Open 'Decommission Monitoring' in the 'Configuration' tab.
  3. Managed Object Name = <EXTSID>
  4. Managed Object Type = T_SYSTEM
  5. Namespace Name = Customer Namespace
  6. Select 'Delete' then 'Double check' from the Directory browser.

Remove definition for Service Availability Management (SAM) from 'FRUN Application' / 'Service Availability Management':

  1. Click the 'Service Availability Management' tab on the left.
  2. Filter the Services using your <EXTSID>.
  3. Select the row with Valid Status (Green Square).
  4. Change the 'Validity date' to 'TODAY'.
     

2 - Manual System Decommissioning

Note: If you do not plan to reuse the same Host/File system in the future, you do not need to execute Step 1 to 4. 

A - For a Technical System, Host and Database

  • Stop Outside Discovery suppliers on Host / Database (ComputerSystem / DatabaseOutsideDiscovery / MSIISOutsideDiscovery / SRDiagnosticsAgent / BCHostController):
  1. OS as root, Stop the SAP Host Agent:  /usr/sap/hostctrl/exe # ./saphostexec -stop or Redirect the OutsideDiscovery Payload.
  2. OS as root, Remove the /usr/sap/hostctrl/exe/slddest.cfg file or reconfigure it to send the payload somewhere else. 
  • Stop corresponding SDAs processes and related components. 
  1. Remove the SDA: CL_SRSM_AGENT_CLEANUP_TASK or directly on Os remove SDA process as sapadm: ps -efl | grep sapadm
  2. Remove the /usr/sap/hostctrl/SMDAgent Folder (rm -rf)
  3. Remove the HTTP destination in SM59 (search with the host name).
  • Disable all other Data Suppliers that belongs to the decommissioned system depending on the System Type, for instance:
  1. For ABAP (BCSystem / RZ70): Execute RSLDHTTPCONF and Select Delete HTTP Destination SLD_DS_* .
  2. For Java (J2EESystem): Remove or reconfigure the destination  (Config / Security / Dest) in SAP NW Administrator ( http://<host>:<HTTP port>/nwa ) as an AS Java administrator.
  3. For SAP Start Service Kernel (BCControlInstance and CentralserviceInstanceKernel): remove or reconfigure the slddest.cfg file on all instances.
  4. For SAP Start Service ABAP (ABAPInstanceKernel): remove or reconfigure the slddest.cfg file on all instances.
  5. For SAP Start Service Java (J2EEInstanceKernel): remove or reconfigure the slddest.cfg file on all instances.
  6. For SAP HANA: remove or reconfigure the slddest.cfg file in /usr/sap/<DBSID>/SYS/global.
  7. For SAP BusinessObjects Business Intelligence or SAP BOE Data Services, remove or reconfigure the /usr/sap/hostctrl/exe/connect.key file.
  8. For Apache Tomcat, remove or reconfigure the /usr/sap/<SID>/sap_bobj/tomcat/webapps/sap.com~TomcatSLDDataSupplierWEB/sldDataSupplier.properties.
  9. For any other system types, remove the payload sending to SAP Focused Run. For that, check how the Data Suppliers are setup in the Preparing Managed Systems guide.
  • Remove specific Database System Users
  1. For HANA remove the DB user Store hdbuserstore/ASE via WebService: /usr/sap/hostctrl/exe/saphostctrl"" -function SetDatabaseProperty DBCredentials=CLEAN -dbname HDB -dbinstance HDB00 -dbtype hdb -dbuser SYSTEM -dbpass Abcd1234 -dboption User=sapdbctrl -dboption Password=Abcd1234
  2. For MaxDB remove the created User Store.
  • Remove Application related data and configuration (for Hosts or Technical Systems):
  1. For each application in SAP Focused Run: Locally archive the runtime data for the system (e.g. MAI Metrics, Reporting, Logs, ...).
  2. For each application in SAP Focused Run: Cleanup the configuration data (e.g. MAI configuration stores, directory, ...).
  3. Login to SAP Focused Run system and execute report RSRSM_SSI_CLEANUP as described below.
    • Remove the technical systems
    • Remove the hosts
    • Remove the customer network
       

B - For Technical Instance Decommissioning

Execute step 1 to 4 of Section A in the decommissioned instance.

Open LMDB Object Maintenance UI, search for the associated Technical System in the right Customer Network and Remove the decommissioned instance.

Rerun SSI on the Technical System.

 

C - For Host / Database or Technical Instance Re-Integration

  • As sapadm, install the SAP Host Agent on the host following the Official Documentation.
  • Run New Host / Database (Data Suppliers: ComputerSystem / DatabaseOutsideDiscovery / MSIISOutsideDiscovery / SRDiagnosticsAgent / BCHostController)
  • Run New Technical Instance Data Suppliers:
  1. For ABAP (BCSystem / RZ70): Execute RSLDHTTPCONF and Select Delete HTTP Destination SLD_DS_* .
  2. For Java (J2EESystem): Remove or reconfigure the destination (Config / Security / Dest) in SAP NW Administrator ( http://<host>:<HTTP port>/nwa ) as an AS Java administrator.
  3. For SAP Start Service Kernel (BCControlInstance and CentralserviceInstanceKernel): remove or reconfigure the slddest.cfg file on all instances.
  4. For SAP Start Service ABAP (ABAPInstanceKernel): remove or reconfigure the slddest.cfg file on all instances.
  5. For SAP Start Service Java (J2EEInstanceKernel): remove or reconfigure the slddest.cfg file on all instances.
  6. For SAP HANA: remove or reconfigure the slddest.cfg file in /usr/sap/<DBSID>/SYS/global.
  • Check from the Agent Admin that the SDA deployment has been triggered, the SDA Configuration done, and Heartbeat Green.
  • Rerun SSI on the Database and Technical System. 

Report RSRSM_SSI_CLEANUP

The cleanup report has been designed so, that it in case an error occurs during the deletion of a given object, you can simply retry to delete that object. Check the log messages, and remove the root cause of the error before retrying the delete.

The SLG1 messages logged during the cleanup operation, will be displayed in the Cleanup Report UI.

If you want to inspect the SLG1 messages logged for a cleanup operation, after you have closed the Cleanup Report UI, you can do so via transaction SLG1. You must specify:

  • Object: AI_SSI
  • Subobject: CLEANUP

To remove a technical system from the SAP Focused Run system and the LMDB:

  1. Manually execute SA38 report RSRSM_SSI_CLEANUP
  2. Select a Customer Network
  3. Go to the Cleanup Technical System tab
  4. Select a Technical System
  5. Make your choice from the offered options
  6. Press Delete Selected Objects
  7. This will trigger the cleanup

To remove a host from the SAP Focused Run system and the LMDB:

  1. Manually execute SA38 report RSRSM_SSI_CLEANUP
  2. Select a Customer Network
  3. Go to the Cleanup Host tab
  4. Select a Host
  5. Press Delete Selected Objects
  6. This will trigger the cleanup

To remove a customer network from the SAP Focused Run system and the LMDB:

  1. Manually execute SA38 report RSRSM_SSI_CLEANUP
  2. Select a Customer Network
  3. Go to the Cleanup Customer Network tab
  4. Make your choice from the offered options
  5. Press Delete Selected Objects
  6. This will trigger the cleanup

WARNING:

  • A customer network can ONLY be deleted if no technical systems and hosts are assigned to it.
  • The associated namespace will be also deleted.

Known Issues

Decommissioning of Introscope Enterprise Manager Limitation

After the decommissioning of an Introscope EM system you may receive a warning like:

Could not delete Introscope EM properties with SAP Focused Run connection details from the Simple Diagnostics Agent. The Introscope EM may continue to send data to the SAP Focused Run system.

If this occurs, the decommissioning program has not been able to confirm that the relevant properties have been deleted from the Simple Diagnostics Agent. It is likely that the Introscope EM system still has the details for SAP Focused Run communication stored. As a consequence, the Introscope EM system may continue to send data to the SAP Focused Run system, although the technical system was successfully removed from the SAP Focused Run system and from the LMDB. In order to resolve this, you must:

  • Logon the OS of the Introscope EM system
  • Remove or rename the file <EM_HOME>/sap/<FRUN_SID>_srsm.e2emai.properties
  • In case of problems with this specific instruction you may open an incident at SV-SMG-DIA-WLY