Local Deployment 
Overview
The directory structure after deploying the “irj.ear” file looks as follows.
This structure can be changed at any time. The Java code should not assume that the structure would remain the same in the next release. The Portal Runtime API provides methods for abstracting from the real location of resources.
<SAP J2EE Engine>\<server>\services\servlet_jsp\work\jspTemp | +-- irj | +-- portalapps <== WEB resources | | | +-- <myApplication> <== a subfolder for each portal application | | | +-- images | +-- scripts | +-- ... | +-- WEB-INF | | | +-- lib | +-- portal | | | | | +-- logs | | +-- lib | | | | | +-- system | | | +-- lib | | | | | +-- portalapps <== Non-WEB resources | | | | | +-- <myApplication> <== a subfolder for each portal application | | | | | +-- classes <== API: java classes only | | +-- lib <== API: jar files only | | | | | +-- private <== Implementation of the portal application | | | +-- classes <== CORE: java classes only | | | +-- lib <== CORE: jar files only | | | | | +-- portalapp.xml <== deployment descriptor | | | | | +-- META-INF <== deployment descriptor | | +-- MANIFEST.MF <== Manifest file | | | | | +-- deployment |
Local Deployment of Portal Applications
A portal application is deployed locally either at startup or when it is first called (for example through an HTTP request). The PAR file content is extracted and split into two parts:
· The public part contains Web resources (images, scripts, style sheets) that are to be accessible from the user-agent (that is, the browser)
· The private part (that is, the PORTAL-INF folder) is deployed in a secure folder which is not accessible from the browser (that is, in WEB-INF). The private part contains the code (API and core implementation), the deployment descriptor and some application-specific files
The local deployment is a copy of the original PAR file content stored in the application repository. The local deployment is a kind of cache. This means that a change made in the deployment descriptor deployed locally may have no impact at runtime since PRT may use the original version instead.