CA Release Automation 6.1 now allows for applications that have deployments to be removed, previously you could not delete an application once a deployment has been run. This Tech Tip has details on how the delete process works and also details on how you can monitor the progress of the deletion. Very large applications can take a longtime to delete (several hours) but the delete process runs as a background process and this will have a minimal overhead on the performance of the management server.
Note: A fix was created for the delete function after the 6.1 GA release to resolve an intermittent issue with the delete function so please ensure you are using the latest Release Automation 6.1 build before using the delete function. Patches for CA Release Automation can be found at this location CA Release Automation Solution and Patches
To Delete an application, login to the ROC and click on the designer tab and select the application model from the drop down.
Select the application to be deleted from the application drop down and click on the trash can icon
The following warning dialog is displayed. Only continue if you want to remove all reference to the selected application
The application deletion will start and you have the option to continue the delete process in the background.
If you choose to run the application deletion in the background, you can check the status of the deletion in the following locations:
1 The deleting application is renamed as shown in the screenshot below.
2 A log file is created on the management server to track the status for the application deletion. The log files is called DeleteApplication.log and can be found in this location /opt/CA/ReleaseAutomationServer/logs
This is a sample extract from the DeleteApplication.log, The last line in the long shows that the application deletion has completed and the time took
2016-05-06 03:40:19,517 [http-nio-8080-exec-7] DEBUG (DeleteApplication:1108) - after - remove all categories. Took 20 ms
2016-05-06 03:40:19,517 [http-nio-8080-exec-7] TRACE (DeleteApplication:1111) - Remove published flows
2016-05-06 03:40:19,517 [http-nio-8080-exec-7] DEBUG (DeleteApplication:1112) - before - remove published flows
2016-05-06 03:40:19,518 [http-nio-8080-exec-7] DEBUG (DeleteApplication:1122) - after - remove published flows. Took 1 ms
2016-05-06 03:40:19,518 [http-nio-8080-exec-7] TRACE (DeleteApplication:1125) - Remove component from server types
2016-05-06 03:40:19,576 [http-nio-8080-exec-7] DEBUG (DeleteApplication:1298) - Deleting Revision Mapping for application : 126
2016-05-06 03:40:19,581 [http-nio-8080-exec-7] DEBUG (DeleteApplication:1301) - Deleting Parameter values and folders for application : 126
2016-05-06 03:40:19,675 [http-nio-8080-exec-7] DEBUG (DeleteApplication:1304) - Delete application 126
2016-05-06 03:40:20,914 [http-nio-8080-exec-7] DEBUG (DeleteApplication:168) - delete application id : 126, name : Cars-import-2016-05-06 03:39:58.277 finished. Took a total of 6 seconds
3 A JMX method has also been created to monitor the status of the deletion, to access the JMX method login to the JMX console on the management server, the default port for JMX is 20203.
Scroll down to the Domain: noliocenter and click on the info type.
Find the operation called listAllDeleteApplicationsProgress and click on the corresponding Invoke button on the right hand side
If a delete process is running you will see the following output, if nothing is returned from this operation then this will indicate that no delete application operations are currently active.
