This section describes how you deploy, manage and undeploy an application on AS Java. Refer to the Java EE specification about the specifics of the deployment phase.
Deployment is the final step before starting your application. When the application is deployed, its components are allocated to the corresponding containers that can handle them appropriately.
We recommend you use the SAP NetWeaver Developer Studio when you need to develop an application from scratch and deploy it. For more information about developing an application with the SAP NetWeaver Developer studio, see Tasks.
If you have an already-developed application, you can deploy it with SAP NetWeaver Developer Studio as described in this section.
Hot deployment it is the ability to redeploy applications without restarting the cluster. You have to restart the application being updated, however, all other components that are not connected to it keep running without this connection.
The user that you use to log on to AS Java must have the appropriate security actions. More information: Security Actions Necessary to Perform Deploy Operations
More information: Deploying and Undeploying with SAP NetWeaver Developer Studio
If you want to use non-SAP Java EE compatible deployment tools to deploy your Java EE components on AS Java, you have to use the Java EE Deployment library provided with AS Java. It implements the JSR 88: Java EE Application Deployment specification and provides the required APIs to the third-party tools based on J2EE 1.4 or Java EE 5.
More information: Deploying Applications with Third-Party Deployment Tools
You need Ant scripts to automate repeated tasks.
More information: Using Ant Scripts to Work with SDAs
You can use shell scripts to perform single operations over SAP-specific or standard JavaEE archives.
More information: Using Shell Scripts to Work with SDAs