• No results found

BES Installation Guide. Enterprise Server 6.5

N/A
N/A
Protected

Academic year: 2021

Share "BES Installation Guide. Enterprise Server 6.5"

Copied!
51
0
0

Loading.... (view fulltext now)

Full text

(1)

Enterprise Server

6.5

(2)

Borland Software Corporation 100 Enterprise Way

Scotts Valley, California 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-2004 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/).

This product includes software developed by Steve Viens and contributors. All rights reserved (http://juddi.org/).

This product includes software developed by the MX4J project. All rights reserved (http://mx4j.sourceforge.net/).

BES0065WW21000

0102030405-9 8 7 6 5 4 3 2 1 PDF

(3)

Contents

Chapter 1

Introduction to Borland Enterprise Server

(BES)

1

BES Products and Editions overview . . . 1

AppServer Edition . . . 1

AppServer Edition features . . . 2

VisiBroker Edition . . . 2

VisiBroker Edition features . . . 2

Borland Enterprise Server Documentation . . . 3

Accessing BES online help topics in the standalone Help Viewer . . . 4

Accessing BES online help topics from within a BES GUI tool . . . 4

Documentation conventions . . . 4

Platform conventions . . . 5

Contacting Borland support . . . 5

Online resources. . . 5

World Wide Web . . . 6

Borland newsgroups . . . 6

Chapter 2

Planning your installation

7

Package contents . . . 7

System requirements . . . 7

JDK . . . 8

Web . . . 8

Disk space requirements . . . 8

Licensing . . . 8

What's next? . . . 9

Chapter 3

Installing BES on Windows

11

Preparing for installation . . . . 11

JDK . . . . 12

Installing Borland Enterprise Server . . . . 12

Install log . . . . 15

Product documentation . . . . 15

Installing a standalone Borland Management Console . . . . 15

Installing more than one BES instance . . . . 16

Configuring VisiBroker C++ server, VisiTransact, or VisiNotify license variables . . . . 16

Borland product registration wizard . . . . 16

Migrating an existing 6.0 license . . . . 17

Direct registration . . . . 18

Email registration . . . . 18

Web page registration . . . . 18

Telephone registration . . . . 19

Uninstalling Borland Enterprise Server . . . . 19

Chapter 4

Installing BES on Solaris and Linux

21

Installing on other platforms . . . 21

Preparing for installation . . . 21

JDK . . . 22

JRE requirements for Linux download installation. . . 22

Mounting the BES CD on Solaris . . . 22

Preparing to install BES on Linux . . . 23

Installing Borland Enterprise Server . . . 23

Install log. . . 26

Product documentation . . . 27

Installing a standalone Management Console. . . . 27

Installing more than one BES instance . . . 27

Running the installer without a GUI . . . 28

Configuring VisiBroker for C++ server, VisiTransact, or VisiNotify license variables . . . . 28

Using the setuser tool to manage ownership . . . . 29

Usage. . . 29

Examples: . . . 30

Changing the ownership of an installation and supporting files . . . 30

Enabling multi-user mode (MUM) . . . 30

Enabling Managed Objects to start as root while running in MUM . . . 31

Enabling JavaScript support when starting Managed Objects while in MUM . . . 32

Disabling multi-user mode . . . 32

Borland product registration wizard . . . 33

Migrating an existing 6.0 license . . . 33

Direct registration. . . 34

Email registration . . . 34

Web page registration . . . 34

Telephone registration . . . 35

Uninstalling Borland Enterprise Server . . . 35

Chapter 5

Installing BES Using Silent Installation

(Windows, Solaris, Linux)

37

What is silent installation? . . . 37

Preparing for installation . . . 37

Disk space requirements . . . 37

JDK . . . 38

Using silent installation . . . 38

Invoking silent installation on Windows. . . 38

Invoking silent installation on Solaris . . . 39

Invoking silent installation on Linux. . . 39

Properties file for silent installation . . . 40

Sample silent installation properties for Windows . . . 42

Sample silent installation properties for Solaris or Linux . . . 42

(4)

iv

Tables

5.1 Properties File Contents for Silent Installation 40

(5)
(6)

C h a p t e r 1 : I n t r o d u c t i o n t o B o r l a n d E n t e r p r i s e S e r v e r ( B E S ) 1

C h a p t e r

1

Chapter 1

Introduction to Borland Enterprise

Server (BES)

Borland Enterprise Server is a set of services and tools that enable you to build, deploy, and manage distributed enterprise applications in your corporate environment.

BES Products and Editions overview

Borland provides the following “Editions” of its Enterprise Server in order to better meet your specific deployment requirements:

AppServer Edition — A leading, certified implementation of the J2EE 1.3 standard,

Borland Enterprise Server AppServer Edition supports the latest industry standards

such as EJB 2.1, JMS 1.02, Servlet 2.3, JSP 1.2, CORBA 2.6, XML, and SOAP. Borland provides three versions of AppServer Edition, which include leading enterprise messaging solutions for Java Messaging Service (JMS) management (Tibco, SonicMQ, and OpenJMS).

VisiBroker Edition — For the CORBA developer, Borland provides Borland

Enterprise Server VisiBroker Edition, which includes both VisiBroker for Java and VisiBroker for C++ to leverage the industry-leading VisiBroker Object Request

Broker (ORB). Both are complete implementations of the CORBA 2.6 specification. Each BES Edition and product is built upon the same server core, and they seamlessly interact with each other. You can choose the degree of functionality and services you need, and if your needs change, it is simple to upgrade your license. See Chapter 3, “Installing BES on Windows” or Chapter 4, “Installing BES on Solaris and Linux” for details.

AppServer Edition

Borland Enterprise Server AppServer Edition allows you to securely deploy and manage all aspects of your distributed Java and CORBA applications that implement the J2EE 1.3 platform standard.

With AppServer Edition, the number of server instances per installation is unlimited, so the maximum of concurrent users is unlimited.

(7)

B E S P r o d u c t s a n d E d i t i o n s o v e rv i e w

AppServer Edition includes:

A complete, certified implementation of J2EE 1.3.Apache Web Server version 2.0

Borland Security, which provides a framework for securing BES.

Single-point management of leading JMS management solutions included with BES

(Tibco, SonicMQ, and OpenJMS).

Strong management tools for distributed components, including applications

developed outside of BES.

AppServer Edition features

AppServer Edition offers the following features:

Support for a broad spectrum of enterprise server platforms (please refer to http://

www.borland.com/techpubs/bes/platforms for a list of the platforms supported for BES).

Full support for clustered topologies.

Seamless integration with the VisiBroker ORB infrastructure.

Integration with the Borland JBuilder integrated development environment.Enhanced integration with other Borland products including Borland Together

ControlCenter, Borland OptimizeIT ServerTrace, Borland Janeva, and Borland Deployment Op-Center.

BES allows existing applications to be exposed as Web Services and integrated

with new applications or additional Web Services. Borland Web Services support is based on Apache Axis 1.2 technology, the next-generation Apache SOAP server that supports SOAP 1.2.

VisiBroker Edition

VisiBroker is for distributed deployments that require CORBA to communicate between both Java and non-Java objects. It is available on a wide range of platforms (hardware, operating systems, compilers and JDKs). VisiBroker Edition solves all the problems normally associated with distributed systems in a heterogeneous environment. VisiBroker Edition includes:

VisiBroker for Java and VisiBroker for C++, two implementations of the

industry-leading Object Request Broker.

VisiNaming Service, a complete implementation of the Interoperable Naming

Specification in CORBA 2.6.

GateKeeper, a proxy server for managing connections to CORBA Servers behind

firewalls.

VisiBroker Console, a GUI tool for easily managing a CORBA environment.

VisiBroker Edition features

VisiBroker Edition offers the following features:

“Out-of-the-box” security and web connectivity.

Seamless integration to the J2EE Platform, allowing CORBA clients direct access to

EJBs.

A robust Naming Service (VisiNaming), with caching, persistent storage, and

replication for high availability.

(8)

C h a p t e r 1 : I n t r o d u c t i o n t o B o r l a n d E n t e r p r i s e S e r v e r ( B E S ) 3 B o r l a n d E n t e r p r i s e S e rv e r D o c u m e n t a t i o n

Load distribution across a cluster of CORBA servers.Full compliance with the OMG's CORBA 2.6 Specification.

Integration with the Borland JBuilder integrated development environment.Enhanced integration with other Borland products including Borland Janeva and

Borland Deployment Op-Center.

Borland Enterprise Server Documentation

The BES documentation set includes the following:

BES Installation Guide — describes how to install BES on your network. It is written

for system administrators who are familiar with Windows or UNIX operating systems.

BES Developer's Guide — provides detailed information about packaging,

deployment, and management of distributed object-based applications in their operational environment.

Borland Management Console User's Guide — provides information about using the

Borland Management Console GUI.

Borland Security Guide — describes Borland's framework for securing BES,

including VisiSecure for VisiBroker for Java and VisiBroker for C++.

BES VisiBroker for Java Developer's Guide — describes how to develop VisiBroker

applications in Java. It familiarizes you with configuration and management of the Visibroker ORB and how to use the programming tools. Also described is the IDL compiler, the Smart Agent, the Location, Naming and Event Services, the Object Activation Daemon (OAD), the Quality of Service (QoS), and the Interface Repository.

BES VisiBroker for C++ Developer's Guide — describes how to develop VisiBroker

applications in C++. It familiarizes you with configuration and management of the Visibroker ORB and how to use the programming tools. Also described is the IDL compiler, the Smart Agent, the Location, Naming and Event Services, the OAD, the QoS, and the Interface Repository.

BES VisiBroker for C++ API Reference — provides a description of the classes and

interfaces supplied with VisiBroker for C++.

BES VisiBroker VisiTime Guide — describes Borland's implementation of the OMG

Time Service specification.

BES VisiBroker VisiNotify Guide — describes Borland's implementation of the OMG

Notification Service specification and 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).

BES VisiBroker VisiTransact Guide — describes Borland's implementation of the

OMG Object Transaction Service specification and the Borland Integrated Transaction Service components.

BES VisiBroker VisiTelcoLog Guide — describes Borland's implementation of the

OMG Telecom Log Service specification.

BES 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.

The documentation is typically accessed through the Help Viewer installed with your BES product. You can choose to view help from the standalone Help Viewer or from within a BES GUI tool. Both methods launch the Help Viewer in a separate window and

(9)

D o c u m e n t a t i o n c o n v e n t i o n s

give you access to the main Help Viewer toolbar for navigation and printing, as well as access to a navigation pane. The Help Viewer navigation pane includes a table of contents for all BES books and reference documentation, a thorough index, and a comprehensive search page.

Important Updates to the product documentation, as well as PDF versions, are available on the web at http://www.borland.com/techpubs/bes.

Accessing BES online help topics in the standalone Help Viewer

To access the online help through the standalone Help Viewer on a machine where the product is installed, use one of the following methods:

WindowsChoose Start | Programs | Borland Deployment Platform | Help Topics

or, open the Command Prompt and go to the product installation \bin directory,

then type the following command: help

UNIX Open a command shell and go to the product installation /bin directory, then enter the command:

help

Tip During installation on UNIX systems, the default is to not include an entry for bin in your PATH. If you did not choose the custom install option and modify the default for PATH entry, and you do not have an entry for current directory in your PATH, use ./ help to start the help viewer.

Accessing BES online help topics from within a BES GUI tool

To access the online help from within a BES GUI tool, use one of the following methods:

From within the Borland Management Console, choose Help | Help TopicsFrom within the Borland Deployment Descriptor Editor (DDEditor), choose Help |

Help Topics

From within the VisiBroker Console, choose Help | Help Topics

The Help menu also contains shortcuts to specific documents within the online help. When you select one of these shortcuts, the Help Topics viewer is launched and the item selected from the Help menu is displayed.

Documentation conventions

The documentation for BES uses the typefaces and symbols described below to indicate special text:

Convention Used for

italics Used for new terms and book titles.

computer Information that the user or application provides, 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.

(10)

C h a p t e r 1 : I n t r o d u c t i o n t o B o r l a n d E n t e r p r i s e S e r v e r ( B E S ) 5 C o n t a c t i n g B o rl a n d s u p p o r t

Platform conventions

The BES documentation uses the following symbols to indicate platform-specific information:

Windows: All supported Windows platforms. Win2003: Windows 2003 only

WinXP: Windows XP 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 fee-based, consultant-level support and detailed assistance.

For more information about Borland's support services or contacting Borland Technical Support, please see our web site at: http://support.borland.com and select your geographic region.

When contacting Borland's support, be prepared to provide the following information:

Name

Company and site IDTelephone number

Your Access ID number (U.S.A. only)Operating system and versionBorland product name and versionAny patches or service packs appliedClient language and version (if applicable)Database and version (if applicable)

Detailed description and history of the problemAny 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 http://www.borland.com

Online Support http://support.borland.com (access ID required)

Listserv To subscribe to electronic newsletters, use the online form at: http://www.borland.com/products/newsletters

(11)

C o n t a c t i n g B o r l a n d s u p p o r t

World Wide Web

Check http://www.borland.com/bes regularly. The BES 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/download_bes.html (updated BES

AppServer Edition software and other files)

