Installation Guide - Borland Technical Publications

Installation Guide
VERSION 5.2
Borland ®
Enterprise Server
Borland Software Corporation
100 Enterprise Way, Scotts Valley, CA 95066-3249
www.borland.com

Borland Software Corporation may have patents and/or pending patent applications covering subject matter in this
document. Please refer to the product CD or the About dialog box for the list of applicable patents.The furnishing of
this document does not give you any license to these patents.
COPYRIGHT © 1992–2003 Borland Software Corporation. All rights reserved. All Borland brand and product names
are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries.
All other marks are the property of their respective owners.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
BES0052WW21000
0102030405-9 8 7 6 5 4 3 2
PDF

Contents
Chapter 1
Introduction to Borland Enterprise
Server 1-1
Borland Enterprise Server Documentation . . . 1-1
Documentation conventions . . . . . . . . . . . 1-3
Platform conventions . . . . . . . . . . . . . 1-3
Contacting Borland support . . . . . . . . . . . 1-3
Online resources . . . . . . . . . . . . . . . . 1-4
World Wide Web . . . . . . . . . . . . . . . . 1-5
Borland newsgroups . . . . . . . . . . . . . . 1-5
Chapter 2
Planning your installation 2-1
Package contents . . . . . . . . . . . . . . . . . . 2-1
System requirements . . . . . . . . . . . . . . . 2-1
JDK. . . . . . . . . . . . . . . . . . . . . . . . 2-2
Web . . . . . . . . . . . . . . . . . . . . . . . 2-2
Disk space requirements . . . . . . . . . . . . . 2-3
Licensing . . . . . . . . . . . . . . . . . . . . . . 2-3
Planning your network . . . . . . . . . . . . . . 2-3
What's next? . . . . . . . . . . . . . . . . . . . . 2-5
Chapter 3
Installing on Windows NT or 2000 3-1
Preparing for installation . . . . . . . . . . . . . 3-1
JDK. . . . . . . . . . . . . . . . . . . . . . . . 3-1
Installing the Borland Enterprise Server . . . . 3-2
SonicMQ Messaging Service . . . . . . . . . 3-6
Installing a standalone Borland Enterprise Server
Management Console . . . . . . . . . . . . . . 3-6
Product documentation . . . . . . . . . . . . . . 3-7
Installing more than one server . . . . . . . . . 3-7
Install log . . . . . . . . . . . . . . . . . . . . . . 3-8
Uninstalling the Borland Enterprise Server . . . 3-8
Licensing and registering using the Borland
Management Console . . . . . . . . . . . . . . 3-9
Licensing the Borland Enterprise Server. . . 3-9
Registering the Borland Enterprise Server. .3-10
Chapter 4
Installing on UNIX/Linux 4-1
Installing on HP-UX or IBM AIX. . . . . . . . . 4-1
Preparing for installation . . . . . . . . . . . . . 4-1
JDK. . . . . . . . . . . . . . . . . . . . . . . . 4-2
Mounting a CD. . . . . . . . . . . . . . . . . . . 4-2
Starting the installation . . . . . . . . . . . . . 4-3
File ownership and the iaschangeowner script . 4-3
Changing ownership of a server instance . . 4-3
Installing the Borland Enterprise Server . . . . . 4-5
Licensing . . . . . . . . . . . . . . . . . . . . . 4-5
Installing a standalone Borland Enterprise Server
Management Console. . . . . . . . . . . . . . . 4-6
Product documentation . . . . . . . . . . . . . . 4-6
Installing more than one server . . . . . . . . . . 4-7
Setting environment variables for VisiBroker
(Edition and standalone) . . . . . . . . . . . . . 4-7
Changing environment variables in UNIX . . 4-8
Uninstalling the Borland Enterprise Server . . . 4-8
Running the installer without a GUI . . . . . . . 4-8
Installing on Linux . . . . . . . . . . . . . . . . . 4-9
KornShell. . . . . . . . . . . . . . . . . . . . . 4-9
Chapter 5
Installing BES Using Silent Installation
(Windows, Solaris, Linux) 5-1
What is silent installation? . . . . . . . . . . . . . 5-1
Preparing for installation. . . . . . . . . . . . . . 5-1
Disk space requirements . . . . . . . . . . . . 5-2
JDK . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Uninstalling previous versions of Borland
Enterprise Server . . . . . . . . . . . . . . . 5-2
Using silent installation . . . . . . . . . . . . . . 5-3
Invoking silent installation on Windows . . . 5-3
Invoking silent installation on Solaris
or Linux. . . . . . . . . . . . . . . . . . . . . 5-4
Windows properties file . . . . . . . . . . . . . . 5-5
Solaris/Linux properties file. . . . . . . . . . . . 5-5
Use of JVM_JDK_HOME . . . . . . . . . . . . . . 5-6
i

Chapter
1
Chapter1Introduction to Borland Enterprise
Server
The Borland Enterprise Server is a set of services and tools that enable you to build,
deploy, and manage enterprise applications in your corporate environment. These
applications provide dynamic content by using JSP, servlets, and Enterprise Java
Bean (EJB) technologies.
Borland Enterprise Server Documentation
Important
The Borland Enterprise Server documentation set includes the following:
• The Borland Enterprise Server Installation Guide
• The Borland Enterprise Server User’s Guide
• The Borland Enterprise Server Developer’s Guide
• The Borland Enterprise Server VisiBroker Developer’s Guide
• The Borland Enterprise Server VisiBroker VisiNotify Guide
• The Borland Enterprise Server VisiBroker Programmer’s Reference
• The Borland Enterprise Server VisiBroker GateKeeper Guide
• The Borland Enterprise Server Pet Store Tutorial
The documentation in PDF format and updates to the product documentation are
available on the web at http://www.borland.com/techpubs/bes.
Introduction to Borland Enterprise Server 1-1

Borland Enterprise Server Documentation
Note:
Windows
UNIX
Note:
To access the standalone online Help Topics on a machine where the product is
installed, use one of the following methods:
• Choose Start|Programs|Borland Enterprise Server|Help Topics
• Open a command shell and enter the command:
beshelp
To recognize the beshelp command, your path system variable must include the
/bin directory, or you can enter the path explicitly.
To access the online Help Topics and the Pet Store Tutorial on a machine where the
product is installed, use one of the following methods:
• From within the Management Console, choose|Help
• (Help Topics only) From within the DDEditor, choose|Help
• (Help Topics only) (VisiBroker standalone) From within the VisiBroker Console,
choose|Help
The Installation Guide describes how to install the Borland Enterprise Server on your
network. It is written for system administrators who are familiar with Windows NT,
2000, or UNIX operating systems.
The User's Guide provides information about using the Borland Enterprise Server.
This information includes how to use the graphical interface tools to start, stop, and
manage servers and services, how to use EJB and web containers, the wizards, the
Deployment Descriptor Editor, and the Application Assembly Tool. This guide also
describes the Dreamweaver UtraDev plug-in.
The Developer's Guide provides detailed information about packaging, deployment,
and management of distributed object-based applications in their operational
environment. Tuning services, establishing connections, and advanced approaches to
common problems are discussed. Additionally, this guide describes the VisiClient
Container.
The VisiBroker Developer's Guide describes how to develop VisiBroker applications in
Java or C++. It familiarizes you with configuration and management of the
Visibroker ORB using its consoles and properties file. Also described is the IDL
compiler, the Smart Agent, the Location, Naming and Event Services, the object
ActiActivationmon, the Quality of Service, and the Interface Repository.
The VisiBroker VisiNotify Guide describes Borland's implementation of the OMG
standard, Notification Service. This guide discusses how to use the major features of
the notification messaging framework, in particular, the Quality of Service (QoS)
properties, Filtering, and Publish/Subscribe Adapter (PSA).
The VisiBroker Programmer's Reference provides a description of the classes and
interfaces supplied with VisiBroker for Java and C++ in addition to information
about how to use the programming tools and command-line options.
The VisiBroker GateKeeper Guide describes how to use the VisiBroker GateKeeper to
enable VisiBroker clients to communicate with servers across networks, while still
conforming to the security restrictions imposed by web browsers and firewalls.
1-2 Installation Guide

Documentation conventions
The Borland Enterprise Pet Store Tutorial guides you through a basic tour of the BES
product with particular focus on clustering using the Borland Management Server (a
built-in management service).
Documentation conventions
The documentation for the Borland Enterprise Server uses the typefaces and symbols
described below to indicate special text:
Convention
Used for
italics
Information that the user or application
provides, such as variables in syntax diagrams.
It is also used for new terms and book titles.
computer
Sample command lines and code.
bold computer
In text, bold indicates information the user
types in. In code samples, bold highlights
important statements.
[ ] Optional items.
... Previous argument that can be repeated.
| Two mutually exclusive choices.
Keycaps
A key on your keyboard. For example, Press
Esc to exit.
Platform conventions
The Borland Enterprise Server documentation uses the following symbols to indicate
platform-specific information:
Windows: Windows NT and Windows 2000
WinNT: Windows NT only
Win2000: Windows 2000 only
UNIX: UNIX platforms
Solaris: Solaris only
Linux: Linux only
Contacting Borland support
Borland offers a variety of support options. These include free services on the
Internet where you can search our extensive information base and connect with other
users of Borland products. In addition, you can choose from several categories of
telephone support, ranging from support on installation of Borland products to feebased,
consultant-level support and detailed assistance.
Introduction to Borland Enterprise Server 1-3

Contacting Borland support
For more information about Borland's support services, please see our web site at:
http://www.borland.com/devsupport
and select your geographic region.
For Borland support worldwide information, visit:
http://www.borland.com/devsupport/contacts.
When contacting Borland's support, be prepared to provide the following
information:
• Name
• Company and site ID
• Phone number
• Your Access ID number (U.S.A. only
• Operating system and version (for example, Windows NT Server 4.0 with Service
Pack 5)
• Borland product name and version (for example, Borland Enterprise Server 5.2,
AppServer Edition)
• Any patches or service packs applied
• Client language and version (if applicable)
• Database and version (if applicable)
• Detailed description and history of the problem
• Any log files which indicate the problem
• Details of any error messages or exceptions raised
Online resources
You can get information from any of these online sources:
World Wide Web
Online Support
Listserv
http://www.borland.com
http://support.borland.com (access ID required)
To subscribe to electronic newsletters, use the online form
at:
http://www.borland.com/contact/listserv.html
or, for Borland's international listserver,
http://www.borland.com/contact/intlist.html
1-4 Installation Guide

Contacting Borland support
World Wide Web
Check http://www.borland.com regularly. The Borland Enterprise Server Product
Team posts white papers, competitive analyses, answers to FAQs, sample
applications, updated software, updated documentation, and information about new
and existing products.
You may want to check these URLs in particular:
• http://www.borland.com/products/downloads (updated software and other
files)
• http://www.borland.com/techpubs/bes (documentation)
• http://community.borland.com (contains our web-based news magazine for
developers)
Borland newsgroups
Note:
You can participate in many threaded discussion groups devoted to the Borland
Enterprise Server products.
You can find user-supported newsgroups for Enterprise Server and other Borland
products at:
http://www.borland.com/newsgroups.
These newsgroups are maintained by users and are not official Borland sites.
Introduction to Borland Enterprise Server 1-5

1-6 Installation Guide

Chapter
2
Chapter2Planning your installation
Important
This chapter describes installation requirements for the Borland Enterprise Server
and its components. It includes planning guidelines for installing components on
your network.
Go to http://www.borland.com/techpubs/bes for documentation updates and
more information on:
• installing Borland Enterprise Server on HP-UX or IBM AIX
• installing BES using silent installation (HP-UX or IBM AIX)
Package contents
Note:
The package contains the Borland Enterprise Server CD and product documentation.
Your package may include additional product CDs that ship with the Borland
Enterprise Server.
You can also download the Borland Enterprise Server software from the Borland web
site: http://www.borland.com/products/downloads.
This guide describes how to install the Borland Enterprise Server on Windows, UNIX
and Linux.
System requirements
Please refer to the Borland web site, http://www.borland.com/techpubs/bes/
platforms for the latest information on platforms supported by the Borland
Enterprise Server and for JDK requirements.
In addition to platform-specific requirements, the Borland Enterprise Server
components use TCP and UDP Broadcast services to communicate. Even if you are
Planning your installation 2-1

System requirements
running the components on a single machine you must have TCP and UDP services
available.
JDK
The installer installs JDK versions 1.4.1 and 1.3.1. The Borland Enterprise Server
infrastructure and tools use JDK 1.4. Third party components bundled with the
Borland Enterprise Server are certified to work JDK 1.3.
The Borland Enterprise Server installer allows you to specify which default JDK
version you want the Server to use after installation is complete. The default version
you specify is used for components that host user application code, for example, in
Partitions (including the Standard Partition), and the application client container,
"VisiClient Container". You can change the JDK version each Partition will run on
using the Borland Management Console. For more information, refer to the "Server’s
View" chapter in Borland Enterprise Server User's Guide.
Other JDKs
On the JDK installer panel you can select a default JDK other than one packaged with
the installer to host your application code. However, choosing another JDK may have
unpredictable results, so we highly recommended that you use the JDK packaged
with the installer.
JDKs for HP-UX and IBM AIX
The Borland Enterprise Server installation packages for HP-UX and IBM AIX do not
ship any version of the Java Development Kit (JDK). For information on Java
products for HP-UX go to http://www.hp.com/products1/unix/java/. For
information on Java products for IBM AIX go to http://www.ibm.com/
developerworks/tools.
Make sure you have the appropriate Java Development Kit (JDK) installed in your
environment before installing Borland Enterprise Server on HP-UX or IBM AIX. You
need the full JDK installed, not just the Java Runtime Environment (JRE).
VisiBroker
A standalone VisiBroker installation requires the appropriate JDK. Please refer to the
above platform page to see what is supported.
To ensure the necessary JDK is at the start of your PATH, type the following at a
command prompt:
java -version
Web
To use the Web engine and Web Administration Tool included with the Borland
Enterprise Server, you need one of the following web browsers:
2-2 Installation Guide

Disk space requirements
• Netscape Navigator, version 4.6 or later
• Microsoft Internet Explorer, version 5.0 or later
Disk space requirements
Important
The following are the general disk space requirements.
The disk space requirements can be affected by:
• operating system
• JDK version
Disk space requirements
Component
Borland Enterprise Server (full installation)
Borland VisiBroker (standalone)
Space
626 MB (plus 329 MB in your temporary
directory)
321 MB (plus 329 MB in your temporary
directory)
Note:
The messaging shared service product, SonicMQ, is bundled with the Borland
Enterprise Server installation. SonicMQ automatically installs, requires no user
intervention, and does not allow configuration. For more detailed information on the
SonicMQ product, refer to the SonicMQ documentation located in \
SonicMQ\sonicmq_docs\.
Licensing
Before you install the Borland Enterprise Server, make sure you have the serial
numbers and/or license keys to run the Borland Enterprise Server edition that you
purchased and its related components. If you have not received a license for the
Borland Enterprise Server, contact your Borland sales representative. For more
information about licensing and registration go to Chapter 3, “Installing on Windows
NT or 2000”.
Planning your network
The following table shows the number of components required for each edition. Use
this information to plan which components to install on each computer. In this table,
the term network indicates a collection of components that are set up to communicate
across the same Smart Agent port.
Planning your installation 2-3

Planning your network
Network requirements
Components
Borland Enterprise Server AppServer Edition
Borland Enterprise Server VisiBroker Edition
Borland Enterprise Server Web Edition
Borland Enterprise Server Management
Console
Borland Management Hub
Borland VisiBroker (standalone)
Requirements
1 copy per development or deployment system.
Includes the VisiBroker and Web Editions.
1 copy per development or deployment system.
Includes the Web Edition.
1 copy per development or deployment system.
At least 1 copy per network, multiple copies as
needed.
At least 1 copy per network, multiple copies as
needed.
1 copy per development or deployment system.
Note:
You can also configure the Borland Enterprise Server to run on a single, stand-alone
computer with TCP and UDP networking capabilities.
When planning the installation, remember the following:
• The AppServer Edition includes both the VisiBroker and Web Editions. If you
have an older version of the VisiBroker Edition on your computer, Borland
recommends you remove it before installing the new Edition.
• You can install the Borland Enterprise Server Management Console or Borland
Management Server Hub separately. Typically, you install either the AppServer,
VisiBroker or Web Edition on a large shared UNIX or NT machine. You can install
the Management Console on any machine you use to view, modify or manage
your distributed applications.
• Installing the product documentation (online Help Topics and Examples) is
optional. Borland recommends you install the "docs".
Information requested includes:
Serial number and license key: You should have a serial number and/or license key
for the Borland Enterprise Server Editions and related products.
Installation directory: This is the directory you specify to install the server. If you are
installing the Borland Enterprise Server and the Management Console on the same
computer, we recommend you use the same installation directory.
JDK: You must specify a JDK version, 1.4.1. or 1.3.1 to host user application code.
Remember, it is highly recommended that you use the JDK included with the
installer.
Smart Agent Port: This is the network-wide UDP Broadcast port used by
the Borland Enterprise Server to communicate with the Smart Agent. By default, the
port number is 14000, but you can specify any vacant port number in the range of
5000 to 65535. All components that communicate with one another must have the
same port number.
Server name: This is a user-defined name that uniquely identifies an instance of the
Borland Enterprise Server. By default, this is the name of the computer where you
2-4 Installation Guide

What's next?
What's next?
install the Borland Enterprise Server. Every Borland Enterprise Server using the same
Smart Agent port should have a unique name.
Once you've gathered license information and planned your network installations,
you are ready to install the Borland Enterprise Server. If you are installing on
Windows, see Chapter 3, “Installing on Windows NT or 2000”. If you're installing on
UNIX, see Chapter 4, “Installing on UNIX/Linux”.
Planning your installation 2-5

2-6 Installation Guide

Chapter
3
Chapter3Installing on Windows NT or 2000
Important
This chapter describes how to install the Borland Enterprise Server and related
components on Windows NT or 2000. If you are installing on UNIX or Linux, see
Chapter 4, “Installing on UNIX/Linux”.
For documentation updates, go to http://www.borland.com/techpubs/bes.
Preparing for installation
You can install the Borland Enterprise Server from the CD or download the software
from the Borland web site http://www.borland.com/products/downloads.
Before you install the Borland Enterprise Server:
1 Exit all applications.
2 Select an installation method:
• If you want to download a version of the product from the Borland web site go
to http://www.borland.com/products/downloads.
• If you are installing from CD, mount the Borland Enterprise Server CD.
JDK
The installer installs JDK versions 1.4.1 and 1.3.1. The Borland Enterprise Server
infrastructure and tools use JDK 1.4. Third party components bundled with the
Borland Enterprise Server are certified to work JDK 1.3.
The Borland Enterprise Server installer allows you to specify which default JDK
version you want the Server to use after installation is complete. The default version
you specify is used for components that host user application code, for example, in
Partitions (including the Standard Partition), and the application client container,
"VisiClient Container". You can change the JDK version each Partition will run on
Installing on Windows NT or 2000 3-1

Installing the Borland Enterprise Server
using the Borland Management Console. For more information, refer to the "Server’s
View" chapter in Borland Enterprise Server User's Guide.
Other JDKs
On the JDK installer panel you can select a default JDK other than one packaged with
the installer to host your application code. However, choosing another JDK may have
unpredictable results, so we highly recommended that you use the JDK packaged
with the installer.
Note:
JDKs for HP-UX and IBM AIX
The Borland Enterprise Server installation packages for HP-UX and IBM AIX do not
ship any version of the Java Development Kit (JDK). For information on Java
products for HP-UX go to http://www.hp.com/products1/unix/java/. For
information on Java products for IBM AIX go to http://www.ibm.com/
developerworks/tools.
Make sure you have the appropriate Java Development Kit (JDK) installed in your
environment before installing Borland Enterprise Server on HP-UX or IBM AIX. You
need the full JDK installed, not just the Java Runtime Environment (JRE).
We recommend uninstalling any previous versions or evaluation versions of the
Borland Enterprise Server, or install the new version to a different location, on a
different install path. For more information on installing multiple servers, see
“Installing more than one server” on page 3-7.
Installing the Borland Enterprise Server
To install the Borland Enterprise Server and related components:
1 If installing from CD, browse to your CD drive.
2 Within the CD, double-click the install_windows.exe icon to start the installation.
3 Select Install Borland Enterprise Server.
4 Follow the on screen 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.
Changing JDKs after installation
Once the Borland Enterprise Server is installed, you can use the Borland
Management Console to change and configure a Partition's JDK. Refer to
"Configuring a partition" in the Borland Enterprise Server User's Guide, and the
context help included within the Partition configuration panel.
VisiClient Container: To change the JDK for the VisiClient Container (application
client container), you must edit the appclient.config file manually. This file can
be found in /bin/appclient.config.
3-2 Installation Guide

Installing the Borland Enterprise Server
Note:
Note:
Note:
Edit the following text string: javahome $var(installRoot)/jdk/jdk1.4.1.
For more information on the VisiClient Container refer to "The VisiClient
Container" in the Borland Enterprise Server Developer's Guide.
For updates on JDK requirements for Windows, Unix/Linux, and for VisiBroker,
please refer to the Borland web site, http://www.borland.com/techpubs/bes/
platforms.
1 On the license agreement screen, specify the following:
• License Agreement information. Installation and use of the Borland Enterprise
Server requires acceptance of the license agreement.
• License information. This information includes a serial number and a license
key. The license information indicates which Edition(s) you have purchased,
and which features will be available to you.
If you do not provide license information here, you are able to complete the
installation. However, you are required to enter license information later using
the Management Console. For more information, refer to “Licensing and
registering using the Borland Management Console” on page 3-9.
If you are installing a Client only or the VisiBroker standalone version, you
must provide license information at this time.
2 When the Choose Product Components screen appears, select one of the
following:
• Borland Enterprise Server (complete). Installs the entire Borland Enterprise
Server, which includes the AppServer Edition, the VisiBroker Edition and Web
Edition.
• Borland VisiBroker (standalone). Installs VisiBroker for C++ and Java ONLY.
The VisiBroker standalone option is not the VisiBroker Edition. The VisiBroker
standalone installation does not include the Web Edition; the VisiBroker
Edition installation does.
Choose product installation
Installing on Windows NT or 2000 3-3

Installing the Borland Enterprise Server
Note:
The Borland Enterprise Server and standalone VisiBroker installations allow you
to install different features in different places. You can also select a "custom"
installation, which is a variation of features.
3 Depending on which Borland Enterprise Server product you choose, select from
the following product components for each feature set (next screen):
Borland Enterprise Server
• Management Console. The 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. This option allows you to
install the Console separately from the Borland Enterprise Server.
• Server. This includes all Borland Enterprise Server components such as Apache
Web server, JDataStore, and such.
• Client. This is a client container that hosts client applications such as J2EE and
CORBA clients.
• Docs This option installs the online Help Topics, Pet Store Tutorial, and
Examples for the Borland Enterprise Server.
• Management Hub. This includes all of the Borland Management Server
components, such as the management repository, the management server
client, and such.
In a typical install, only one Management Hub should be installed per
management domain.
• Custom. This option is a variation on any of the above component selections.
Borland VisiBroker (standalone)
• VisiBroker Console. This installs just the VisiBroker Console, which is a GUI
and tools for managing the VisiBroker ORB and services.
• VisiBroker ORB. This installs VisiBroker for C++ and Java only.
• Docs. This option installs the online Help Topics, Pet Store Tutorial, and
Examples for the Borland Enterprise Server.
• Custom. This option is a variation on any of the above component selections.
3-4 Installation Guide

Installing the Borland Enterprise Server
Choosing product components
Note:
Important
4 Specify installation settings for the following:
• Smart Agent port (osagent). This specifies the Smart Agent port (OSAGENT_PORT
environment variable) used by the server. This is a number between 5,000 and
65,535.
Ports in the Borland Enterprise Server are:
• The Smart Agent port is also known as the osagent. This port is used by the
ORB to communicate with the server. The Smart Agent must be specified at
installation time. You can change the Smart Agent port at any time using the
Console.
• The Management port is the port the Borland Enterprise Server listens to for
management functionality in the Console. This may also be referred to as the
"user port". This port can only be specified and changed after installation.
The Management port is set using the Borland Enterprise Server Management
Console. If you change the Management port (user port) of a server that is part
of a cluster, in order to maintain the cluster's operation, you must also make the
same change to the Management port for all other servers in that cluster. Note
that the Management port can only be changed locally, on the machine on
which the server is installed.
• Server name. Every server using the same Smart Agent (osagent)port should
have a unique name.
5 Location for the product icons. You can choose between a number of options for
product icon placement. If you choose "In an existing Program Group", a dropdown
menu activates in your Start menu.
6 Select a Java Deveopment Kit. Remember, it is highly recommended that you use
a JDK packaged with the installer.
Installing on Windows NT or 2000 3-5

Installing a standalone Borland Enterprise Server Management Console
Note:
7 When the pre-installation summary screen appears, check that component and
configuration information is correct, and that your Disk Space Available exceeds
the Disk Space Required. To start the installation, click Install.
8 After the installation completes you have the option to modify your system
environment by including the /bin directory to your environment path. The
default is set to "No".
You may have to manually add certain components, such as a JDK, to your
environment path if you select the default.
SonicMQ Messaging Service
The SonicMQ Message Broker (a full implementation of the Java Messaging Service
(JMS)) is automatically installed with the Borland Enterprise Server. For information
about SonicMQ, please refer to their documentation, which can be found in
\SonicMQ\sonicmq_docs\.
Installing a standalone Borland Enterprise Server Management
Console
The 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 NT machine, while the
Management Console runs on any machine from which you want to view or modify
the distributed system. Once the Management Console is installed, you can deploy to
any server on your network.
1 When the Smart Agent screen appears, specify the same Smart Agent port as those
specified for the server(s) you want the Management Console to support.
2 After installation, if you want to change the Smart Agent port, right-click on the
server in the Navigation Pane and select "Configure". You can change the value in
the Smart Agent port field. The Smart Agent address specifies the IP address or
the host name of the machine running the Smart Agent. The default value is null
which tells the application to use the value from the OSAGENT_ADDR environment
variable. If the OSAGENT_ADDR variable is not set, Borland Enterprise Server expects
that the Smart Agent is running on a local host.
3-6 Installation Guide

Product documentation
Changing the Smart Agent port
3 Complete the installation as described in the previous section,“Installing the
Borland Enterprise Server” on page 3-2.
Product documentation
Note:
The Borland Enterprise Server 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:
• Choose Start|Programs|Borland Enterprise Server|Help Topics
• From within the Management Console, choose|Help
• From within the DDEditor, choose|Help
• (VisiBroker standalone) From within the VisiBroker Console, choose|Help menu
The product documentation in PDF format and updates to the documentation are
available on the Web at: http://www.borland.com/techpubs/bes.
Installing more than one server
Note:
If you install more than one Borland Enterprise Server on the same computer, they
must have completely different install paths; the install directories at the top level
must be different. Also, you must modify the server.xml file for the standard
Partition to make sure container services included with each server have unique port
ID numbers. Keep the defaults on one server, but change the defaults for all other
servers so that they have unique port ID numbers.
We recommend you use the Management Console's Partition Services properties
panel to change port ID numbers. For the web container (Tomcat 4.1), change the
XML directly in /var/servers/server_name/adm/properties/
partitions/standard/tomcat/conf/.
Installing on Windows NT or 2000 3-7

