Quick start setup

 

Note

This section aims to fast track all of the setup and configuration exercises, in the event this course is run in one day instead of two or that someone needs to catchup for some reason. We highly recommend that you take the time to at least read through the setup and recreate it, in you own time.

Verify the environment has been setup correctly. Java 7 must be installed and the JAVA_HOME environment variable can be set to the root of the Java installation. This is important as a number of Caplin components rely on this variable. You can check what JAVA_HOME is set to by running "set JAVA_HOME" on Windows and "printenv JAVA_HOME" on Linux.
The Java binary must also be present on the system path which can be checked using: "java -version"

Unzip the Deployment framework to a suitable folder. Note if following this step on Windows, it is vital that you unzip using the Cygwin command and not use the Windows Archive manager (or 7-zip) as the file encoding can be incorrect and cause script errors.
unzip DeploymentFramework-6.VERSION_NUMBER.zip

Copy the following release kits into the kits folder
Linux
- Liberator-6.VERSION_NUMBER-x86_64-pc-win32.zip
- Transformer-6.VERSION_NUMBER-x86_64-pc-win32.zip


Windows
- Liberator-6.VERSION_NUMBER-x86_64-pc-linux-EL5-gnu.tar.gz
- Transformer-6.VERSION_NUMBER-x86_64-pc-linux-EL5-gnu.tar.gz
All - CaplinManagementConsole-VERSION_NUMBER-kit.zip

To install these new components run
./dfw deploy

Once finished JMX funtionality needs to be enabled for the CMC to connect to Liberator and Transformer. These blades are built in so nothing needs to be copied into kits.
./dfw activate LiberatorJMX
./dfw activate TransformerJMX

We also need to create a CMC configuration file
./dfw mon

and start the CMC
./dfw cmc

Then we can start the stack using
./dfw start

You should see the red boxes denoting Liberator and Transformer, turn blue in the CMC display indicating they are online. In your browser navigate to http://localhost:18080 and a Liberator page should load, clicking on "Status" should display some config information and the connected peers (Transformer)

You might have noticed in the startup of Liberator a message stating "Evaluation. Will shutdown in 30 minutes" this is because we are using the default 30min licenses. To prevent shutdown after 30mins we need to install a Development license. 
Copy new versions of licence-rttp.conf and license-transformer.conf
to
global_config/licenses

Now the main components are working we can install the trading, permission and pricing integration adaptors. Copy the following files into the kits folder:
- PermissioningAdapter-2013.09.26.0830.zip
- CPB_PermissioningService-6.2.0-293454.zip
- CPB_RefinerService-6.2.0-293678.zip
- PricingAdapter-2013.09.27.1138.zip
- TradingAdapter-2013.09.25.1318.zip

Before we install the new Permissioning service we must disable the default OpenPermissioning service.
./dfw deactivate OpenPermissioning
./dfw deploy

Once the new integration adaptors have been deployed they need to be configured with the host name by running:

./dfw hosts PricingAdapter localhost
./dfw hosts TradingAdapter localhost
./dfw hosts PermissioningAdapter localhost

Now everything installed and configured we can start up
./dfw start

There should be new boxes in CMC representing the three new integration adaptors. You will notice that the Trading DS will remain red. This is because it has not be able to connect to a backend pricing and trading system. We have supplied a mock trading backend that can be run using:
java -jar SimpleFXServer-supp.jar

The Trading peer should now connect to the backend and then connect to Liberator.

We have also supplied a very simple test application that can be used to interact with the system. To install it some files need to be unzipped into the htdocs folder of Liberator.
unzip the contents of testpage-supp.zip to kits/Liberator/latest/htdocs

It can be accessed using the url:
http://localhost:18080/testpage

#Please note it is bad practice to modify anything in the kits folder manually as these changes can be lost when upgrading. Normally the client application would be served from an application server like Tomcat and not from Liberator.