Decommissioning

Introduction

Decommissioning involves the removal of managed objects such as hosts, databases and technical systems. This also includes removal/archiving of all related artefacts such as customer network, LMDB namespace, MAI data, reporting data, configuration data, logs, alerts and work-modes.

WARNING: Decommissioning operations result in non-reversible loss of data. Removing a host or a technical system from LMDB will remove all the data related to the corresponding GUID; therefore, the LMDB cleanup must be the very last step of the decommissioning operation. Decommissioning might require admin and root OS permissions.

Note: If a host or a technical system has been accidentally removed from LMDB, you can still set it up again using the Managed System Setup Documentation by executing Outside Discovery and re-running all relevant Data Suppliers. In this case, SSI must be re-executed as well.

Automatic Decommissioning

We consider technical systems, hosts, customer networks and LMDB namespaces. Data is deleted so that it does not interfere if the same system is re-configured from scratch. The result is a program for cleaning up all data for all FRUN applications and infrastructure components.

Cleanup can be triggered via SA38 Report RSRSM_SSI_CLEANUP

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. Databases and hosts can only be deleted if they are no longer used by any technical system.

Note: If you plan to move one managed system from one customer network to another, you must first decommission this system from the old customer network.

Note: This report still had some issues in FRUN 1.00 FP00. The FRUN 1.00 FP01 version of the report has all known issues solved.

 

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 SAM definition 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 Datasuppliers 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 BusinessObject Business Intelligenceor SAP BOE Data Services, remove or reconficure 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 paypload sending to Focused Run. For that, check how the datasuppliers 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 FRUN: Locally archive the runtime data for the system (e.g. MAI Metrics, Reporting, Logs, ...):
  2. For each application in FRUN: Cleanup the configuration data (e.g. MAI configuration stores, directory, ...): login to FRUN <EXTSID> System and execute those 2 reports:

For Technical Systems, from SAPGUI:

-manually execute SA38 report RSRSM_SSI_CLEANUP
-select a Customer Network
-go to the Cleanup Technical System tab
-select a Technical System
-press Delete Selected Objects
-this will trigger the following cleanup Tasks:

Lifecycle: CL_LMDB_SSI_CLEANUP_TS_DISUSED or Set lifecycle state manually from LMDB to Disused.
SAM: CL_SAM_MSC_CLEANUP_TECHSYS
EWA: CL_SERV_MSC_CLEANUP_TECHSYS
WWM: CL_MSC_CLEANUP_TECHSYS
CCDB: CL_COF_DEL_INTF
TA: After removeal of SDA, no additional cleanup required
SYSMON: CL_MAI_AUTO_DECOMMISSIONING
SSI: CL_SSI_CLEANUP → RSRSM_SSI_CLEANUP 
LMDB: CL_LMDB_SSI_CLEANUP_TS_DELETE

For Hosts, from SAPGUI:

-manually execute SA38 report RSRSM_SSI_CLEANUP
-select a Customer Network
-go to the Cleanup Host tab
-select a Host
-press Delete Selected Objects
-this will trigger the following cleanup Tasks:

CCDB: CL_COF_DEL_INTF
SSI: CL_SSI_CLEANUP
LMDB: CL_LMDB_SSI_CLEANUP_HOST_DEL

  • Remove Customer Network:

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.
-Hosts will only be deleted if they are not used by a technical system.
-Before proceeding with a landscape cleanup, first remove the technical systems and then the databases.

  • To remove a customer network from the 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

 

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 Datasuppliers:
  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 Databse and Technical System. 

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 Focused Run connection details from the Simple Diagnostics Agent. The Introscope EM may continue to send data to the 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 Focused Run communication stored. As a consequence the Introscope EM system may continue to send data to the Focused Run system, although the technical system was successfully removed from the 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