Blog Post on Deployment of EAR file with Telnet command

[jaskaran_singh1991]

Introduction

As a Basis Administrator, many of the times we get requests from the developers to deploy EAR (Enterprise Archive) files in the SAP system.

 

These files can be deployed via many available tools provided by SAP and one of them is deploy via the telnet administrator tool.

 

Just for the reference to consultant, we have different files which can be deployed or undeployed like .SDA (Software Deployment Archive), SCA (Software Component Archive), .EAR (Enterprise Archive) or .WAR (Web Archive) files.

 

Deployment Process

1. Ask Developer to provide the EAR file and copy in on the local server


2. Check the instance number from the profile


3. Use command telnet localhost

Telnet Login command

 

4. This tool mainly ask for the administrator user and credentials

Administrator Login

 

5.   Once the connection to tool is successful, use below command to deploy the file.

 

deployment

  6.   It will show the summary of components deployed as well

 

Summary logs

 

7. Post this you will able to see the timestamp of deployment from the Netweaver login. My file was related to a job definition so post deployment I was able to check this in nwa

 

NWA check

 

Conclusion

As mentioned earlier, expertise on Telnet commands can help Basis consultants to easily deploy the files resulting in time saving.

References

SAP has multiple notes based on this like 2462712, 1715441 : Deploy/Undeploy/Force Redeploy EAR/WAR/RAR/SDA files on SAP AS JAVA and SAP KBA ##2553568 : Undeploy SCA (Software Component Archive) on SAP AS JAVA 

 

https://blogs.sap.com/2012/08/14/undeploying-sca-sda-ear-war-files-on-j2ee-servers-on-netweaver-rele...

 

NOTE: Undeployment operations as such are not supported and should be used only in cases where the SAP Basis Admin is well versed with the system landscape and the repercussions of this activity. There is no support for undeployment issues; if unknowingly a component is deployed, the official recommendation is to restore the system to the previous state it was before the deployment was triggered. Hence, you should always take a full offline backup before commencing deployment.

Existing dependencies have to be taken into account while deploying/undeploying. For more details on this, check:

 

Disclaimer: This blog is based on my personal insight and is for reference purposes only. Please follow the due diligence and standard SAP notes for complete technical guides and implementation for your project scenarios.

 

Please do like and ask questions in case of any queries.