Macromedia - JRun LiveDocs : Using BIN files

The JRun SDK includes the JRun modules as binary (BIN) files. Based on your license agreement, you can access some or all of these modules. The BIN files are in the sdk_root/installers/unix directory.

You can use the BIN files to create a JRun installer with either a GUI installer tool, such as InstallAnywhere, or a shell script. You can import these BIN files into any compatible installer development environment. You can also execute BIN files on a UNIX command line or from within a shell script. In Windows, you can execute the BIN files with Cygwin.

The BIN files are equivalent to the Windows Installer merge modules described in the section "About merge modules".

If you do not use the BIN files, you can create a customized installer using the raw filesets in the sdk_root/filesets directory.

BIN file list

The following table describes the binary modules:


BIN file	File name	Description
Core	JRun4Core.bin	(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.bin	(Optional) Includes all files used by the default JRun server.
jikes	JRun4Jikes.bin	(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.bin	(Optional) Includes the JMC EAR file and the admin JRun server. The JMC provides access to JRun settings through a web-based GUI.
Web services	JRun4WebServices.bin	(Optional) Includes all files used to implement web services on JRun.
Documentation	JRun4Docs.bin	(Optional) Includes the PDF and HTML files for the basic documentation set.
JDBC drivers	JRun4JDBCDrivers.bin	(Optional) Includes the JRun JDBC drivers.
XDoclet	JRun4XDoclet.bin	(Optional) Includes the files for JRun's implementation of XDoclet.
Flash gateway	JRun4FlashGateway.bin	(Optional) Includes the Macromedia Flash Remoting service.
Web Server Configuration Tool	JRun4Conn.bin	(Optional) Includes the tool to connect JRun to external web servers.

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

BIN file properties

BIN installable modules require properties in a plain-text file called installer.properties. The installer.properties file must be in the same directory as the BIN file. In a development environment, such as InstallAnywhere, you can use the GUI to set the properties.

The following table describes the required properties:


Properties	Default value	Description
USER_INSTALL_DIR	/opt/JRun4	Directory in which JRun installs.
JAVA_HOME	none	Path to the Java runtime folder.
INSTALLER_UI	none	The silent mode of installation; set to SILENT.

The following is an example of an installer.properties file that silently installs JRun to the /opt/MyApp/appserver directory:

For more information on using BIN files and installer.properties, see the InstallAnywhere documentation that is available for download at http://www.installanywhere.com.

Comments

danger42 said on Jun 28, 2002 at 5:08 PM :

To get the platform-specific BIN files, you must download additional ZIP files. Go to http://www.macromedia.com/software/jrun/oem/ and click the "Download JRun SDK" link.

The following files contain the Unix InstallAnywhere BIN files you use to build custom JRun installations on Unix platforms:

jrun4-aix-sdk-bin-en.zip For AIX (ZIP, 52.7MB)
jrun4-hpux-sdk-bin-en.zip For HP-UX (ZIP, 52.3MB)
jrun4-linux-sdk-bin-en.zip For Linux (ZIP, 52.4MB)
jrun4-solaris-sdk-bin-en.zip For Solaris (ZIP, 52.3MB)
jrun4-tru64-sdk-bin-en.zip For Tru64 (ZIP, 42.7MB)

JRun SDK Guide
Platform-Independent JRun Installers