JRun SDK Guide Previous Up One Level Next
JRun Installer Overview


Building a customized version of JRun

The standard JRun installation gives you some control over which components you can include, however, the SDK includes filesets and the build.txt file so that you can have much finer-grained control over your own installation.

The following sections describe how to use the JRun filesets and build.xml file to customize your installation.

This section is intended for advanced JRun users who want more control over the JRun installation than the JRun installer provides. OEMs can use the techniques described in this section, but should use an installer development environment (such as InstallShield or InstallAnywhere) and the information in the following chapters to build their own customized installers for their customers.

Building JRun

Use the build.xml file in the sdk_root/filesets directory to customize your JRun installation with different combinations of modules, OS-specific files, and language-specific files.

Note:   You must have Ant installed.

To build a customized version of JRun:

  1. From the command line, change to the sdk_root/filesets directory.
  2. Type Ant at the command line.

    Ant builds the JRun installation.

  3. To test the JRun installation, execute the jrun command from the jrun_root/bin directory.

The filesets in the SDK provide you some control over individual JRun components. For an overview of the filesets, see "SDK file group".

Choose components

The default target of the build.xml file includes all available JRun components. Each component name corresponds to the fileset in the sdk_root/all directory. For a description of the components, see "JRun components".

The following lines show the default value of the build-all target: 

<project name="JRun OEM Kit" default="build-all" basedir=".">

...
<target name="build-all" depends="core,default-server,flashgateway,jmc, jrunwizard,macromedia_drivers,webservices,wsconfig,xdoclet" />

You can change the components that you install using the Ant command, as the following example shows: 

%> ant core default-server jmc

This example includes only the core, default-server, and jmc filesets.

Setting the language

The SDK includes the following directories for creating custom localized JRun installations:

These directories include localized versions of JRun files.

You can set the language using the Ant command. The following example shows an installer that uses the French-language fileset: 

%> ant -D oem.language=french

Valid values for the oem.language property are: english, french, and japanese. The default is english.

Note:   The property settings are not case-sensitive. Target names are case-sensitive.

Setting the platform

You can set the target platform for the JRun installation using the oem.os property. The default is intel-win, as the following example shows: 

%> ant -D oem.os=intel-win

The oem.os property corresponds to the name of the filesets directories, not including the localization directories. The possible values of the oem.os property are as follows:

For a description of these filesets, see "SDK file group".

Setting the destination directory

You can set the destination directory of the JRun installation using the oem.destination property in the build.xml file. The default is {basedir}/generated, as the following example shows: 

<property name="oem.destination" value="${basedir}/generated" />

You can change the base directory and the subdirectory defined by the oem.destination property. For example, if you want to set the destination directory to /opt/jrun4, replace the existing value with the following: 

<property name="oem.destination" value="/opt/jrun4" />

In Windows, the default installation directory for JRun is c:/jrun4. On UNIX, the default installation directory is /opt/jrun4.

Previous Up One Level Next

 

Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/jrun/4/JRun_SDK_Guide/installoverview4.htm