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 include Liberator, Transformer, and C-based integration adapters.

Follow the steps below to configure the JVM in a C-based DataSource application:

  1. Set up the location and name of the JVM (Java Virtual Machine) by running the Deployment Framework command ./dfw java from the Deployment Framework’s topmost directory:

    For example:

    ./dfw java "C:/Program Files (x86)/Java/jre7/bin/client/jvm.dll"
    You only need to do this once, as the setting will apply to all instances of Liberator, Java and C-based Adapter blades running under that particular Deployment Framework.
  2. If you intend to run a 32 bit C-based Adapter blade that uses a JVM, you should specify the location of a suitable 32 bit JVM that it can use. In Linux environments that use Deployment Framework release 6.2 and later, you can define this location by running the Deployment Framework command ./dfw java32

    For example:

    ./dfw java32 /usr/local/java/jre/lib/i386/server/
  3. You may need to set up additional Java configuration (jvm-global-classpath, jvm-options, add-javaclass), putting it the appropriate configuration file:

Where do I put the configuration?

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

Adapter: Developing a C-based Adapter blade.

Blade’s DataSource/etc/java.conf

Adapter: Customising an existing C-based Adapter blade.

Deployment Framework’s


Liberator: Developing a Java-based Liberator Permissioning Service blade.

Blade’s Liberator/etc/java.conf

Liberator: Customising a Java-based Liberator Permissioning Service blade.

Deployment Framework’s


Transformer: Developing a Java-based Transformer Service blade.

Blade’s Transformer/etc/java.conf

Transformer: Customising an existing Java-based Transformer Service blade.

Deployment Framework’s


See also: