PAR Format
This section contains the following:
PAR File Format
The following table describes the PAR file format.
|
File/Directory under PAR Directory |
Sub Directory |
Description |
|---|---|---|
|
META-INF |
/MANIFEST.MF |
The manifest.mf file describes what is contained in the exported file. |
|
/dp |
/name.properties |
Contains component service attribute values. |
|
/name.xml |
Contains display profile document. |
|
|
/pbfiles |
/providerClassBaseDir |
Contains customized desktop provider classes. |
|
/templateBaseDir |
Contains desktop JSPs and templates. |
|
|
/templateBaseDir/classes |
Contains desktop provider resource bundle files. |
|
|
/communityTemplateBaseDir |
Contains community templates and properties files. |
|
|
/static |
Static files to be deployed as part of the portal war. This maps to (by default in UNIX platform) /var/opt/SUNWps/portals/portal-ID directory. |
|
|
/war |
War files to be deployed. This maps to (by default in UNIX platform) /var/opt/SUNWps/portals/portal-ID/war directory. |
|
|
.jar |
JAR files associated with providers. |
|
|
Java-class-files |
Class files associated with providers. |
PAR Directory Structure
The following table describes the PAR directory structure.
|
Directory under PAR Directory |
Files and Sub Directories |
Description |
|---|---|---|
|
/dt |
DPMapping.properties |
Mapping file properties contains name -> dn mapping |
|
/name.properties |
The name should be defined in the DPMapping.properties file. |
|
|
/name.xml |
There could be multiple files start with the same name, appended by -XXX.xml, files start with same name will be merged into one XML file. The name must be defined in the DPMapping.properties file (with exception of the name global). For example, global-1.xml and global-2.xml will be merged into global.xml, and global should be defined in the DPMapping.properties file. |
|
|
/pbfiles |
/providerClassBaseDir |
This directory structure maps to (by default on UNIX platform) /var/opt/SUNWps/portals/portal-ID/desktop/classes. Under this directory, you can have customized provider classes in packaged subdirectories. |
|
/templateBaseDir |
This directory structure maps to (by default on UNIX platform) /var/opt/SUNWps/portals/portal-ID/desktop. Under this directory, you can have anoymous/, default/, sampleportal/ etc. |
|
|
/communityTemplateBaseDir |
This directory structure maps to (by default on UNIX platform) /var/opt/SUNWps/portals/portal-ID/communitytemplates directory. |
|
|
/static |
/web-src |
Can contain any customized files in open WAR. The files in this directory will be included in the par/static directory, and will be imported into portal-data-dir/web-src directory. |
|
/war |
Contains war files, note that is the portal war file is will not be added in the par file |
- © 2010, Oracle Corporation and/or its affiliates