A module must include a META-INF
directory containing the manifest file MANIFEST.MF
. For example, the manifest used by the DPS module is located at:
<ATG11dir>/DPS/META-INF/MANIFEST.MF
Manifest Attributes
You can set a number of manifest attributes to specify the module’s environment and resources:
Manifest attribute | Description |
---|---|
| The CLASSPATH to use for the assembled EAR file. This attribute overrides attribute |
| Files to exclude from the assembled EAR file. By excluding unnecessary files, you can reduce the size of the EAR file. |
| The path to the directory that contains the configuration files for the named configuration layer |
| A space-delimited set of paths to module resources that contain classes required by this module, either Paths are relative to the module’s root directory. These libraries and directories of classes are imported into the |
| A space-delimited set of paths to module resources that contain classes required by the module’s client-side features. |
| A space-delimited set of paths to module resources that provide Java Help help-sets to the module’s client application. For example, the
|
| A space-delimited set of paths to module resources that provide Nucleus configuration files needed by the module’s application components. These can be |
| One or more EAR files for this Oracle Commerce Platform module whose J2EE modules are to be included in the assembled application. |
| One or more EJB modules for this Oracle Commerce Platform module to include in the assembled application. |
| A space-delimited set of paths to module resources that provide Nucleus configuration files. These configuration files are appended to the configuration path when you enable the Paths are relative to the module’s root directory. For more information about the |
| A Nucleus pre-initializer required for this module, the name of a class that implements interface |
| A space-delimited set of module names, specifying modules on which this module depends. If you specify this module when you run the application assembler, the modules listed here also are included in the application. When the application starts, the manifests of the modules listed here are processed before the current module’s, in least-dependent to most-dependent order . Note: You should usually set this attribute to include |
| One or more web applications to include in the assembled application for this Oracle Commerce Platform module. |
Individual Module Resource Entries
A module’s manifest can contain one or more entries for individual resources. The manifest must include an entry for each resource that is automatically downloaded to the client. For example:
Name: help/das_ui_help.jar ATG-Client-Update-File: true ATG-Client-Update-Version: 3.0.2 build 42
At a minimum, a resource entry must set ATG-Client-Update-File
to true. The following table shows all attributes that can be set for each resource:
Resource attribute | Description |
---|---|
| Optional, specifies whether to copy the resource into EAR files. |
| Required, this attribute must be set to true to enable auto-downloading of the file. |
| Optional, a SHA digest of the file in Base-64 form, permitting checking of the resource’s version and integrity. |
| Optional, a MD5 digest in Base-64 form, permitting checking of the resource’s version and integrity. |
| Optional, a version string that specifies the resource’s version, overriding any |