Troubleshooting Caplin FX Corporate

This page outlines a checklist of tasks to perform when troubleshooting issues with Caplin FX Corporate.

Liberator status page

Login to the Status page in Liberator’s built-in website and check that all DataServices are running normally.

Liberator’s Status web page, available when Liberator’s LiberatorWebsite blade is activated, provides a one-page overview of Liberator, user sessions, DataSources and DataServices.

Do not enable the LiberatorWebsite blade in production environments.

Java application server

Check the following aspects of the server.

Check the FX Corporate web-app has deployed

Check the FX Corporate web-app has deployed correctly.

For example, in Apache Tomcat, check that the FX Corporate WAR is no longer present in Tomcat’s webapps directory.

FX Corporate’s web-application context

Check that the environment entries in FX Corporate’s web-application context are correct. These entries provide the FX Corporate application with the address and port of the primary and secondary Liberator servers in your infrastructure.

For example, in Apache Tomcat the web-application context for FX Corporate is stored in the file CATALINA_BASE/conf/Catalina/localhost/<fx-corporate-webapp-name>.xml. An example context file is shown below.

<?xml version='1.0' encoding='utf-8'?>

<Context>

    <!-- This allows us to expose the terms folder -->
    <Resources>
        <PostResources className="org.apache.catalina.webresources.DirResourceSet"
            base="../conf/resources" webAppMount="/resources" />
    </Resources>

    <!-- Default set of monitored resources -->
    <WatchedResource>WEB-INF/web.xml</WatchedResource>

    <Environment name="LIBERATOR.DOMAIN" value="example.com"
        type="java.lang.String" override="false" />
    <Environment name="LIBERATOR.PRIMARY.ADDRESS" value="liberator1.example.com"
        type="java.lang.String" override="false" />
    <Environment name="LIBERATOR.PRIMARY.PORT" value="18080"
        type="java.lang.String" override="false" />
    <Environment name="LIBERATOR.PRIMARY.HTTPS.PORT" value="18081"
        type="java.lang.String" override="false" />
    <Environment name="LIBERATOR.SECONDARY.ADDRESS" value="liberator2.example.com"
        type="java.lang.String" override="false" />
    <Environment name="LIBERATOR.SECONDARY.PORT" value="18080"
        type="java.lang.String" override="false" />
    <Environment name="LIBERATOR.SECONDARY.HTTPS.PORT" value="18081"
        type="java.lang.String" override="false" />
    <Environment name="CAPLIN.DEV.MODE" value="false"
        type="java.lang.String" override="false" />

    <Environment name="caplin.keymaster.privatekey.filename"
        value="../../conf/keymaster/privatekey.pem"
        type="java.lang.String" override="true" />

</Context>

KeyMaster resources

Check that KeyMaster’s private key and key stores are in the correct location.

In Apache Tomcat, KeyMaster’s resource files are stored in the CATALINA_BASE/conf/keymaster/ directory.

user.properties file

If you are working in a development environment and need to configure user credentials manually, check the contents of the CATALINA_BASE/webapps/corporatetrader/WEB-INF/cfg/keymaster/users.properties file.

For details on the format of the file, see Setting user credentials during development.

Log files

Check the following log files for clues to the cause of the problem.

For information on interpretting Caplin log files, see How to manage and interpret log files (PDF).

To view a live log of StreamLink traffic between FX Corporate and Liberator, open a web browser and append ?debug=finer to the URL for your FX Corporate application.

For more details, see Capture StreamLinkJS logging data.

Liberator logs

Check Liberator’s log files in the <framework_root>/server/Liberator/var directory:

  • event-rttpd.log

  • http-access-rttpd.log

  • object-rttpd.log

  • request-rttpd.log

  • session-rttpd.log

  • packet-rttpd.log (binary format — see note below)

The DataSource packet log (packet-rttpd.log) is in binary format and requires Liberator’s logcat utility to view it. For more details, see Viewing packet logs with logcat.

Integration adapter logs

Check the log files for the integration adapters on the Caplin Platform that connect to your backend systems.

For example, if you use Caplin’s Wallstreet Adapter, check the log files in the <framework_root>/activate_blades/WallStreetAdapter/DataSource/var/ directory.

  • datasource.log

  • javaWallStreetAdapter.log

  • wallstreet-adapter.log

  • packet-datasource.log (binary format — see note below)

The DataSource packet log (packet-datasource.log) is in binary format and requires Liberator’s logcat utility to view it. For more details, see Viewing packet logs with logcat.

See also: