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.
|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||Provides a full status page for Liberator that is suitable for development.||||Note 2|
|MinimalLiberatorWebsite||Liberator||Provides a minimal status page and associated configuration for Liberator that is suitable for secure product deployment.||||Note 2|
|OpenPermissioning||Liberator||Defines open authentication configuration for Liberator.||||Note 3
Defines Cfgauth authentication configuration for Liberator.
Note: Do not use CfgPermissioning in production.
|JavaOpenPermissioning||Liberator||A Java implementation of open authentication configuration for Liberator.||||Note 3
|TokenPermissioning||Liberator||Defines Tokenauth authentication configuration for Liberator.||||Note 3
|XMLPermissioning||Liberator||Defines XMLauth authentication configuration for Liberator.||||Note 3
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.
Note 3: The built-in blades OpenPermissioning, CfgPermissioning, JavaOpenPermissioning, TokenPermissioning and XMLPermissioning 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 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.