Install log
To change Web container port IDs:
1 Open the Borland Enterprise Server Management Console.
2 In the navigation tree, expand Partition Services.
3 Right-click the Web Container node and select Configure.
The General tab displays the server.xml file. To edit port ID properties, use the
Connectors tab.
4 Go to the Connectors tab and set a different port number in the Port field.
Changing the port ID
Install log
The installer generates an install log that installs to the root of the installation
directory. The file is:
/Borland_Enterprise_Server_InstallLog.xml
The file is an XML formatted log with installation specific information, such as errors.
Uninstalling the Borland Enterprise Server
Note:
To uninstall the Borland Enterprise Server:
1 Make sure there are no background processes like osagent running during the
uninstall.
2 Open the installation directory.
3 Double-click the Uninstall icon.
4 Click Uninstall to completely remove all components that were installed.
This does not remove files and folders that were created after the installation.
3-8 Installation Guide

Licensing and registering using the Borland Management Console
Note:
5 After you run the uninstall program, check the installation directory and remove
any unnecessary files and sub directories.
After uninstalling, there may still be files stored in a temp directory, such as the
one under the Windows "Profiles" folder. You should delete these as well.
Licensing and registering using the Borland Management Console
This section describes how to license and register the Borland Enterprise Server using
the Management Console.
Licensing the Borland Enterprise Server
Note:
Note:
You can license the Borland Enterprise Server during installation. If you do not enter
license information during installation, you are required to enter it using the
Management Console.
To enter license information using the Management Console:
1 The Management Console executable file is: consolew.exe. To start the Console,
use one of the following methods:
• Windows: On your desktop, double-click the Borland Enterprise Server
Console icon, or choose Start|Programs|Borland Enterprise Server|
Management Console.
• UNIX: Open a command shell and enter the following command:
console
To recognize the console command, your path system variable must include
the /bin directory, or you can enter the path explicitly.
The Borland Management Console login screen appears.
2 To use the Borland default login settings, enter the password: admin
3 Click Login.
The Borland Management Console appears.
4 In the navigation pane of the Management Console, expand Enterprise Servers.
5 Right-click the server that you want to license and select Update License.
6 Enter your serial number and key.
Registering the Borland Enterprise Server
The product registration wizard allows you to register electronically or by telephone.
If you have an Internet connection, we recommend electronic registration. You must
register the Borland Enterprise Server to comply with the license agreement.
Installing on Windows NT or 2000 3-9

Licensing and registering using the Borland Management Console
Note:
Register by phone
1 To register your server by phone, in the navigation pane right-click the server that
you want to register and select Register Server.
2 Select the "I do not have an Internet connection" radio button.
3 Select your geographic location from the "Telephone Number" drop-down menu.
4 Call the telephone number shown for your geographic location to speak to a
Borland representative. Leave the screen up while you talk to the Borland
representative.
If your serial number and authorization key are not already showing on the
screen, you must go back and update your Borland Enterprise Server license
information using the Management Console.
5 Enter the Activation Key the Borland representative gives you in the Activation
Key field.
6 Complete your registration by following the Registration wizard's instructions.
Register online
If you are a Borland Community Member and/or have a Software Registration
Account from a previous electronic product registration, you can take advantage of
the "Quick Registration" option.
If you are not a Member and do not have an Account, you must create a new
Software Registration Account in order to register your server. You can use your new
Software Registration Account to quickly register other Borland products.
Note:
Note:
Quick Registration
To take advantage of Quick Registration, you must provide your Borland
Community Member user name (or email address) along with your Community
password. If you are not a Member, you can alternatively use your Software
Registration Account user name and password.
To use Quick Registration:
1 In the navigation pane, right-click the server that you want to register and select
Register Server.
2 Select either the "I am a Borland Community Member" or "I am not a Member, but
I have a Software Registration Account" radio button. Click Next.
To become a Borland Community Member (Borland Developer Network) go to
http://community.borland.com.
3 Enter your Borland Community Member user name (or email address) along with
your Community password. Alternatively, you can use your Software
Registration Account user name and password. Click Next.
If you forget your Community Member password, you can obtain it from the
Community web site at http://community.borland.com.
3-10 Installation Guide

Licensing and registering using the Borland Management Console
4 If you use a proxy to connect to the Internet, enter the host and port. If your proxy
requires authentication, enter the user name and password. Click next.
Your registration is now processing. If there is an error, such as an invalid user
name or password, click the Back button to change information or click Next for
other registration options.
Installing on Windows NT or 2000 3-11

3-12 Installation Guide

Chapter
4
Chapter4Installing on UNIX/Linux
Linux:
This chapter describes how to install the Borland Enterprise Server and related
components on UNIX (the Solaris operating system) and Linux. If you are installing
on Windows NT or 2000, see Chapter 3, “Installing on Windows NT or 2000”.
For Linux specific issues, see “Installing on Linux” on page 4-9 at the end of this
chapter.
Installing on HP-UX or IBM AIX
For documentation updates and specific instructions on installing Borland Enterprise
Server on HP-UX or IBM AIX, go to www.borland.com/techpubs/bes.
Preparing for installation
You can install the Borland Enterprise Server from the CD or download the software
from the Borland web site http://www.borland.com/products/downloads.
Before you install the Borland Enterprise Server:
1 Select the installation method:
• If you want to download a version of the product from the Borland web site, go
to http://www.borland.com/products/downloads.
• If you are installing from CD, mount the Borland Enterprise Server CD.
Installing on UNIX/Linux 4-1

Mounting a CD
JDK
The installer installs JDK versions 1.4.1 and 1.3.1. The Borland Enterprise Server
infrastructure and tools use JDK 1.4. Third party components bundled with the
Borland Enterprise Server are certified to work JDK 1.3.
The Borland Enterprise Server installer allows you to specify which default JDK
version you want the Server to use after installation is complete. The default version
you specify is used for components that host user application code, for example, in
Partitions (including the Standard Partition), and the application client container,
"VisiClient Container". You can change the JDK version each Partition will run on
using the Borland Management Console. For more information, refer to the "Server’s
View" chapter in Borland Enterprise Server User's Guide.
Other JDKs
On the JDK installer panel you can select a default JDK other than one packaged with
the installer to host your application code. However, choosing another JDK may have
unpredictable results, so we highly recommended that you use the JDK packaged
with the installer.
JDKs for HP-UX and IBM AIX
The Borland Enterprise Server installation packages for HP-UX and IBM AIX do not
ship any version of the Java Development Kit (JDK). For information on Java
products for HP-UX go to http://www.hp.com/products1/unix/java/. For
information on Java products for IBM AIX go to http://www.ibm.com/
developerworks/tools.
Make sure you have the appropriate Java Development Kit (JDK) installed in your
environment before installing Borland Enterprise Server on HP-UX or IBM AIX. You
need the full JDK installed, not just the Java Runtime Environment (JRE).
Mounting a CD
Note:
The Borland Enterprise Server CD includes installation software for the Solaris
operating system. To use the commands provided in the following sections, open a
command shell.
To mount a CD on your local workstation:
1 Log in to your workstation.
If the Volume Manager is not running, you need superuser privileges to mount the
CD in step 5.
2 Insert the CD into the drive.
3 To determine if the Volume Manager is running, enter the following command:
/usr/bin/ps -ef | grep vold
4-2 Installation Guide