http://www.borland.com/products/downloads/download_visibroker.html (updated

BES VisiBroker Edition software and other files)

http://www.borland.com/techpubs/bes (documentation updates and PDFs)

http://info.borland.com/devsupport/bdp/faq/ (Borland Enterprise Server and Borland

Deployment Op-Center FAQs)

http://community.borland.com (contains our web-based news magazine for

developers)

Borland newsgroups

You can participate in many threaded discussion groups devoted to the Borland Enterprise Server products. Visit http://www.borland.com/newsgroups for information about joining user-supported newsgroups for Enterprise Server and other Borland products.

(12)

C h a p t e r 2 : P l a n n i n g y o u r i n s t a l l a t i o n 7

C h a p t e r

2

Chapter 2

Planning your installation

This guide describes installation and installation-related tasks for installing Borland Enterprise Server (BES) on Windows, UNIX, and Linux.

Important Go to http://www.borland.com/techpubs/bes for documentation updates and more information.

Some recommendations:

You can install the Borland Management Console separately. Typically, you install

BES on a large shared UNIX or Windows machine. We recommend you 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/or the examples is

optional, however, Borland recommends you install both.

Package contents

The package contains the Borland Deployment Platform CD and product documentation. Your package may include additional product CDs that ship with Borland Enterprise Server.

Note You can also download the Borland Software from the Borland web site: http://www.borland.com/products/downloads/download_bes.html.

System requirements

For the latest information on platforms supported by Borland Enterprise Server and for JDK requirements, please refer to the Borland web site: http://www.borland.com/ techpubs/bes/platforms

In addition to platform-specific requirements, the Borland Enterprise Server

components use TCP and UDP Broadcast services to communicate. Even if you are running the components on a single machine you must have TCP and UDP services available.

(13)

D i sk s p a c e r e q u i r e m e n t s

JDK

The installer installs JDK versions 1.4.2 and 1.3.1. on Windows, and JDK 1.4.2 on UNIX platforms. The Borland Enterprise Server infrastructure and tools use JDK 1.4.2.

Web

To use the Web engine and Web Administration Tool included with BES, you need one of the following web browsers:

Netscape Navigator, version 4.6 or laterMicrosoft Internet Explorer, version 5.0 or later

Disk space requirements

For disk space requirements, refer to http://www.borland.com/techpubs/bes/platforms.

Important The disk space requirements can be affected by:

operating systemJDK

Licensing

There are two types of BES licenses:

Node-locked licenses. These licenses are locked to the system on which they are

applied and activated. You cannot copy these licenses to another system, and they cannot be accessed from a BES product running on another system. If you reinstall the software on the same system, you will need to reactivate the license.

