Blade naming conventions
Each Platform blade that is deployed to a Deployment Framework must have a unique name. When developing a new Platform blade, follow these naming conventions that will make it easier to maintain the blade in future:
Give the blade a name reflecting the feature that it implements.
For example, TradeFXBlade, for an Adapter blade that implements an Integration Adapter dedicated to FX Trading.
The name of the root directory where the blade files are located in the Deployment Framework must be the blade name.
For example, the blade called TradeFXBlade, must be located in the directory <Framework-root>/kits/TradeFXBlade
For another example of this, see Create the Adapter blade’s directory structure in Create a C-based Adapter blade.
For C-based Adapter blades, in any DataSource configuration that refers to the Adapter, the
remote-nameoptions of the
add-peerconfiguration item should contain the name of the blade.
For examples of this, see Set up Liberator configuration and Set up Transformer configuration in Create a C-based Adapter blade
If the blade provides a data service to Liberator, the
service-nameoption in the
add-data-serviceconfiguration item of the Liberator configuration by default contains the name of the blade, though you may wish to change this to a more meaningful name.
For an example of this, see Set up Liberator configuration in Create a C-based Adapter blade.