Blade types

Each Caplin Platform blade is a self contained set of files.

Config blade

This type of blade consists solely of configuration files. Config blades are used for the following purposes:

  • To enable and configure built-in functionality in Liberator and Transformer. A config blade is a convenient way to package related configuration options required by a built-in service. For a list of config blades in Liberator and Transformer, see Built-in blades.

  • To deploy an adapter’s configuration files without deploying the adapter’s binary. This is commonly done during development of an adapter, when you need your adapter’s configuration deployed to one or more Deployment Frameworks, but you want to run the adapter manually within your IDE.

Adapter blade

This type of blade connects to, and supplies data to, a Liberator and/or Transformer. It consists of:

  • An Integration Adapter (an executable binary file).

  • Configuration for the Adapter (including its DataSource configuration)

  • Configuration for the core components (Liberator and/orTransformer). This configuration enables the Adapter to exchange data with these core components.

Integration Adapters can be written in Java using the Caplin Integration Suite, or in C using the C DataSource API.

Service blade

This type of blade contains a module written in C, Java, or Lua that is to be loaded into one of the core components; for example, a permissioning auth (authorisation) module that is loaded into Liberator, or Transformer’s Refiner (filtering and sorting) service .

Lua is a scripting language that’s used to write Transformer modules; for more about this, see How Can I…​ Write a Lua Pipeline for Transformer.
Platform blades overview diagram showing blade types