This document describes procedures for installing the Borland Enterprise Server using silent installation for Windows, Solaris and Linux.
Silent installation is recommended for use in medium to large scale deployments. It is used to set installation configurations, such as new license information, one time, using those configurations for installing on multiple machines. Once the configuration file is set up the silent installation runs without user interaction. The silent install process includes installation of the Java Development Kit (JDK).
Important: Using silent install implies your consent to the Borland Enterprise Server License Agreement.
Before using silent installation you should check disk space requirements, JDK requirements, and uninstall any previous versions of the full server. VisiBroker standalone versions do not require uninstalling.
The total amount of disk space required to install the Borland Enterprise Server depends on which components you install. For more information, see "Planning your network" in the Borland Enterprise Server Installation Guide and http://www.borland.com/techpubs/bes/platforms.
Note: Disk space includes JDK installation.
For Windows, Solaris and Linux platforms, two JDK versions are installed with the product. In Borland Enterprise Server version 5.2, they are JDK 1.3.1 and JDK 1.4.1. The JDK variable (JVM_JDK_HOME) used to set the JDK path, is used by Borland Enterprise Server components that host user application code, such as in new Partitions (including the Standard Partition), and the application client container, "VisiClient Container".
Borland Enterprise Server 5.2: For Windows, Solaris and Linux platforms, the optional variable (JVM_JDK_HOME), is used only to set the JDK path to a JDK other than the default version 1.4.
Using a JDK other than one included with the installer may have unpredictable results. We highly recommend you use a JDK included with the installer.
Important: The messaging core service product, SonicMQ, is bundled with the full Borland Enterprise Server installation. It installs automatically (requires no user intervention), and does not allow configuration. For more detailed information on the SonicMQ product, refer to the SonicMQ documentation included with the Borland Enterprise Server.
Note: It is not necessary to uninstall previous versions of VisiBroker standalone.
To uninstall the Borland Enterprise Server:
osagent, running during the uninstall.The Uninstall program does not remove any configuration or application files and folders that were created after the installation.
You cannot reinstall Borland Enterprise Server over a previous installation in the same BES installation directory, or file location. You must first uninstall any previous version before reinstalling. If you do not uninstall first, you must reinstall to another file location.
Before invoking the silent installation process, you must first create a text file that contains the properties for configuration settings, such as install directory, server name and serial number. See the Windows properties file or the Solaris/Linux properties file below.
After you've created the text properties file, save it as propertiesfile.txt for Windows or propertiesfile.fil for Solaris or Linux, where <propertiesfile> is the name of your file. Now you can invoke the silent installation process using the values specified in the properties file(s).
To invoke the silent installation process on Windows:
propertiesfile file:
installer.exe -f <path to properties file>where
installer is the name of the Borland Enterprise Server installer and <path to properties file> is the full path of the propertiesfile file.
For example:
BES52_Windows.exe -f c:\silentproperties.txt
propertiesfile file:
installer.exe -f <path to properties file>where
installer is the name of the Borland Enterprise Server installer and <path to properties file> is the full path of the propertiesfile file.
For example:
install_windows.exe -f c:\silentproperties.txt
To invoke the silent installation process on Solaris or Linux:
.bin file.propertiesfile file:
installer.bin -f <path to properties file>where
installer is the name of the Borland Enterprise Server installer and <path to properties file> is the full path of the propertiesfile file.
For example:
BES52_Solaris64/32.bin -f usr/home/myname/silentproperties.filor
BES52_Linux.bin -f /opt/myname/silentproperties.fil
propertiesfile file:
installer.bin -f <path to properties file>where
installer is the name of the Borland Enterprise Server installer and <path to properties file> is the full path of the propertiesfile file.
For example:
install_solaris.bin -f usr/home/myname/silentproperties.filor
install_linux.bin -f /opt/myname/silentproperties.fil
This Windows properties file applies to silent installation of Borland Enterprise Server and/or Borland VisiBroker Standalone. The property file is a plain text file.
Windows properties file for silent installation
| Variable | Value |
|---|---|
| INSTALLER_UI | silent (required). The mode of installation. |
| USER_INSTALL_DIR | <install_dir> (required). The full path name for the Borland Enterprise Server product directory of your choice. |
| USER_SHORTCUTS | ..\Start Menu\Programs\Borland Enterprise Server (required). The full path name for product shortcuts directory of your choice. |
| OSAGENT_PORT | (optional). Default is 14000. |
| SERVER_NAME | <server_name> (required). A server name of your choice. |
| JVM_JDK_HOME | <install_dir>\jdk\jdk1.4.1 (optional). Default is jdk\jdk1.4.1 See
discussion of JVM_JDK_HOME in Use
of JVM_JDK_HOME section. |
| BES_SERIAL | <serial_number> optional, required to install with a license. |
| BES_KEY | <key> optional, required to install with a license. |
| INSTALL_TYPE_1 | Borland Enterprise Sever (required). Installs full Borland Enterprise Server. Use TYPE_1 or TYPE_2, NOT BOTH. |
| INSTALL_TYPE_2 | Borland VisiBroker (optional). Installs Borland VisiBroker Standalone. Use TYPE_1 or TYPE_2, NOT BOTH. |
This Solaris/Linux properties file applies to silent installation of Borland Enterprise Server and or Borland VisiBroker Standalone. The property file is a plain text file.
Solaris/Linux properties file for silent installation
| Variable | Value |
|---|---|
| INSTALLER_UI | silent (required). The mode of installation. |
| USER_INSTALL_DIR | <install_dir> (required). The full path name for the Borland Enterprise Server. |
| USER_SHORTCUTS | /dev/null (required). Leave as is. |
| OSAGENT_PORT | (optional). Default is 14000. |
| SERVER_NAME | <server_name> (required). A server name of your choice. |
| JVM_JDK_HOME | <install_dir>\jdk\jdk1.4.1 (optional). Default is jdk\jdk1.4.1 See
discussion of JVM_JDK_HOME in Use
of JVM_JDK_HOME section. |
| BES_SERIAL | <serial_number> optional, required to install with a license. |
| BES_KEY | <key> optional, required to install with a license. |
| INSTALL_TYPE_1 | Borland Enterprise Sever (required). Installs full Borland Enterprise Server. Use TYPE_1 or TYPE_2, NOT BOTH. |
| INSTALL_TYPE_2 | Borland VisiBroker (optional). Installs Borland VisiBroker Standalone. Use TYPE_1 or TYPE_2, NOT BOTH. |
Note: Leave out BES_SERIAL and BES_KEY if you are installing without a license.
JVM_JDK_HOMEFor Windows, Solaris and Linux platforms, two JDK versions are installed with the product. In Borland Enterprise Server version 5.2, they are JDK 1.3.1 and JDK 1.4.1. The JDK variable (JVM_JDK_HOME) used to set the JDK path, is used by Borland Enterprise Server components that host user application code, such as in new Partitions (including the Standard Partition), and the application client container, "VisiClient Container".
Borland Enterprise Server 5.2: For Windows, Solaris and Linux platforms, the optional variable (JVM_JDK_HOME), is used only to set the JDK path to a JDK other than the default version 1.4.
Examples:
JVM_JDK_HOME can be set to the JDK 1.3.1 provided by the product.
JVM_JDK_HOME=<USER_INSTALL_DIR>\jdk\jdk1.3.1
JVM_JDK_HOME can be set to a JDK installed by the user (if it is a supported version)
JVM_JDK_HOME=<path to local JDK>
Using a JDK other than one included with the installer may have unpredictable results, we highly recommend you use the (default) JDK included with the installer.