Resource Deployment

Service resource files that are used by Engines are centrally managed, starting at the Director. The centrally located resources on the Director are then synchronized to Managers, which then synchronize them with Engines.

Grid Libraries are the method of deploying resources to Engines. They are an archive containing a set of resources and properties necessary to run a Service, along with configuration information that describes how those resources are to be used. Grid Libraries can contain Java classes and JARs, native libraries, .NET assemblies, configuration files, Java system properties, Engine hooks, and alternate JREs needed to run a Service. They can also contain references to other Grid Libraries as dependencies. A Service Session can use a Grid Library by setting the appropriate options for the Service Type used by the session.

The build directory of the SDK includes an example ANT build script that can be used to build Grid Libraries. The examples in the SDK can be automatically packaged as Grid Libraries by using this script and included configuration files. Each Service example contains grid-library.xml and build.properties files. The build directory contains build.xml, deploy.bat, and deploy.sh, which parse the grid-library-build-properties files to create Grid Libraries.

For more information about packaging Grid Libraries, see Creating Grid Libraries. For information about deploying Grid Libraries, see the TIBCO GridServer® Administration.