Deploy a built-in blade

It’s easy to deploy the built in Config blades that come with Liberator and Transformer.

In the following steps you’ll be using the dfw command of the Deployment Framework. Before entering any dfw command as ./dfw <command-name>, make sure your current (working) directory is set to the Deployment Framework’s topmost directory.

For a list of dfw commands, click here.

  1. After you’ve deployed the Framework’s core components (Liberator, Transformer) using the ./dfw deploy command, check the state of the components' built-in Config blades by entering the command

    ./dfw versions

    Here’s a typical listing produced by the ./dfw versions command:

    Deployment Framework           6.0.4-268982

   Core components                Version
   -----------------------------------------------------------
   Liberator                      6.0.5-268662
   Transformer                    6.0.4-268662

   Deployed blades                Version            State
   -----------------------------------------------------------

   Built-in blades                                   State
   -----------------------------------------------------------
   BlotterExport                                     Inactive
   DemoDataSource                                    Inactive
   DirectConnection                                  Active
   HTTP                                              Active
   HTTPS                                             Inactive
   JavaOpenPermissioning                             Inactive
   LiberatorJMX                                      Inactive
   LiberatorWebsite                                  Active
   MinimalLiberatorWebsite                           Inactive
   OpenPermissioning                                 Active
   ServerIdentification                              Active
   TransformerJMX                                    Inactive

  2. Deactivate the built-in blades that you don’t need but are currently active, and then activate those you do need but are currently inactive. For example:

    ./dfw deactivate LiberatorWebsite
./dfw activate MinimalLiberatorWebsite HTTPS LiberatorJMX

  3. For the changes to take effect, restart the Platform’s core components and Integration Adapters:

    ./dfw start

Mutally exclusive blades

The built-in blades OpenPermissioning and JavaOpenPermissioning are mutually exclusive, as are LiberatorWebsite and MinimalLiberatorWebsite. Only make one blade of each pair active at a time.

Setting port numbers

The built-in blades HTTP, HTTPS, DirectConnection, TransformerJMX, and LiberatorJMX 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 (see Check port numbers 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

See also: