Deployment

Grid Libraries are deployed using the resource deployment page located at Services > Services > Grid Libraries, or by using the Admin API. When a Grid Library is uploaded, it is first verified to ensure that the ZIP archive is not corrupt and that the grid-library.xml file validates against the Grid Library DTD. If there is an error, it is displayed next to the file on the Services > Services > Grid Libraries page.

The Resource Manager then replicates uploaded, valid libraries to all Engines. Variable Substitution property files also must be placed in this directory. Engines download Grid Libraries based on the attributes in the root level grid-library element. Grid Libraries whose attributes match the properties of a particular Engine are downloaded by that Engine and ignored by Engines with non-matching properties. If no attributes are specified in this element for a particular Grid Library, all Engines download it.

Adding or removing Grid Libraries or property files do not trigger an Engine and Daemon restart. It is not necessary to restart until the Engine actually needs to use the Grid Library, and even then only if necessary according to the loading procedure. If a deployed Grid Library is changed, it does cause the Daemon and Engines to restart. Also, it is the responsibility of the user not to delete Grid Libraries loaded by active Services from the Libraries page, as that might lead to library load failures for subsequently executed tasks.

If you are not using the Resource Manager for replication, you can use an alternate shared Grid Library directory. You must then set the Grid Library Path in all Engine Configurations to point to this directory, instead of the default replicated location. When changes are made to this library, you must then use the Update button on the Services > Services > Grid Libraries page on the Primary Director. This sends a message to all Engines to check and update their Grid Libraries using the Grid Library Manager.

The Resource Manager uses secure hashes as file signatures when determining if a file has changed on the Manager. All files are signed when the Manager starts. After that, a file is only signed again if the file’s last modified time has changed since the sign.