Network licenses. These licenses require the use of a license server. BES

supports the use of either Belise (Borland's license server), or FlexLM, a popular third-party license server found in many IT environments. Refer to the instructions in the email you receive from Borland for activating and using your network licenses. BES node-locked licenses must be registered and activated before using the product. To apply node-locked licenses you will need the following:

The Serial Number and Key, or the activation file for each license. These will

arrive in an email from Borland.

A Borland Developer Network (BDN) account. If you don't have an account, you

will be able to create it during the registration/activation process described in

“Installing BES on Windows” on page 11 and “Installing BES on Solaris and Linux” on page 21.

Internet access. This is required if you want to use the Direct or Web page

methods for activating your license. This can be from any system - not necessarily the system on which your product is installed.

If you are applying a license to a remote system, you must have Telnet access to that system and some way to copy (that is, FTP) the activation file to that system.

(14)

C h a p t e r 2 : P l a n n i n g y o u r i n s t a l l a t i o n 9 W h a t ' s n e x t ?

What's next?

Once you've planned your network installations, you are ready to install BES. If you are installing on Windows, see Chapter 3, “Installing BES on Windows”. If you are installing on UNIX, see Chapter 4, “Installing BES on Solaris and Linux”.

(15)
(16)

C h a p t e r 3 : I n s t a l l i n g B E S o n W i n d o w s 11

C h a p t e r

3

Chapter 3

Installing BES on Windows

This section describes how to install Borland Enterprise Server (BES) and related components on Windows. If you are installing on Solaris or Linux, see Chapter 4, “Installing BES on Solaris and Linux”.

Important For documentation updates, go to http://www.borland.com/techpubs/bes.

Note We recommend uninstalling any previous versions of BES, or installing the new version to a different location; on a different install path. For more information on installing multiple servers, see “Installing more than one BES instance” on page 16.

Note If you have already installed an evaluation version and have since purchased a license to use BES on a permanent basis, you do not need to reinstall the version of the software you evaluated. You can use the License Manager (launched from the Tools menu in the Management Console) to remove your evaluation license, then add and activate your new, permanent license. For information on activating your new license, see “Borland product registration wizard” on page 16.

Preparing for installation

You can install BES from the CD or download the software from the Borland web site http://www.borland.com/products/downloads/download_bes.html.

Before you install BES:

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/download_bes.html.

If you are installing from CD, place the CD into your CD-ROM drive.

If you want to perform a silent installation using definitions from a properties file,

see Chapter 5, “Installing BES Using Silent Installation (Windows, Solaris, Linux)”.

(17)

I n s t a l l i n g B o r l a n d E n t e r p r i s e S e r v e r

JDK

The installer installs JDK versions 1.4.2 and 1.3.1 on Windows. The BES infrastructure and tools use JDK 1.4.2. For information about changing a Partition's JDK after you have completed the product installation, go to Changing the JDK in the “Using Partitions” section of the BES User's Guide.

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.

Installing Borland Enterprise Server

To install BES and related components:

1 You can download the BES installer from the web or install from CD. 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. If you are installing a BES installer downloaded from the web, double-click the downloaded executable to start the installation.

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.

2 Select the Borland Deployment Platform product you want to install:

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.

3 License agreement. Installation and use of BES requires acceptance of the license

agreement.

4 Choose Install Folder. This creates a new installation of BES, or adds components

to an existing 6.5 installation. Either accept the default (C:\Borland\BDP) or choose another location.

Important You cannot install this version of BES on top of previous releases.

5 Choose Product Components. Depending on the Borland Deployment Platform

product you are installing, select from the following product components for each feature set:

a 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” on page 15.

Server. All server components, such as the Partition, Apache Web server,

(18)

C h a p t e r 3 : I n s t a l l i n g B E S o n W i n d o w s 13 I n s t a l l i n g B o r l a n d E n t e r p ri s e S e r v e r

Client. Components for client applications (EJB client and CORBA client). Documentation. Suite of online documentation.

Examples. Example applications for Borland Enterprise Server.

b 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.

6 Choose VisiBroker Extended Services. If you chose the option to install the

VisiBroker Extended Services you purchased, select from the following extended services:

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

7 Choose Install Type. Typical/Custom panel:

a Typical. Express install - uses default settings. The installer generates the BES

example configuration, which is comprised of different example Partitions, and their supporting services.

In addition, the typical installation includes the following defaults:

Smart Agent port. Also known as the 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.

Management port. The port BES listens to for management functionality in the

Management Console. You can use the Management Console to change the Smart Agent port (sometimes referred to as the “user port”) after installation is completed. The default is 42424.

Agent name. Every agent using the same Smart Agent (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.

Product icons. The typical installation does not install product icons. To install

(19)

I n s t a l l i n g B o r l a n d E n t e r p r i s e S e r v e r

Adding the BES bin directory to your PATH variable. The typical installation

does not add the BES 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.

Adding the VisiBroker environment variables. The typical installation does not

add the VisiBroker environment variables to your system environment. If you choose the Custom install type to add the VisiBroker environment variables, the installation sets the BES_LIC_DIR to <install_dir>\var and

BES_LIC_DEFAULT_DIR to <install_dir>\license.

b Custom. This option allows you to set various installation options, such as:

Specifying Smart Agent port/ Management port/ Agent name to other than

default values (see “Choose Install Type. Typical/Custom panel:” on page 13

for the default values).

Product icons. This allows you to choose a shortcut folder in a new program

group, an existing program group, in the Start menu, on the desktop, or in another location.

Example management configuration setup. To install BES/BDOC sample

management configurations, choose “Yes” (default).

Include bin directory in PATH. The default is “No”. To add the directory to your

PATH, choose “Yes”.

Include VisiBroker environment variables. The default is “No”. To add the

VisiBroker environment variables to your system environment, choose “Yes”. The installation sets the BES_LIC_DIR to <install_dir>\var and

BES_LIC_DEFAULT_DIR to <install_dir>\license.

8 Pre-Installation Summary. Review the displayed information before proceeding

with the installation. You can click the Previous button to revisit and change any selections you made except your choice for which product to install.

9 To approve your choices and start installing, click the Install button.

10 Registration.

To launch the Borland Product Registration Wizard before exiting the installer,

choose “Yes” (default) and click Next. The Registration Wizard launches in a separate window (see “Borland product registration wizard” on page 16). After you dismiss the Registration Wizard, the installer completion panel displays.

If you are installing an evaluation or free version of BES, you are not prompted to

launch the Registration Wizard. Before using BES, copy the license activation key file you receive by email from Borland to the <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/download_bes.html 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 6.0 on the same machine where you installed BES 6.5, use the lmadm command-line tool to migrate your 6.0 license for use with the newly-installed BES 6.5 software (see “Migrating an existing 6.0 license” on page 17). For information about BES license types, see Chapter 2, “Planning your installation”.

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 Using the License Manager in

Management Console User's Guide).

(20)

C h a p t e r 3 : I n s t a l l i n g B E S o n W i n d o w s 15 I n s t a l l l o g

Install log

The installer generates an install log that is written to the root of the installation directory if you installed BES from CD, or to the folder where the installer file resides if you used a downloaded file to install BES.

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 file is an XML formatted log with installation-specific information, such as errors.

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:

At the command prompt, use the following command:

help

To recognize the help command, your path system variable must include the <install_dir>\bin directory, or you can enter the path explicitly.

Choose Start | Programs | Borland Deployment Platform | Help TopicsFrom within the Borland Management Console, go to the Help menuFrom within the DDEditor, go to the Help menu

From within VisiBroker Console, go to the Help menu

Note Product documentation updates, HTML and PDF versions are available on the Web: http://www.borland.com/techpubs/bes.

Installing a standalone Borland Management Console

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:

1 On the Choose Product Components panel, select only the Management Console.

2 On the Choose Install Type panel, choose Custom.

3 When the Configuration Settings screen appears, specify the same Management port as those specified for the server(s) you want the Management Console to support.

4 Complete the installation as described in “Borland Enterprise Server AppServer Edition” on page 12.

(21)

I n s t a l l i n g m o r e t h a n o n e B E S i n s t a n c e

Installing more than one BES instance

If you install more than one instance of BES on the same machine:

Each server must have completely different install paths; the install directories at the

top level must be different.

You must modify Management ports with unique port ID numbers to make sure

container services are included with each server.

Keep the defaults on one server, but change the defaults for all other servers so that

they have unique port ID numbers.

Note We recommend you use the Management Console to change port ID numbers. To change Management port numbers:

1 Open the Borland Management Console.

2 Right-click on the Agent whose ports you want to change and select Properties.

3 Enter port numbers as needed. To change Web container port IDs:

1 Open the Borland Management Console.

2 In the navigation tree, expand the Partition whose web container you want to change.

3 Right-click the web container node and select Properties. The Properties tab Service: HTTP/ node displays the connector attributes.

4 To edit port ID properties, enter the values into the table.

For information about updating the Borland web container server.xml, go to the BES

Developer's Guide Web components section.

Configuring VisiBroker C++ server, VisiTransact, or VisiNotify license

variables

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:

1 Open a command window.

2 Change directories to <install dir>\bin.

3 Execute vbroker.bat.

Borland product registration wizard

Before using BES, 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.

(22)

C h a p t e r 3 : I n s t a l l i n g B E S o n W i n d o w s 17 B o r l a n d p ro d u c t r e g i s t r a t i o n w i za r d

If you have a valid, node-locked license for BES 6.0 installed on the same machine as the newly-installed BES 6.5, use the lmadm command-line tool to migrate your 6.0 license for use with the newly-installed BES 6.5 software (see “Migrating an existing 6.0 license” on page 17). (For information about BES license types, see Chapter 2, “Planning your installation”.)

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 product using one of the following registration methods:

Direct. If your system is connected to the Internet, this is the simplest method. The

product registration wizard guides you through all required steps and automatically activates your license for you. For more information, see “Direct registration” on page 18.

Email. You send your registration request via your own email account (from any

system), and will receive an activation file via email that you can apply to your installation. For more information, see “Email registration” on page 18.

Web page. Similar to email, except you register by visiting the Borland web site. For

more information, see “Web page registration” on page 18.

Telephone. You provide information to a Borland representative, who will send you

an activation file by email or mail. For more information, see “Telephone registration” on page 19.

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.

Migrating an existing 6.0 license

To migrate an existing 6.0 node-locked license after installing 6.5:

1 Open a command shell and invoke the 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

2 Enter the option to “Migrate a node locked license”.

3 When prompted, enter the full path to your BES 6.0 installation.

4 When prompted, enter the full path to your BES 6.5 installation.

5 When prompted, choose the option to proceed with the migration and overwrite the existing license.

Note This option overwrites any existing licenses found in the BES 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 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.)

6 After the completion message is displayed, press Enter to continue.

(23)

B o r l a n d p r o d u c t r e g i s t r a t i o n w i z a r d

Direct registration

To use the Borland product registration wizard for Direct registration:

1 Select the Direct registration method in the first wizard screen, and click Next.

2 Indicate whether you have a BDN account, and click Next. If you do not have an account you are prompted to create one in this wizard.

3 If applicable, enter proxy settings for you internet connection.

4 Review the summarized information before clicking Next. The wizard monitors and displays the progress of your registration.

5 When registration is successfully completed, click Next. Then click Finish to close the Wizard.

Email registration

To use the Borland product registration wizard for Email registration:

1 In the first wizard screen, select the Email registration method and click Next.

2 Indicate whether you have a BDN account, and click Next. If you do not have an account you are prompted to create one in this wizard.

3 Review the summarized information before clicking Next.

4 Copy the content of the Email Registration content pane into an email message addressed to [email protected], and click Next.

5 To close the Wizard, click Finish. You will receive a product activation file by email.

6 Copy the activation file into the <install_dir>\license directory, and it will be applied automatically when you start your product.

Web page registration

To use the Borland product registration wizard for Web page registration:

1 In the first wizard screen, select the Web page registration method and click Next.

2 Copy the registration key from the Web Registration step of the wizard, then click Finish to close the Wizard.

3 Start a web browser and open the http://reg.borland.com URL.

4 In the registration web page, enter your BDN account information and click Login. If you do not have an account, click the Create account link (http://reg.borland.com/ srs5/new_user.jsp).

5 In the Product Registration web page, enter the Serial Number and the Registration Key (from the registration wizard) and click Continue.

6 Verify the email address to which the activation file will be sent, and click Register. You will receive a product activation file by email.

7 Copy the activation file into the <install_dir>\license directory, and it will be applied automatically when you start your product.

(24)

C h a p t e r 3 : I n s t a l l i n g B E S o n W i n d o w s 19 U n i n s t a l l i n g B o r l a n d E n t e r p ri s e S e r v e r

Telephone registration

To use the Borland product registration wizard for Telephone registration:

1 In the first wizard screen, select the Telephone registration method and click Next.

2 From the drop-down list, select the location that is nearest you.

3 Click Next, then click Finish to close the Wizard.

4 Dial the number for assistance by telephone and keep the information in the Phone Registration wizard screen on hand.

5 When you receive your activation file, copy it into the <install_dir>\license directory, and it will be applied automatically when you start your product.

Uninstalling Borland Enterprise Server

To uninstall Borland Enterprise Server:

1 Make sure there are no background processes (such as 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.

Note This does not remove files and folders that were created after the installation.

5 After you run the uninstall program, check the installation directory and remove any unnecessary files and subdirectories.

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.

(25)
(26)

C h a p t e r 4 : I n s t a l l i n g B E S o n S o l a r i s a n d L i n u x 21

C h a p t e r

4

Chapter 4

Installing BES on Solaris and Linux

This section describes how to install Borland Enterprise Server and related

components on the Solaris and Linux operating systems. If you are installing on Windows, see Chapter 3, “Installing BES on Windows”.

Important For documentation updates, go to http://www.borland.com/techpubs/bes.

Note We recommend uninstalling any previous versions of BES, or installing the new version to a different location; on a different install path. For more information on installing multiple servers, see “Installing more than one BES instance” on page 27.

Note If you have already installed an evaluation version and have since purchased a license to use BES on a permanent basis, you do not need to reinstall the version of the software you evaluated. You can use the License Manager (launched from the Tools menu in the Management Console) to remove your evaluation license, then add and activate your new, permanent license. For information on activating your new license, see “Borland product registration wizard” on page 33.

Installing on other platforms

For documentation updates and specific instructions on installing BES on platforms other than Windows (32-bit versions), Solaris, or Red Hat Linux (X86), go to http://www.borland.com/techpubs/bes.

Preparing for installation

You can install BES from the CD or download the software from the Borland web site http://www.borland.com/products/downloads/download_bes.html.

Before you install BES, 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/download_bes.html. If you are installing BES on Linux from a downloaded file, see “Preparing to install BES on Linux” on page 23.

(27)

M o u n t i n g t h e B E S C D o n S o l a ri s

If you are installing from CD, mount the Borland Enterprise Server CD before

starting the installation. (For Solaris see “Mounting the BES CD on Solaris” on page 22. For Linux, see “Preparing to install BES on Linux” on page 23.)

If you want to install from the command line without invoking the installer's GUI, see

“Running the installer without a GUI” on page 28.

If you want to perform a silent installation using definitions from a properties file, see

Chapter 5, “Installing BES Using Silent Installation (Windows, Solaris, Linux)”.

JDK

The JDK, version 1.4.2, is installed during installation on Solaris and Linux. For information about changing a Partition's JDK after you have completed the product installation, go to Changing the JDK in the “Using Partitions” section of the

Management Console User's Guide.

Note For updates on JDK requirements for Solaris, Linux, and for VisiBroker Edition, please refer to the Borland web site, http://www.borland.com/techpubs/bes/platforms.

JRE requirements for Linux download installation

If you are installing BES on Linux using a file downloaded from the Borland download site you need an existing JRE, 1.4.2 or above, in your environment in order to run the extracted installer jar file.

Important When running the extracted installer for Linux, include the full path to your installed JRE.

To check the location and version of your JRE, use the following syntax: $which java

/opt/local/bin/java $java -version java version "1.4.2"

Mounting the BES CD on Solaris

The Borland Enterprise Server CD includes installation software for the Solaris and Linux operating systems. This section describes how to prepare to install BES on Solaris from CD. (To prepare to install BES on Linux, see the “Preparing to install BES on Linux” on page 23 section.)

To mount a CD on your local workstation:

1 Log into your workstation.

Note 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 Open a command shell.

4 To determine if the Volume Manager is running, enter the following command: /usr/bin/ps -ef | grep mountd

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/lib/autofs/automountd

5 If the Volume Manager is running, proceed to “Installing Borland Enterprise Server” on page 23.

(28)

C h a p t e r 4 : I n s t a l l i n g B E S o n S o l a r i s a n d L i n u x 23 P re p a ri n g t o i n s t a l l B E S o n L i n u x

6 If the Volume Manager is not running, become root, then enter the following commands to mount the CD before proceeding to “Installing Borland Enterprise Server” on page 23:

/usr/sbin/mount -F hsfs -r /dev/dsk/device /cdrom where device is the device name of the CD.

7 Enter the following command to change to the CD directory: cd /cdrom

8 To unmount the CD after installing BES, become root and enter the following command:

umount /cdrom

Preparing to install BES on Linux

To prepare to install BES on Linux:

1 If you're installing from a tar file downloaded from the Borland Web site:

a Extract the installation executable from the tar file you downloaded.

b Obtain all permissions, or chmod all, where 777 indicates all, to run the installer.

2 If you're installing BES on Linux from CD:

a Become root and enter the following commands to mount the CD before proceeding to “Installing Borland Enterprise Server” on page 23:

mount /dev/cdrom exit

b Change to the CD directory. cd /mnt/cdrom

Installing Borland Enterprise Server

To install Borland Enterprise Server and related components:

1 You can download the BES installer from the web or install from CD.

a If installing BES from CD:

1 Type the appropriate command:

Solaris: install_solaris

Linux: install_linux

The CD splash screen appears after a few moments.

2 Click the highlighted product.

The installation wizard launches in a separate window.

Note To view Readme and installation documentation on the CD, or to browse the contents of the CD, click the appropriate entries on the splash screen.

b If installing BES on Solaris from a downloaded file:

1 Go to the directory where you extracted the installer.

(29)

I n s t a l l i n g B o r l a n d E n t e r p r i s e S e r v e r

c If installing BES on Linux from a downloaded file:

1 Go to the directory where you extracted the installer.

2 Launch the installation wizard:

<path to JRE>/java -cp <extracted_jar_file> install

Follow the installation wizard's 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.

2 Select the Borland Deployment Platform product you want to install:

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.

3 License agreement. Installation and use of BES requires acceptance of the license

agreement.

4 Choose Install Folder. This creates a new installation of BES, or adds components

to an existing 6.5 installation.

Important You cannot install this version of BES on top of previous releases.

5 Choose Product Components. Depending on the Borland Deployment Platform

product you are installing, select from the following product components for each feature set:

a 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 Management Console” on page 27.

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.

b 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

(30)

C h a p t e r 4 : I n s t a l l i n g B E S o n S o l a r i s a n d L i n u x 25 I n s t a l l i n g B o r l a n d E n t e r p ri s e S e r v e r

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.

6 Choose VisiBroker Extended Services. If you chose the option to install the

VisiBroker Extended Services you purchased, select from the following extended services:

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

7 Choose Install Type. Typical/Custom panel:

a Typical. Express install - uses default settings. The installer generates the BES

example configuration, which is comprised of different example Partitions, and their supporting services.

In addition, the typical installation includes the following defaults:

Smart Agent port. Also known as the 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.

Management port. The port BES listens to for management functionality in the

Management Console. You can use the Management Console to change the Smart Agent port (sometimes referred to as the “user port”) after installation is completed. The default is 42424.

Agent name. Every agent using the same Smart Agent (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.

Adding the BES bin directory to your PATH variable. The typical installation

does not add the BES 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.

Adding the VisiBroker environment variables. The typical installation does not

add the VisiBroker environment variables to your system environment. If you choose the Custom install type to add the VisiBroker environment variables, the installation sets the BES_LIC_DIR to <install_dir>/var and

BES_LIC_DEFAULT_DIR to <install_dir>/license.

b Custom. This option allows you to set various installation options, such as:

Specifying Smart Agent port/ Management port/ Agent name to other than

default values (see “Choose Install Type. Typical/Custom panel:” on page 25

(31)

I n s t a l l l o g

Example management configuration setup. To install BES/BDOC sample

management configurations, choose “Yes” (default).

Include bin directory in PATH. The default is “No”. To add the directory to your

PATH, choose “Yes”.

Include VisiBroker environment variables. The default is “No”. To add the

VisiBroker environment variables to your system environment, choose “Yes”. The installation sets the BES_LIC_DIR to <install_dir>/var and

BES_LIC_DEFAULT_DIR to <install_dir>/license.

8 Pre-Installation Summary. Review the displayed information before proceeding

with the installation. You can click the Previous button to revisit and change any selections you made except your choice for which product to install.

9 To approve your choices and start installing, click the Install button.

10 Registration.

To launch the Borland Product Registration Wizard before exiting the installer,

choose “Yes” (default) and click Next. The Registration Wizard launches in a separate window (see “Borland product registration wizard” on page 16). After you dismiss the Registration Wizard, the installer completion panel displays.

If you are installing an evaluation or free version of BES, you are not prompted to

launch the Registration Wizard. Before using BES, copy the license activation key file you receive by email from Borland to the <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/download_bes.html 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 6.0 on the same machine where you installed BES 6.5, use the lmadm command-line tool to migrate your 6.0 license for use with the newly-installed BES 6.5 software (see “Migrating an existing 6.0 license” on page 33). For information about BES license types, see Chapter 2, “Planning your installation”.

Note If you want to register and activate your license later, either by running the lmadm executable found in the <install_dir>/bin directory or by launching the wizard from the Tools menu in the Management Console (see Using the License Manager in

Management Console User's Guide), choose “No” and click Next.

11 When the installation completes, to dismiss the installer, click Done.

Install log

The installer generates an install log that is written to the root of the installation directory if you installed BES from CD, or to the folder where the installer file resides if you used a downloaded file to install BES.

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

(32)

C h a p t e r 4 : I n s t a l l i n g B E S o n S o l a r i s a n d L i n u x 27 P r o d u c t d o c u m e n t a t i o n

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:

help

To recognize the help command, your path system variable must include the <install_dir>/bin directory, or you can enter the path explicitly.

From within the Borland Management Console, go to the Help menuFrom within the DDEditor, go to the Help menu

From within VisiBroker (Standalone) Console, go to the Help menu

Note Product documentation updates, HTML and PDF versions are available on the Web: http://www.borland.com/techpubs/bes.

Installing a standalone Management Console

BES 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:

1 On the Choose Product Components panel, select only the Management Console.

2 On the Choose Install Type panel, choose Custom.

3 When the Configuration Settings screen appears, specify the same Management port as those specified for the server(s) you want the Management Console to support.

4 Complete the installation as described in the “Borland Enterprise Server AppServer Edition” on page 24 section.

Installing more than one BES instance

If you install more than one instance of BES on the same machine:

Each server must have completely different install paths; the install directories at the

top level must be different.

You must modify Management ports with unique port ID numbers to make sure

container services are included with each server.

Keep the defaults on one server, but change the defaults for all other servers so that

they have unique port ID numbers.

Note We recommend you use the Management Console to change port ID numbers. To change Management port numbers:

1 Open the Borland Management Console.

2 Right-click on the Agent whose ports you want to change and select Properties.

(33)

R u n n i n g t h e i n s t a l l e r w i t h o u t a G U I

To change Web container port IDs:

1 Open the Borland Management Console.

2 In the navigation tree, expand the Partition whose web container you want to change.

3 Right-click the web container node and select Properties. The Properties tab Service: HTTP/ node displays the connector attributes.

4 To edit port ID properties, enter the values into the table.

For information about updating the Borland web container server.xml, go to the BES

Developer's Guide Web components section.

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.

To run the installer in text-only mode:

1 Change directories to the folder where the installation executable file is.

2 Type the appropriate command:

Solaris CD

install_solaris install -i console

Solaris downloaded file

<install_file>.bin install -i console

Linux CD

install_linux install -i console

Linux downloaded file

<path to JRE>/java -cp <install_file>.jar -i console

The installer will write to stdout and read from stdin. This allows you to telnet from one system to another and run the installer remotely.

Configuring VisiBroker for C++ server, VisiTransact, or VisiNotify

license variables

Before running VisiBroker C++ server, VisiTransact, or VisiNotify, you need to set two license environment variables (BES_LIC_DIR and BES_LIC_DEFAULT_DIR). During

installation, a shell script is created for you to use for setting these environment variables.

To set the variables:

1 Open a command window.

2 Change directory to <install dir>/bin.

3 Determine the appropriate script for your shell.

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

References

Related documents

The wizard and console-based installation program also creates a .properties file for subsequent installations and configurations using the unattended or silent method with the

For example, if your spouse and child were covered for medical and dental coverage only, through your spouse’s employer, and your spouse terminated employment (therefore

The BES is an application that is used to create and correct one- time adjustments and permanent budget requests. The BES creates a Budget Journal Entry where budget

Although presented as the remedy for economic problems and unemployment since the 1990s, the diffusion of new forms of flexible and temporary work contracts has transformed

Using the writings of some of the foremost anti-colonial national liberation theorists and activists of Antilles and African origin this article seeks to demonstrate

injection resisted alveolar epithelial cell apoptosis, 46,47 whereas those exposed to 50 U/kg BLM via endotracheal instillation showed pronounced apoptosis of alveolar macrophages

Course Learning Objectives Matrix Course Learning Objectives Course Assessment Methods* Extent of Coverage of Program Outcomes** (ABET Criterion 3)1. Upon successful