File ownership and the iaschangeowner script
To see a list of all running processes, look for a response similar to the following:
root 247 1 0 Oct 30? 0:00 /usr/sbin/vold
4 If the volume manager is running, proceed to Step 6.
5 If the volume manager is not running, enter the following commands to mount the
CD:
mkdir /cdrom/name
/usr/sbin/mount -f hsfs -r /dev/dsk/device /cdrom/name
where device is the device name of the CD.
6 Enter the following command to change to the CD directory:
cd /cdrom/name
Starting the installation
1 To start the installation type the following command:
install_solaris
The installation screen appears after a few moments.
2 Select Install Borland Enterprise Server.
File ownership and the iaschangeowner script
Some files and directories, such as log files, properties, and realms are not created
when the Borland Enterprise Server is installed. Instead, they are created by the
server at runtime the first time the server is started. Permissions on these files and
directories are granted based on the user running the server at this initial time. For
example, if you run the server for the first time as usernameA, some files or directories
will be owned by usernameA. Any subsequent running of the server by any other user
(including root) will result in error due to permission problems. File ownership must
be changed in order to allow any other users to write to these files.
Changing ownership of a server instance
To change ownership use the iaschangeowner script (UNIX only) in the /bin
directory of the installed Borland Enterprise Server. The script changes the
ownership of files such as logs and properties to allow writing by another owner.
The following directories (and their contents) are affected by the iaschangeowner
script:
• /var/defaults
• /var/bms
• /var/servers/
Installing on UNIX/Linux 4-3

File ownership and the iaschangeowner script
• /SonicMQ
Note:
Usage
This version of Borland Enterprise Server includes two iaschangeowner options, the
and .
When a Borland Enterprise Server installation has multiple server instances defined,
the ownership of each instance can be set to different, or the same users.
Usage: iaschangeowner -r [-s | -d] -o
-g [-a]
When a Borland Enterprise Server installation has multiple server instances defined,
the ownership of each instance can be set to different, or identical users.
• -r : The root directory of the Borland Enterprise Server installation.
• -d defaults (templates): Change the ownership of future servers. -d and -s cannot
be specified at the same time.
• -s : The name of the server instance to change ownership of. This is
not required if the server only contains one server instance. -d and -s cannot be
specified at the same time.
• -o : The user id of the new owner, for example, nobody, root, and
such.
• -g : The group id of the new group.
• -a: If owner is root, set Apache to run as root. Otherwise, set Apache to run as the
user who starts it (or the Borland Enterprise Server).
Rules
The following rules apply:
• If neither -s or -d are specified, and only one server was created, ownership of that
server will be changed. An error will be generated if more than one server exists.
• If -s is specified, only that server's files will be changed. -d cannot
be specified at the same time.
• If -d is specified, all the files in /var/default will be updated and therefore any
new server will be owned by the new user. -s cannot be specified at this time.
• BMS and SonicMQ directories will always be changed to the new owner.
Usage example
The following is a short example using the iaschangeowner script to change the user
name and group for any servers started from the /usr/BES installation:
% iaschangeowner -r /usr/BES -d -o jsmith -g admin
Failure to change permissions prior to changing server owners will result in errors
similar to the following:
4-4 Installation Guide

in/ias: server_root/sk.txt: cannot create
Installing the Borland Enterprise Server
Installing the Borland Enterprise Server
Note:
Note:
Important
To install the Borland Enterprise Server and related components:
1 To start the installation, on the Introduction screen click Next.
2 Follow the on screen instructions. For most options, defaults offered by the
installation wizard are acceptable.
You can use the Back button to return to an earlier screen and change any
information that is incorrect.
During installation, the installer checks to make sure you have the correct version
of JDK installed on your computer.
Changing JDKs after installation
Once the Borland Enterprise Server is installed, you can use the Borland
Management Console to change and configure a Partition's JDK. Refer to
"Configuring a Partition" in the Borland Enterprise Server User's Guide, and the
context help included within the Partition configuration panel.
VisiClient Container: To change the JDK for the VisiClient Container (application
client container), you must edit the appclient.config file manually. This file can
be found in /bin/appclient.config. Edit the following text string:
javahome $var(installRoot)/jdk/jdk1.4.1. For more information on the
VisiClient Container refer to "The VisiClient Container" chapter in the Borland
Enterprise Server Developer's Guide.
For updates on JDK requirements for Windows, UNIX, and for VisiBroker, refer to
the Borland web site, http://www.borland.com/techpubs/bes/platforms.
For more information and graphical representations, see Chapter 3, “Installing on
Windows NT or 2000”.
Licensing
Important
1 If you do not provide license information during this installation you are able to
complete the installation. However, you are required to enter the license
information later using the Management Console.
2 If you are installing a Client or the VisiBroker standalone version, you must
provide your license information at this time.
A fully licensed installation on UNIX may omit the following licensing error
message when using tools like idl2cpp or VBJ:
"There is no valid license to run this product or component. Please make sure that
a license enabling this product or component is installed correctly and it has not
expired."
Installing on UNIX/Linux 4-5

Installing a standalone Borland Enterprise Server Management Console
These tools require access to appropriate environment variables. Prior to running
these tools, use the vbroker.csh or vbroker.sh scripts in the installation /bin
directory to set up the appropriate environment variables. Building the examples
requires invoking a number of these tools. If you want to compile the examples on
UNIX or Linux, you must invoke the setup scripts first. This behavior is as
designed.
For more information on licensing and registration of the Borland Enterprise
Server, refer toChapter 3, “Installing on Windows NT or 2000”.
Installing a standalone Borland Enterprise Server Management
Console
The 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 NT 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 the Console on a separate machine:
1 Follow the installation procedure described in "Installing the Borland Enterprise
Server on Windows NT or 2000" in the previous section.
2 When the Choose Product Components screen appears, select only the
Management Console.
3 When the Smart Agent screen appears, specify the same Smart Agent port as those
specified for the server(s) you want the Management Console to support.
Product documentation
The Borland Enterprise Server 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:
• Open a command shell and type the command:
beshelp
To recognize the beshelp command, your path system variable must include the
/bin directory, or you can enter the path explicitly.
• From within the Management Console, choose|Help
• From within the DDEditor, choose|Help
• (VisiBroker standalone) From within the VisiBroker Console, choose|Help menu
4-6 Installation Guide

