Deployment of Applications 

Once you create a portal application and bundle it into a PAR file, it must be deployed to a portal, which can done in the following ways:

●      Archive Uploader Tool: A single PAR can be uploaded by the Archive Uploader, which is available in the portal at System Administrator à Support à Portal Runtime à Administration Console.

This method is used by administrators and developers.

For more information, see Deploying Applications Via the Archive Uploader.

●      Eclipse Plug-in: A single PAR can be uploaded from the NetWeaver Developer Studio directly into a portal via the PAR Export feature of the portal plug-in for Eclipse.

This method is used by developers.

For more information, see Managing PAR and JAR Files in the Project.

●      Business Package: A collection of PARs and portal content can be packaged together and deployed via the SAP Deployment Manager.

This method is generally used by administrators.

For more information, see Business Package Administration.

●      EAR File: PAR files can be included in a standard J2EE EAR file, and the EAR file can be deployed to the SAP J2EE Engine.

This method is used by administrators and developers.

For more information on packaging a PAR in an EAR file, see Packaging PARs in J2EE Applications.

For more information on deploying EAR files, see Deploying Archives.

No matter what method is used to deploy an application, the application is placed into the application repository and a copy is placed on each node in the cluster. For more information on the application repository, see Application Repository.

The actions that occur during deployment are described in Deployment Flow.