Start and stop components

Here’s how to start and stop Liberator, Transformer, and integration adapters on a server machine.

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.

Contents:

Starting components
Stopping components
Clean stop
Clean stop and restart

Starting components

To start all the deployed core components (Liberator, Transformer) and all the Adapter blades that you’ve activated, use the dfw start command:

Start all Caplin Platform components

./dfw start

Start just Liberator and Transformer

./dfw start servers

Start Liberator only

./dfw start Liberator

Start Transformer only

./dfw start Transformer

Start individually named components

./dfw start <bladename1> <bladename2> ...

If the platform components and Adapter blades are deployed on more than one server machine, run the start command on each of the machines where the target core components and/or blades are located.

When you’ve changed the configuration of a production system, we recommend that you run the dump command immediately, before restarting the system. The most up-to-date configuration data will then be readily available if Caplin Support need it to help fix a problem with your running system. If you don’t run dump before restarting, you’ll have to stop the running system to get the configuration needed to diagnose a fault, or copy the configuration manually from the various directories where it’s located.

If your Platform deployment is Windows-based deployment and the core components and Adapter blades are deployed on more than one server machine, before you start everything up, first add all the ports used for the components to the Windows Firewall exceptions on each machine. This will make sure that Windows Firewall doesn’t reject connection requests when the components and Adapters start up.

Stopping components

To stop all the deployed core components (Liberator, Transformer) and all the Adapter blades that you’ve activated, use the dfw stop command:

Stop all Caplin Platform components

./dfw stop

Stop just Liberator and Transformer

./dfw stop servers

Stop Liberator only

./dfw stop Liberator

Stop Transformer only

./dfw stop Transformer

Stop individual components

./dfw stop <bladename1> <bladename2> ...

If the platform components and Adapter blades are deployed on more than one server machine, you’ll need to run the stop command on each of the machines where the target core components and/or blades are located.

Clean stop

To stop active Caplin Platform components and delete their log files, run the dfw dfw clean command.

Stop and clean all active components

./dfw clean

Stop and clean Liberator and Transformer only

./dfw clean servers

Clean stop and restart

To stop, clean, and restart active Caplin Platform components on the host, run the dfw cleanstart command.

Stop, clean, and restart all active components

./dfw cleanstart

Stop, clean, and restart Liberator and Transformer only

./dfw cleanstart servers

If the platform components and Adapter blades are deployed on more than one server machine, you need to run the clean or cleanstart command on each of the machines where the target core components and/or blades are located.