Activate a built-in blade

It’s easy to activate 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.

Activating a built-in config blade

To deploy a built-in config blade, follow the steps below:

  1. Enter the command below to stop core components and integration adapters:

    $ ./dfw stop

  2. Run the dfw versions command to check the state of built-in Config blades:

    $ ./dfw versions
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

  3. 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, to deactivate the LiberatorWebsite blade and activate the MinimalLiberatorWebsite blade, enter the commands below:

    $ ./dfw deactivate LiberatorWebsite
$ ./dfw activate MinimalLiberatorWebsite

  4. Enter the command below to restart core components and integration adapters:

    $ ./dfw start

Mutually 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 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: