GPAL script resolution

Your application's processes.xml file enables you to specify the script file for each process. Genesis looks for these files in three locations:

Installed modules

The primary lookup location for GPAL scripts is in the /scripts directory in each installed module on the target server. So, for every directory under $GENESIS_HOME, the process bootstrap will attempt to resolve a script file in the directory $GENESIS_HOME/module/scripts.

Site Specific scripts

It is possible to override GPAL scripts that are installed as part of either the core platform or additional platform components. To do this, create a script file with the same name (or copy the file from the installed module) to the site-specific/scripts directory.

Script files in the site-specific/scripts directory take precedence over files with the same name in the directory of an installed module.

Runtime classpath

GPAL script files can also be bundled inside jar archives. A script file can be resolved by name, provided the file is in the root directory of a jar archive that has been added to the process classpath. This is useful if you do not want to allow overrides of specific script files for security reasons.