Configure a DataSource application’s JVM

To configure the Java virtual machine (JVM) for a C-based DataSource application, or for a Java module within the application, use the appropriate dfw commands and then set up any additional configuration items as defined on the Java (JVM) configuration reference page.

Java-based DataSource applications

You don’t need to set up the location and name of the JVM (Java virtual machine) for DataSource applications that are entirely Java-based, because the Deployment Framework starts such applications by running a jar using the java command.

C-based DataSource applications

C-based DataSource applications use an embedded JVM and include Liberator, Transformer, and C-based integration adapters.

To configure the embedded JVM for C-based Datasource applications, follow the steps below:

  1. Ensure that the correct version of Oracle Java is installed and that the Caplin Deployment Framework can detect it. For more information, see Installing the Deployment Framework.

  2. Edit DataSource Java configuration in the appropriate file:

    What I’m developing/customising: Configuration goes in :

    Developing a C-based adapter blade

    Blade’s DataSource/etc/java.conf

    Customising an existing C-based adapter blade

    Deployment Framework’s global_config/overrides/<blade-name>/DataSource/java.conf

    Developing a Liberator Permissioning Service blade

    Blade’s Liberator/etc/java.conf

    Customising a Liberator Permissioning Service blade

    Deployment Framework’s global_config/overrides/<blade-name>/Liberator/etc/java.conf

    Developing a Transformer Service blade

    Blade’s Transformer/etc/java.conf

    Customising an existing Transformer Service blade

    Deployment Framework’s global_config/overrides/<blade-name>/Transformer/etc/java.conf

See also: