Entering content frame

Function documentation PAR Files Deployment Locate the document in its SAP Library structure

Use

The portal administrator typically uses the Archive Uploader component to upload and deploy a portal application to the portal. He or she can also import content to the portal using external tools provided by the persistence layer. In both cases, the upload consists of two steps:

Prerequisites

SAP J2EE Engine must be up and running.

Activities

Uploading a PAR File to the Application Repository

The PAR file is stored in the application repository. There is only one application repository and all PRT nodes of the SAP J2EE Engine cluster share the same content. This means that the upload procedure is done only once. The PAR upload procedure stores the whole archive in the underlyingpersistence layer. It also extracts all the information requiring fast access at runtime from the deployment descriptor portalapp.xml.

Deploying a PAR File on all PRT Nodes

Once the upload to the application repository is completed, the upload process notifies all PRT nodes. This step updates the local deployment of the portal application on each server. The update of the local deployment requires Hot Deployment capabilities, and that is why all portal applications can be released. A PRT node:

·        Checks if the application is already loaded and drops the corresponding instance

This step also checks and drops all entities (applications, components and services) that depend on the current application

·        Starts the deployment process

This process gets the PAR file from the repository and updates the local deployment by expanding the archive content

·        Restarts all portal applications that have been dropped

This graphic is explained in the accompanying text

The main purpose of the local deployment is to improve performance at runtime by providing fast access to classes and to portal application resources. The local deployment avoids additional round trips to the application repository and, in that sense, must be considered as a cache for portal applications.

Deployment Policy

The local deployment is done using the DeploymentPolicy property declared in the deployment descriptor.

·        If this property is set to “5.0”

The deployment is backwards compatible with the EP50 version of the portal. The old folder is not removed and the deployment process simply overrides the folder with the new content.

·        If the DeploymentPolicy property is missing

A regular deployment is performed; the old deployment folder is removed and then replaced by the new one. It is important to understand that the EP60 deployment logic assumes that the application does not store any configuration locally; everything should be stored in the repository.

 

 

Leaving content frame