This page describes directory structure of the Deployment Framework.
The Deployment Framework has the following directory hierarchy. Files and directories packaged with the framework are shown in black; files and directories added as a result of deploying components are shown in grey.
The Framework uses this directory to manage which blades are active.
A command-line interface (CLI) for managing the Framework and blades. You can perform any Framework operation by running the dfw utility with the appropriate command parameter.
To get a list of all the possible Framework commands, type: ./dfw help
To run a Framework command, type: ./dfw <command>
Also see the list of dfw commands on this web site.
This directory contains documents about the Framework, and the associated release note.
This directory holds files and directories concerning configuration that is global to the Framework. To customise the configuration, only change files that are in the global_config directory and its subdirectories. All other configuration files in the Framework and in Caplin supplied blades are read-only and must not be edited.
Defines configuration macros that are server specific, such as the port numbers of the core components and the location of the Java Runtime Environment (JRE). The default settings are defined in the included file environment-defaults.conf.
Defines the servers that core components and any Adapter blades run on. You must update this file to reflect the deployment - you usually do this by running the Framework command
./dfw hosts. Note that an Integration Adapter blade consists of an executable binary file in addition to its configuration and core component configuration, so you need to define which server(s) its executable will run on.
A file that defines the names of global fields used in DataSource messages.
When components are deployed, any licenses required by these components must be placed in this directory. The Liberator license must be named license-rttpd.conf, and the Transformer license must be named license-transformer.conf.
Any SSL keys required by the system must be placed in this directory, including the public key file for Caplin KeyMaster.
This directory contains files that you can update to change configuration; for example, to make the Liberator log events at DEBUG level instead of INFO level.
When you deactivate a blade, any configuration overrides that apply to it are moved from the overrides directory to the inactive-overrides directory. When you subsequently activate the blade again, its configuration overrides are moved from inactive-overrides back to overrides.
The default directory where configuration information created by the
./dfw dumpcommand is located.
This directory initially contains the Framework’s built-in Caplin Platform blades and some scripts:
Used on Windows to ensure that links in the kit are created correctly.
This directory holds configuration files containing server specific configuration for the core components.
This directory contains some Cygwin utilities that are used by the Framework scripts, and a utility script (information.sh) used by the built-in blades.
A key feature of the Deployment Framework is the modularisation of configuration. Each DataSource component is deployed to the framework as a blade containing the application binary and configuration for itself, Liberator (optional), and Transformer (optional).
When you start a DataSource application under the Deployment Framework, it loads a configuration file from the
etc/ directory in its working directory.
Each of the configuration files above use the file-inclusion directive
include-file to include a series of configuration files from the Deployment Framework and, in the case of Liberator and Transformer, other active blades.
By deploying (
dfw deploy) and deleting (
dfw delete) components, and by activating (
dfw activate) and deactivating (
dfw deactivate) configuration blades, you move configuration into and out of two key Deployment Framework directories:
global_config/overrides. Liberator and Transformer’s configuration files contain wildcard file inclusions to include configuration from these two directories:
The following diagrams illustrate the chain of configuration-file inclusion when you run a component in the Deployment Framework. For information on how to dump the full configuration chain for a component, see the Deployment Framework command
Files and directories that a server administrator can customise at deployment time are shown in green. All other files and directories are either internal to the Deployment Framework or internal to a DataSource application.