This section describes how to install Borland Enterprise Server (BES) and Borland Deployment Op-Center (BDOC) on Windows Itanium platform.
Important: For documentation updates, go to http://www.borland.com/techpubs/bes.
Notes:
For the latest platform information and system requirements go to
BES:
http://www.borland.com/techpubs/bes/platforms.BDOC:
http://www.borland.com/techpubs/opcenter/platforms.You can install BES/BDOC from the CD or download the software from the Borland web site http://www.borland.com/products/downloads/all_products.html.
Before you install BES/BDOC:
The installation package on CD includes a bundled version of the Java Development Kit (JDK). However, if you are downloading BES/BDOC from the web, you need an existing JRE 1.3, or above in your environment in order to run the installer.
Important: If you are downloading BES/BDOC from the web, you need a 64-bit version JRE 1.3 or above. An x86 version can not be used to run the installer.
Make sure to put the JDK bin directory into the path variable.
To check the location of your JDK and the version, use the following syntax:
prompt>java -version
Note: For updates on JDK requirements for Windows and for VisiBroker, please refer to the Borland web site, http://www.borland.com/techpubs/bes/platforms.
Important: No icons or shortcuts will be created in the Windows interface. All commands must be executed from the command-line.
To install BES/BDOC:
If you are installing from CD and autorun is enabled on your system, the installer automatically starts when you insert the CD into your CD-ROM drive and you will see a splash screen.
Follow the onscreen instructions. For most options, defaults offered by the installation wizard are acceptable. You can use the Previous button to return to earlier screens and change any information that is incorrect.
To install from web download:
.tar file and untar it:
BES_65_WIN_ITANIUM_Web.taror
OPCENTER_65_WIN_ITANIUM_Web.tar
<full_path_to_jdk>\java -cp <install_file>.jar installwhere
<install_file.jar> is either BES_65_WIN_ITANIUM.jar or OPCENTER_65_WIN_ITANIUM.jar.
Follow the onscreen instructions. For most options, defaults offered by the installation wizard are acceptable. You can use the Previous button to return to earlier screens and change any information that is incorrect.
Important: Once you select which product you are installing and click Next, to select a different product, you must cancel the current installation and restart the installation process.
BES AppServer Edition with Tibco. Installs the entire Borland Enterprise Server, which includes VisiBroker core functionality, plus support for integrated management of Java Messaging Services (JMS) through Tibco.
BES AppServer Edition with SonicMQ. Installs the entire Borland Enterprise Server, which includes VisiBroker core functionality, plus support for integrated management of JMS through SonicMQ.
BES AppServer Edition with OpenJMS. Installs the entire Borland Enterprise Server, which includes VisiBroker core functionality, plus support for integrated management of JMS through OpenJMS.
BES VisiBroker Edition. Installs the VisiBroker Java and C++ Core, development and management tools, and optional VisiBroker Extended Services.
Important: You cannot install this version of BES/BDOC on top of previous releases.
Borland Enterprise Server AppServer Edition
Management Console. GUI and tools for managing services and Partitions. For information about installing only the Management Console, go to Installing a standalone Borland Management Console.
Server. All server components, such as the Partition, Apache Web server, JDataStore, and VisiBroker.
Client. Components for client applications (EJB client and CORBA client).
Documentation. Suite of online documentation.
Examples. Example applications for Borland Enterprise Server.
Borland Enterprise Server VisiBroker Edition
VisiBroker Console. GUI and tools for managing VisiBroker ORB and services.
VisiBroker Core. VisiBroker for Java and C++ development tools and server components.
Documentation. Suite of online documentation.
Examples. Example applications for Borland Enterprise Server.
VisiBroker Extended Services. Optional components you purchase for extended VisiBroker functionality.
VisiBroker Op-Center Management Pack. Adds features for managing VisiBroker through Borland Deployment Op-Center.
VisiBroker Web Services Pack (VisiExchange). Web services support, Apache web server, Borland web container, IIOP connector, redirector, JDataStore, and support for JDBC datasources.
BDOC
Management Console. GUI and tools for managing BDOC Configurations. For information about installing only the Management Console, go to Installing a standalone Borland Management Console.
Documentation. Suite of online documentation.
Op-Center Server Components. All required BDOC server-side components including the Management Hub and Management Agent.
VisiNotify. An industrial strength, ORB-level implementation of the OMG Event/Notification Service.
VisiSecure. A framework for establishing secure connections between clients and servers.
VisiTime. A complete implementation of the OMG Time Service Specification, Version 1.1.
VisiTransact. A complete implementation of the OMG transaction management solution for transactions with CORBA applications over the Internet or intranets.
VisiTelcoLog. An OMG compliant implementation of the OMG Telecom Log Service specification version 1.1.2
In addition, the typical installation includes the following defaults:
osagent. This port is
used by the ORB to communicate with the server. You can use the Management
Console to change the Smart Agent port after installation is completed.
The default is 14000. 42424. osagent) port should have a unique name. The default is the
host name.
Note: The value(s) you enter for the port(s) must be valid for the installation to proceed.
bin directory to your PATH variable. The
typical installation does not add the BES/BDOC bin folder to your
PATH. To add it, choose the Custom install type.
Note: If you select the default, you may have to manually add certain components to your environment path.
BES_LIC_DIR
to <install_dir>\var and
BES_LIC_DEFAULT_DIR to
<install_dir>\license. bin directory in PATH. The default is "No". To
add the directory to your PATH, choose "Yes". BES_LIC_DIR to
<install_dir>\var and BES_LIC_DEFAULT_DIR
to <install_dir>\license. Important: (For BDOC installation) There should only be one Hub per Management Domain (port). For specific information on installing more than one Borland Enterprise Server on the same machine go to the Installing more than one BES instance section in the BES Installation Guide.
<install_dir>\license directory. If you did not receive a
license activation key file, or if you are reinstalling the software, go to
http://www.borland.com/products/downloads
and download a new license key. Important: You must register and activate your
license in order to use the product. If you have a valid, node-locked license
for BES/BDOC 6.0 on the same machine where you installed BES/BDOC 6.5, use the
lmadm command-line tool to migrate your 6.0 license for use with
the newly-installed BES/BDOC 6.5 software (see Migrating an existing 6.0 license).
Note: If you want to register and activate your
license later, either by running the lmadmw executable found in
the <install_dir>\bin directory or by launching the wizard
from the Tools menu in the Management Console (see Management Console User's Guide).
The installer generates an install log that is written to the root of the installation directory if you installed BES/BDOC from CD, or to the folder where the installer file resides if you used a downloaded file to install BES/BDOC.
The BES AppServer install log file is:
<install_dir>\BES_AppServer_Edition_InstallLog.xml
The BES VisiBroker install log file is:
<install_dir>\BES_VisiBroker_Edition_InstallLog.xml
The BDOC install log file is:
<install_dir>\Borland_Deployment_Op-Center_InstallLog.xml
The file is an XML formatted log with installation-specific information, such as errors.
The BES/BDOC CD contains a complete library of online documentation. To access the documentation on a machine where the product is installed, use one of the following methods:
help
To recognize the help command, your path system variable must
include the <install_dir>\bin directory, or you can enter
the path explicitly.
Note: Product documentation updates, HTML and PDF versions are available on the Web: http://www.borland.com/techpubs.
Borland Enterprise Server includes a graphical user interface, called the Management Console, which acts as the focal point for managing servers and applications on your network.
The server typically runs on a large shared UNIX or Windows machine, while the Management Console runs on any machine from which users want to view or modify the distributed system. Once the Management Console is installed, you can deploy to any server on your network.
To install a standalone Management Console:
If you install more than one instance of BES on the same machine:
Note: We recommend you use the Management Console to change port ID numbers.
To change Management port numbers:
To change Web container port IDs:
For information about updating the Borland web container
server.xml, go to the BES Developer's Guide.
The installer is capable of running in a text only mode. You can invoke the installer with a parameter which specifies the UI mode.
To run the installer in text-only mode:
<full_path_to_jdk>\java -cp <install_file>.jar install -i console
The installer will write to stdout and read from stdin.
This allows you to run the installer remotely.
Before running a VisiBroker for C++ server, VisiTransact, or VisiNotify, you
need to set two license environment variables (BES_LIC_DIR and
BES_LIC_DEFAULT_DIR). During installation, a batch script is
created for you to use for setting these environment variables.
To set the variables:
<install dir>\bin. vbroker.bat. Important: You cannot reinstall BES/BDOC over a previous installation in the same BES/BDOC 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 JDK home. Each property must be listed on its own line, terminated by a carriage return, with no blank spaces at the end of each line and no blank lines at the end of the file. See the Properties file for silent installation section for more information.
After creating the text properties file, save it as
<propertiesfile>.txt, where <propertiesfile> is
the filename prefix for your properties file. Now you can
invoke the silent installation process using the values specified in the properties
file(s).
Note: All properties and values are case-sensitive. When specifying directory and file paths, always use a forward slash.
The properties can appear in any order in the file.
Properties File Contents 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 BES/BDOC product directory of your choice. For HP-UX, the default installation directory is /opt/Borland/BDP. |
| OSAGENT_PORT | (optional). Default is 14000. |
| SERVER_NAME | <server_name> (optional). A server name of your choice. Default is host name. |
| MANAGEMENT_PORT | (optional). Sets the Management Port. Default is 42424. |
| USER_SHORTCUTS | The required value is /dev/null. |
| INSTALL_DOCS | (optional). Installs the suite of online documentation. Default is YES. |
| INSTALL_EXAMPLES | (optional). Installs the example applications for Borland Enterprise Server. Default is YES. |
| INSTALL_TYPE | BES: Choose only one of the following(required):
BDOC:
|
| JMS_TYPE | BES only. Choose only one of the following (required only if INSTALL_TYPE=AppServer):
|
| JVM_JDK_HOME | (optional). Sets the JDK path for BES components that host user application code. The default is set to the location where the JDK included with BES is installed. |
| INSTALL_CONSOLE | (optional, applies to AppServer Edition only). Installs the Management Console. Default is YES. |
| INSTALL_SERVER | (optional, applies to AppServer Edition only). Installs all the server components, such as the Partition, Apache Web server, JDataStore, and VisiBroker. Default is YES.
|
| INSTALL_CLIENT | (optional, applies to AppServer Edition only). Installs all the components for client applications (EJB client and CORBA client). Default is YES. |
| INSTALL_VBCONSOLE | (optional, applies to VisiBroker Edition only). Installs the GUI and tools for managing VisiBroker ORB and services. Default is YES. |
| INSTALL_VISICORE | (optional, applies to VisiBroker Edition only). Installs the VisiBroker for Java and C++ development tools and server components. Default is YES. |
| INSTALL_VISIMGT | (optional, applies to VisiBroker Edition only). Adds features for managing VisiBroker through Borland Deployment Op-Center. Default is YES. |
| INSTALL_VISIWEB | (optional, applies to VisiBroker Edition only). Installs web services support, Apache web server, Borland web container, IIOP connector, redirector, JDataStore, and support for JDBC datasources. Default is YES. |
| VISI_SERVICES | (optional, applies to VisiBroker Edition only). When INSTALL_TYPE is VisiBroker, installs any optional VisiBroker Extended Services you purchased. The value is a comma-delimited list that contains one or more of the following entries:
For example, if you purchased BES VisiBroker Edition with VisiNotify and VisiTransact, include the following line in your silent installation For a description of each optional Extended Service, see the Choose VisiBroker Extended Services section in BES Installation Guide. |
| CONFIGURATION_SETUP | (optional). Installs the BES example configuration. Default is YES. |
| BDOC_TYPE | BDOC only. Choose only one of the following (required):
|
| INSTALL_BDOC | BDOC only. (optional). All required Op-Center server-side components including the Management Hub and Management Agent. The default is YES. |
This example installs BES VisiBroker Edition on non-default management and agent ports, and installs several VisiBroker Extended Services.
INSTALLER_UI=silent USER_INSTALL_DIR=/opt/Borland/BDP USER_SHORTCUTS=/dev/null OSAGENT_PORT=14925 INSTALL_TYPE=VisiBroker VISI_SERVICES=VisiNotify,VisiSecure,VisiTime,VisiTransact,VisiTelcoLog MANAGEMENT_PORT=42925
This example installs a BDOC master Hub on a non-default management port and does not install the sample Configuration.
INSTALLER_UI=silent USER_INSTALL_DIR=/opt/Borland/BDOC INSTALL_TYPE=Op-Center BDOC_TYPE=master-hub USER_SHORTCUTS=/dev/null MANAGEMENT_PORT=42925 CONFIGURATION_SETUP=NO
To invoke the silent installation process on Windows:
<propertiesfile> file:
java -cp <installer_file> install -f <path to properties file>where
<installer_file> is the name of the BES/BDOC installer file and <path to properties file> is the full path of the <propertiesfile> file.
Note: After silent installation is completed, you need to register and activate the license you received for your product. For information on activating your new license, see the BES Installation Guide. If you want to register and activate your license by running the lmadmw executable found in the <install_dir>\bin directory or by launching the wizard from the Tools menu in the Management Console (see Management Console User's Guide).
Before using BES/BDOC, you need to register and activate the license you received for your product. The license may be in the form of an email from Borland listing one or more serial numbers and license keys, or it may be a license key file sent to you in an email from Borland. For information on how to license your product, go to http://info.borland.com/devsupport/bdpcommon/faq/6.5/licensing/index.html.
If you have a valid, node-locked license for BES/BDOC 6.0 installed on the same
machine as the newly-installed BES/BDOC 6.5, use the lmadm command-line
tool to migrate your 6.0 license for use with the newly-installed BES/BDOC 6.5
software.
If you have already received a key file in an email from Borland for a
product you purchased online or downloaded for evaluation, or if you downloaded
a free version of the product, you can use the registration wizard to apply the
key file, or you can copy it to the <install_dir>\license
directory and it will be applied automatically when you restart your product.
If you have a serial number and key, you can register and activate your BES/BDOC product using one of the following registration methods:
Depending on which method you choose, you may be asked to indicate whether you have a Borland Developer Network (BDN) account. If you do not have an account, you will be prompted to create one in the product registration wizard.
If you do not choose the Direct registration method, you will receive an
activation file. Simply copy this file into the
<install_dir>\license directory and it will be applied
automatically when you start your product.
To migrate an existing 6.0 node-locked license after installing 6.5:
lmadm command-line
license tool with the -i console option. Make sure to include the
full path to your installation's bin directory. For example: C:/BDP/bin/lmadm -i console
Note: This option overwrites any existing licenses found in the BES/BDOC 6.5 installation path you provided. If you have already applied licenses to your 6.5 installation, migrating a 6.0 license from the same machine will overwrite the licenses you applied. (When BES/BDOC 6.5 is installed, a placeholder, empty license is also installed. You can safely overwrite this license when migrating a 6.0 node-locked license.)
lmadm command-line tool, enter the Quit option. To use the Borland product registration wizard for Direct registration:
To use the Borland product registration wizard for Email registration:
<install_dir>\license
directory, and it will be applied automatically when you start your product.
To use the Borland product registration wizard for Web page registration:
<install_dir>\license
directory, and it will be applied automatically when you start your product.
To use the Borland product registration wizard for Telephone registration:
<install_dir>\license directory, and it will be applied
automatically when you start your product. To uninstall BES/BDOC:
osagent running during the uninstall.<install_root>/UninstallerData/. java -cp uninstaller.jar uninstall
Note: After uninstalling, there may still be files
and folders stored in the user's "Documents and Settings" (for example,
.bdp65) folder. You should delete these as well.