JRun SDK Guide Previous Up One Level Next
Windows JRun Installers


Customizing JRun installers with Windows Installer

The JRun SDK natively supports Windows Installer development environments by including the JRun core components as merge modules. This section describes these merge modules and how to work with them.

About merge modules

The JRun SDK includes a set of Windows Installer merge modules that represent core components of JRun. Merge modules are simplified .msi files, which is the file name extension for a Microsoft Windows Installer installation package. The modules contain dependent files that act as a functional group.

A standard Microsoft merge module has a .msm file name extension. A merge module cannot be installed alone because it lacks vital database tables that are present in an installation database.

Merge modules contain unique tables. To install the information delivered by a merge module with an application, you must merge the module into the application .msi file. Applications such as InstallShield Developer 7 and Wise Solutions 4 provide this merging functionality.

Working with merge modules

To work with and view the contents of a merge module or installer file, you can use a tool such as Orca from Microsoft, or a more robust installer tool, such as InstallShield Developer.

For more information on using Orca, see the following URL:

http://msdn.microsoft.com/library/en-us/msi/app_9303.asp

Working with the modules gives you flexibility in package creation and design. Your JRun application might require a minimal set of these JRun modules. You are not required to distribute unnecessary files, thus your final application media size reflects the true requirements of JRun.

The JRun merge modules are located in the sdk_root/installers/windows directory. For a description of the merge modules, see "Merge module list".

Note:   The Core merge module is required in all JRun installers.

Merge module list

The merge modules roughly correspond to the filesets in the sdk_root/filesets/all directory of the SDK. The following table describes the merge modules:
Merge module
File name
Description
Core
JRun4Core.msm
(Required) Includes the basic files to run JRun and serve J2EE applications. Also includes the migration tool, XMLScript, and the JSPC compiler.
Default JRun server
JRun4DefaultServer.msm
(Optional) Includes all files used by the default JRun server.
jikes
JRun4Jikes.msm
(Optional) Includes the JSP compiler. If your web application does not use JSPs or if you precompile your JSPs, the Jikes.msm module is not required.
JRun Management Console
JRun4JMC.msm
(Optional) Includes the JMC application's EAR file and the admin JRun server. The JMC provides access to JRun settings through a web-based GUI.
Web services
JRun4WebServices.msm
(Optional) Includes all files used to implement Web Services on JRun.
Documentation
JRun4Docs.msm
(Optional) Includes the PDF and HTML files for the basic documentation set.
JDBC drivers
JRun4JDBCDrivers.msm
(Optional) Includes the JRun JDBC drivers.
XDoclet
JRun4XDoclet.msm
(Optional) Includes the files for the JRun implementation of XDoclet.
Flash gateway
JRun4FlashGateway.msm
(Optional) Includes the Macromedia Flash Remoting service.
Web Server Configuration tool
JRun4Conn.msm
(Optional) Includes the tool to connect JRun to external web servers.

Previous Up 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/windowsinstall3.htm