Built-in blades

Liberator and Transformer 6.2.1 onwards come with built-in Config blades that implement some of the basic features of a Caplin Platform trading system. Version 6.2.0 and later of the Framework detects and uses these built-in blades if they exist in the Liberator and Transformer kits that you deploy.

If a 6.2.0 (or later) Framework doesn’t detect any built-in blades when deploying Liberator and/or Transformer (because the Liberator/Transformer components are versions older than 6.2.1), it’ll use its own versions of the built-in blades.

If you deploy version 6.2.1 (or later) Liberator or Transformer in a pre-6.2.0 Framework, the Framework won’t use the blades that are built-in to Liberator/Transformer; it will always use the blades supplied with the Framework.

Config blades built into Platform components

Here’s a table that lists the Liberator and Transformer built-in Config blades at the time of publication. A blade marked with a tick (check mark), defaults to the active state in the Deployment Framework. For more about blade states, see How Can I…​ Activate and deactivate blades.

Blade name Platform Component Use Active BY DEFAULT? Notes

BlotterExport

Liberator

Defines blotter export configuration for the Liberator Web Module.

DemoDataSource

-

Contains configuration for the C-based demonstration Integration Adapter provided with the Liberator kit.

This blade is always supplied with the Deployment Framework.

DirectConnection

Liberator

Defines the configuration for direct connections between clients and Liberator.

Note 1

DirectSSLConnection

Liberator

Defines the configuration for direct secure (SSL) connections between clients and Liberator.

Note 1

HTTP

Liberator

Defines HTTP configuration for Liberator, using the deployment specific configuration defined in global_config/environment.conf.

Note 1

HTTPS

Liberator

Defines HTTPS configuration for Liberator, using the deployment specific configuration defined in global_config/environment.conf.

Note 1

LiberatorJMX

Liberator

Defines JMX monitoring configuration for Liberator.

Note 1

LiberatorWebsite

Liberator

Enables Liberator’s HTTP interface and serves status and diagnostic tools suitable for debugging and development. Not supported in production environments.

Note 2

MinimalLiberatorWebsite

Liberator

Enables Liberator’s HTTP interface and serves a simple index page ("This is Liberator"). Suitable for production environments.

Note 2

OpenPermissioning

Liberator

Defines open authentication configuration for Liberator.

Note 3

Note 5

JavaOpenPermissioning

Liberator

A Java implementation of open authentication configuration for Liberator.

Note 3

Note 5

TokenPermissioning

Liberator

Defines Tokenauth authentication configuration for Liberator.

Note 3

Note 4

Note 5

ServerIdentification

Liberator

Prevents the Liberator’s name, version number, and hostname from being transmitted to client applications in HTTP response headers and in other messages, which is considered to be good security practice. If you deactivate this blade, this information is sent to clients.

TransformerJMX

Transformer

Defines JMX monitoring configuration for Transformer.

Note 1

PersistenceService

Transformer

Persists Transformer objects to a file or database

PersistenceServiceClient

Transformer

Allows StreamLink clients remote access to the PersistenceService

Note 1: The built-in blades HTTP, HTTPS, DirectConnection, DirectSSLConnection, LiberatorJMX, and TransformerJMX use particular port numbers. You may need to change the port number settings for some or all of these blades to conform to your own port allocation standards. See Change configuration macro settings in How Can I…​ Change server-specific configuration.

You can find out which port numbers are configured for built-in blades that are active, by running the command ./dfw info

Note 2: The built-in blades LiberatorWebsite and MinimalLiberatorWebsite are mutually exclusive. Only make one of these blades active at a time.

Note 3: The built-in blades OpenPermissioning, JavaOpenPermissioning, and TokenPermissioning are mutually exclusive. Only make one of these blades active at a time. The Deployment Framework command utility, dfw, will warn you if you attempt to activate more than one of these blades at a time, and it won’t let you start the system.

Note 4: This blade is available from Liberator version 6.2.6 onwards and can be used when the Liberator is deployed in Deployment Framework version 6.2.1 onwards.

Note 5: There’s also a Caplin-supplied Permissioning Service blade (not built-in) that enables Liberator to handle permissioning data received from a Permissioning Adapter. See Caplin-supplied blades.

See also: