Considering ADS Software component as an example to explain quick Java SCA telnet undeployment steps and update ticks.
Quick points:
1) ✨Direct Undeployment of SCA without undeploying SDA first is not the right method. Not sure whether it will work or not as well since no sap blogs/proof exist.
undeploy_sca name=ADSSAP vendor=sap.com - Not an correct method
2) If we just type - Undeploy name=ADSSAP vendor=sap.com then command picks ADSSAP itself as an SDA instead of SCA component.
SDA - Will be components of Main Root SCA Component
SCA - Java Component
We can see in the output - SDA Count 1 - Matchable Component not found comment.
3) Usual Undeployment method will be undeploying all SDAs under SCA (ADSSAP) (Near 20 -25 will be there)
Post undeploying SDA, we can undeploy empty SCA ADSSAP. We can find SDA information in Component INFO - NWA Link.
Undeployment steps:
Connect via telnet
add deploy
undeploy name=DocumentServicesLibrary vendor=com.adobe on_undeploy_error=stop
undeploy name=tc~fp~config vendor=sap.com on_undeploy_error=stop
.
.
Once all SDAs undeployed, Proceed undeploying empty ADSSAP SCA.
add deploy
undeploy_empty_sca name=ADSSAP vendor=sap.com (Now, Undeploy will detect ADSSAP SCA correctly)
We can also create XML and provide all SDA information inside XML. Run undeploy with that XML for easy bulk actions.
Refer - SAP Landscape Management 3.0, Enterprise Edition, Installation Guide - Undeploying using Telnet. It will have detailed information.
Checks:
To check if the SCA files are undeployed, enter the following commands:
explore name=ADSSAP
We should get error message: There is no component registered with the specified name ADSSAP.
Note 3397674 - How to apply a new ADSSAP patch
Thanks for visiting !!!
No comments:
Post a Comment