If you create a custom module (see the ATG Platform Programming Guide), you can use the module’s MANIFEST.MF
file to specify paths to the module’s resources, as follows:
ATG-Class-Path
: Specify a space-delimited set of paths to module resources that contain classes required by the module. For example:ATG-Class-Path: lib/resources lib/classes.jar
Oracle ATG Web Commerce adds the
ATG-Class-Path
value to theCLASSPATH
as each module is processed.ATG-Config-Path
: Specify a space-delimited set of paths to module resources that provide Nucleus configuration files needed by the module’s server application components. For example:ATG-Config-Path: config/config.jar config/oca-ldap.jar
Oracle ATG Web Commerce adds the
ATG-Config-Path
value to the configuration path.Note: The path names in a module’s
ATG-Class-Path
andATG-Config-Path
settings are relative to the module’s root, not to the<ATG10dir>
install directory.
In the MANIFEST.MF
file, the ATG-Required
attribute specifies which modules the custom module requires to start up. ATG-Required
ensures that a given module’s manifest is processed after it processes all the modules that the module depends on. For example, if you want to place the config
directory for your custom module after the DPS config
directories in the configuration path, configure the attributes as follows:
ATG-Config-Path: config/
ATG-Required: DPS