Installing more than one server
Note:
The product documentation in PDF format and updates to the documentation are
available on the Web at: http://www.borland.com/techpubs/bes.
Installing more than one server
Note:
If you install more than one Borland Enterprise Server on the same computer, make
sure services included with each server have unique port ID numbers. Each
installation must have completely different install paths; the install directories at the
top level must be different. Also, you must modify the server.xml file for the
standard Partition to make sure the container services included with each server
have unique port ID numbers. Keep the defaults on one server, but change the
defaults for all other servers so that they have unique port ID numbers.
We recommend that you use the Management Console Partition Services properties
panel to hange port ID numbers. For the web COntainer (Tomcat 4.1), change the
XML directly in /var/servers/server_name/adm/properties/
partitions/standard/tomcat/conf/.
To change Web container port IDs:
1 Open the Borland Enterprise Server Management Console.
2 In the navigation tree, expand Partition Services.
3 Right-click the Web Container node and select Configure.
The General tab displays the server.xml file. To edit port ID properties, use the
Connectors tab.
4 Go to the Connectors tab and set a different port number in the Port field.
Setting environment variables for VisiBroker (Edition and
standalone)
After installation, you need to set several environment variables (see licensing
section) in order to run VisiBroker. During installation, two profile scripts are created
for you. Use these scripts to set the environment variables.
To set the variables:
1 Determine the appropriate script for your shell. These scripts are located in the
main VisiBroker installation directory.
If you are using the Korn or Bourne shell, use the following script to set
environment variables:
vbroker.sh
If you are using the C shell, use the following script to set environment variables:
vbroker.csh
2 Add a command to your .profile, .cshrc, or .login file to run the script
automatically when you log in.
Installing on UNIX/Linux 4-7

Uninstalling the Borland Enterprise Server
Changing environment variables in UNIX
In UNIX, the necessary environment variables are added to the vbroker.sh and
vbroker.csh shell script files. These files are generated automatically when you
install VisiBroker.
To change environment variables, use one of the following methods:
• If you're using the Korn or Bourne shell, use the following syntax to set the
variable:
variable=value
export variable
where variable is the name of the environment variable you want to change and
value is the value you want to assign to the variable. You can enter this command
at the command prompt or add a statement to your .profile file.
In this example, the port number is changed to 12000.
OSAGENT_PORT=12000
export OSAGENT_PORT
• If you're using the C shell (csh), use the setenv command to see the variable:
setenv variable value
where variable is the name of the environment variable you want to change and
value is the value you want to assign to the variable. You can enter this command
at the command prompt or add a statement to your .cshrc or .login file.
Uninstalling the Borland Enterprise Server
To uninstall Borland Enterprise Server
1 Change or (cd) to the Borland Enterprise Server installation directory.
2 Enter the uninstall command:
uninstall
The contents of the Borland Enterprise Server directory are deleted.
To uninstall SonicMQ, use SonicMQ's uninstaller located in:
/SonicMQ/.
The SonicMQ uninstaller will prompt you about deleting a large number of files. It is
safe to say yes to all of these requests.
Running the installer without a GUI
The installer is capable of running in a text only mode for UNIX systems. You can
invoke the installer with a parameter which specifies the UI mode:
4-8 Installation Guide

Installing on Linux
installer.bin -i console
The installer will write to stdin and read from stdin. This will allow you to telnet
from one system to another and run the installer remotely.
Installing on Linux
Linux:
The following instructions are specific to Linux installation.
KornShell
Important
You need the KornShell installed on Linux in order to run Borland Enterprise Server
on Linux.
To install the Borland Enterprise Server on Linux:
1 If you are downloading the Borland Enterprise Server from the Web site, you must
first untar to save it in binary format.
2 After saving the linux.bin file, you can then run it to launch the installer.
3 Obtain all permissions, or chmod all, where 777 indicates all, to run the install
script.
4 If you're installing from CD, enter the following commands:
• $ cd /mnt/cdrom
• $ ./install_linux
Installing on UNIX/Linux 4-9

4-10 Installation Guide

Chapter
5
Chapter5Installing BES Using Silent
Installation (Windows, Solaris, Linux)
Note:
This document describes procedures for installing the Borland Enterprise Server
using silent installation for Windows, Solaris and Linux.
For the latest platform information and system requirements for installing Borland
Enterprise Server, go to http://www.borland.com/techpubs/bes/platforms.
What is silent installation?
Important
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).
Using silent install implies your consent to the Borland Enterprise Server License
Agreement.
Preparing for installation
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.
Installing BES Using Silent Installation (Windows, Solaris, Linux) 5-1

Preparing for installation
Disk space requirements
Note:
The total amount of disk space required to install the Borland Enterprise Server
depends on which components you install. For more information, see Chapter 2,
“Planning your installation” and http://www.borland.com/techpubs/bes/
platforms.
Disk space includes JDK installation.
JDK
Important
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".
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.
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.
Uninstalling previous versions of Borland Enterprise Server
It is not necessary to uninstall previous versions of VisiBroker standalone.
To uninstall the Borland Enterprise Server:
1 Shut down any servers that are running.
2 Make sure there are no background processes such as osagent, running during the
uninstall.
3 Open the installation directory.
4 Double-click the Uninstall icon.
5 Click Uninstall to completely remove all components that were installed.
The Uninstall program does not remove any configuration or application files and
folders that were created after the installation.
5-2 Installation Guide

Using silent installation
Reinstalling Borland Enterprise Server
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.
Using silent installation
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 is
the name of your file. Now you can invoke the silent installation process using the
values specified in the properties file(s).
Invoking silent installation on Windows
To invoke the silent installation process on Windows:
1 Open a command prompt.
2 If installing Borland Enterprise Server by downloading from the Borland web site:
• Go to http://www.borland.com/products/downloads and download the
Borland Enterprise Server for Windows.
• Go to the directory where you downloaded the installer and invoke the silent
installation process by entering the following command. Make sure to specify
the full path name of the propertiesfile file:
installer.exe -f
where installer is the name of the Borland Enterprise Server installer and
is the full path of the propertiesfile file.
For example:
BES52_Windows.exe -f c:\silentproperties.txt
3 If installing Borland Enterprise Server from a CD-ROM:
• Insert the Borland Enterprise Server CD into the CD-ROM drive.
• Open a command-line shell.
• Go to the CD-ROM directory.
• Invoke the silent installation process by entering the following command. Make
sure to specify the full path name of the propertiesfile file:
installer.exe -f
Installing BES Using Silent Installation (Windows, Solaris, Linux) 5-3

Using silent installation
where installer is the name of the Borland Enterprise Server installer and
is the full path of the propertiesfile file.
For example:
install_windows.exe -f c:\silentproperties.txt
Invoking silent installation on Solaris or Linux
To invoke the silent installation process on Solaris or Linux:
1 Open a command-line shell.
2 If installing Borland Enterprise Server by downloading from the Borland web site:
• Go to http://www.borland.com/products/downloads and download the
Borland Enterprise Server for Solaris or Linux.
• Unzip and untar for the installer .bin file.
• Go to the directory where you downloaded the installer and invoke the silent
installation process by entering the following command. Make sure to specify
the full path name of the propertiesfile file:
installer.bin -f
where installer is the name of the Borland Enterprise Server installer and
is the full path of the propertiesfile file.
For example:
BES52_Solaris64/32.bin -f usr/home/myname/silentproperties.fil
or
BES52_Linux.bin -f /opt/myname/silentproperties.fil
3 If installing Borland Enterprise Server from CD-ROM:
• Insert the Borland Enterprise Server CD into the CD-ROM drive.
• Open a command-line shell.
• Go to the CD-ROM directory.
• Invoke the silent installation process by entering the following command. Make
sure to specify the full path name of the propertiesfile file:
installer.bin -f
where installer is the name of the Borland Enterprise Server installer and
is the full path of the propertiesfile file.
For example:
install_solaris.bin -f usr/home/myname/silentproperties.fil
or
install_linux.bin -f /opt/myname/silentproperties.fil
5-4 Installation Guide

