Start and stop components and blades

Here’s how to start and stop the core Platform components and any Adapter blades 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
Stopping
Removing (cleaning) log files

Starting

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.

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

./dfw start
To start just the core components (Liberator, Transformer), enter the command
```
./dfw start servers
```
To start just Liberator, enter the command
```
./dfw start Liberator
```
To start just Transformer, enter the command
```
./dfw start Transformer
```
To start one or more Adapter blades, but not the core components, enter the command
```
./dfw bladename1 bladename2 ...
```

If the platform components and Adapter blades are deployed on more than one server machine, you’ll need to 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.

Stopping

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

./dfw stop
To stop just the deployed core components (Liberator, Transformer), enter the command
```
./dfw stop servers
```

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.

Removing (cleaning) log files

To stop all the deployed core components (Liberator, Transformer) and all the Adapter blades that you’ve activated, and remove all the core components' log files, enter the command

./dfw clean
To stop just the deployed core components (Liberator, Transformer) and remove their log files, enter the command
```
./dfw clean servers
```
To clean Adapter Blades and/or core components, and then immediately restart them, enter one of the commands below:
- ./dfw cleanstart
- ./dfw cleanstart servers

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