Windows properties file
Windows properties file
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
(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
(required). A server name of
your choice.
JVM_JDK_HOME
\jdk\jdk1.4.1 (optional). Default
is jdk\jdk1.4.1 See discussion of JDK_HOME in
“Use of JVM_JDK_HOME” on page 5-6.
BES_SERIAL
BES_KEY
INSTALL_TYPE_1
INSTALL_TYPE_2
optional, required to install
with a license.
optional, required to install with a
license.
Borland Enterprise Sever (required). Installs
full Borland Enterprise Server. Use TYPE_1 or
TYPE_2, NOT BOTH.
Borland VisiBroker (optional). Installs Borland
VisiBroker Standalone. Use TYPE_1 or TYPE_2,
NOT BOTH.
Solaris/Linux properties file
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
(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
(required). A server name of
your choice.
Installing BES Using Silent Installation (Windows, Solaris, Linux) 5-5

Solaris/Linux properties file
Variable
JVM_JDK_HOME
BES_SERIAL
BES_KEY
INSTALL_TYPE_1
INSTALL_TYPE_2
Value
\jdk\jdk1.4.1 (optional). Default
is jdk\jdk1.4.1 See discussion of JDK_HOME in
Use of JVM_JDK_HOME section.
optional, required to install
with a license.
optional, required to install with a
license.
Borland Enterprise Sever (required). Installs
full Borland Enterprise Server. Use TYPE_1 or
TYPE_2, NOT BOTH.
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.
Use of JVM_JDK_HOME
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".
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=\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=
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.
5-6 Installation Guide

Index
Symbols
... ellipsis 1-3
| vertical bar 1-3
A
access privileges 4-2
Application Server
network requirements 2-3
Application Server CD 4-1
B
Back button 4-5
Borland Developer Support
contacting 1-3
Borland Enterprise Server
uninstalling 3-8
Borland Technical Support
contacting 1-3
Borland Web site 1-3, 1-5
brackets 1-3
button
Back 4-5
C
CD 4-1
mounting 4-2
cd command 4-2
change permissions script
iaschangeowner 4-3
changing partition JDK 4-5
commands
cd 4-2
conventions 1-3
mkdir 4-2
mount 4-2
uninstall 4-8
components
management hub 3-4
Console
installing 3-6
installing standalone 3-6
network requirements 2-3
standalone 3-6
D
Developer Support
contacting 1-3
disk space requirements 2-3
documentation 1-1
.pdf format 1-1
accessing 3-7, 4-6
accessing Help Topics 1-2
Developer's Guide 1-2
Installation Guide 1-2
on the web 1-5
PDFs 4-7
platform conventions used in 1-3
type conventions used in 1-3
updates 1-1
User's Guide 1-2
VisiBroker Developer's Guide 1-2
VisiBroker GateKeeper Guide 1-2
VisiBroker Programmer's Reference 1-2
VisiBroker VisiNotify Guide 1-2
downloading, from web 4-1
E
environment variables
changing VisiBroker 4-8
setting 4-7
setting VisiBroker 4-7
VisiBroker 4-7, 4-8
error message
UNIX 4-6
F
file permissions
iaschangeowner 4-3
options 4-3
H
Help Topics
accessing 3-7, 4-6
HP-UX
Java products 2-2, 3-2, 4-2
Index I-1

I
iaschangeowner
options 4-3
rules 4-4
usage 4-4
IBM AIX
Java products 2-2, 3-2, 4-2
installation
of multiple servers 4-7
preparing for 3-1, 4-1
installing
command-line 5-1
HP-UX 2-1
IBM-AIX 2-1
Linux 2-1, 4-9
multiple servers 4-7
planning 2-1
reinstalling 5-3
remotely 4-8
requirements 2-1
silent mode 5-1
without a GUI 4-8
J
Java Development Kit (JDK) 4-5
JDK 2-2, 3-1, 4-2
1.3 2-2, 3-2, 4-2
1.4 2-2, 3-2, 4-2
changing 2-2, 3-2, 4-2
HP-UX 2-2, 3-2, 4-2
IBM AIX 2-2, 3-2, 4-2
other 2-2, 3-2, 4-2
Partition 4-5
requirements 2-2, 3-1, 4-2
VisiBroker 2-2
VisiClient Container 3-3
JDK home
silent installation 5-6
L
license 2-3
update 3-9
license key 2-3
licensing 2-1, 3-9
console 3-9
licensing error message 4-6
Linux
KornShell 4-9
silent installation 5-4
M
Management Hub 3-4
message broker
SonicMQ 3-6
messaging service
SonicMQ 2-3
mkdir command 4-2
multiple servers 4-7
N
network, planning 2-3
Newsgroups 1-5
O
Online Help
accessing 1-2
P
PDF documentation 1-1
permissions command
iaschangeowner 4-3
planning, network 2-3
port
management port 3-5
osagent 3-5
Smart Agent port 3-5
user port 3-5
port ID numbers 4-7
preparing, for installation 4-1
properties file
silent installation 5-3
R
registering
Borland Community Member 3-10
I-2 Installation Guide

y phone 3-10
console 3-9
online 3-10
quick registration 3-10
Software Registration Account 3-10
registration 2-1, 3-9
reinstalling
Borland Enterprise Server 5-3
S
serial number 2-3
silent installation 5-1
invoking 5-3
JDK 5-2
JDK home usage 5-6
Linux 5-1, 5-4
properties file 5-3
Solaris 5-1, 5-4
SonicMQ 5-2
text file 5-3
using 5-3
what is 5-1
Windows 5-1, 5-3
silent installation properties file
Solaris 5-5
Windows 5-5
single computer, installation 2-3
Smart Agent port 2-3
changing 3-6
Software
updates 1-5
Solaris
silent installation 5-4
Solaris operating system 4-2
SonicMQ 2-3
messaging service 3-6
square brackets 1-3
stand-alone configuration 2-3
Support
contacting 1-3
symbols
ellipsis ... 1-3
vertical bar | 1-3
T
Technical Support
contacting 1-3
U
UDP services 2-3
uninstall command 4-8
Uninstalling
on NT 3-8
uninstalling
Borland Enterprise Server 5-2
UNIX
idl2cpp 4-6
licensing 4-6
licensing error message 4-6
text only mode 4-8
VBJ 4-6
V
VisiBroker 2-3, 4-1
changing evironment variables 4-8
JDK 2-2
setting evironment variables 4-7
standalone 3-4
standalone version 3-3
VisiBroker Documentation
VisiNotify Guide 1-2
VisiBroker documentation
Developer's Guide 1-2
GateKeeper Guide 1-2
Programmer's Reference 1-2
W
web browser 3-7, 4-6
Windows properties file
silent installation 5-5
World Wide Web
Borland documentation on the 1-5
Borland newsgroups 1-5
Borland updated software 1-5
Index I-3

I-4 Installation Guide