This document describes procedures for installing visiBroker on Red Hat Enterprise Linux 3.0 operating system for MontaVista Linux CGE 4.0 cross platform development with supported target CPU architecture of x86_em64t.
You can install VisiBroker 7.0 from the CD or download VisiBroker from http://www.borland.com/downloads/download_visibroker.html
Note:
We recommend uninstalling any previous versions of VisiBroker, or installing the new version to a different location; on a different install path. If you have already installed an evaluation version and have since purchased a license to use VisiBroker on a permanent basis, you do not need to reinstall the version of the software you evaluated. For information on activating your new license, see Borland Product Registration Wizard.Before installing on Red Hat Enterprise Linux 3.0 you should:
Before installing VisiBroker on Red Hat Enterprise Linux 3.0, check the latest platform information and system requirements.
In addition to platform-specific requirements, Borland VisiBroker 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.
The installation package for Red Hat Enterprise Linux 3.0 does not ship any version of the Java Development Kit (JDK). You need a JDK with version 1.4.2 and above to run the installer (both CD image and web downloaded installer). Currently, both IBM and Sun provide JDK for 64-bit platforms. For information on platform support for JDK from Sun, go to Java Platform, Standard Edition. For information on Java products for IBM as well as the system requirements for installation of the JDK, go to http://www.ibm.com/developerworks/java/jdk.
Important: Before installing on Red Hat Linux, you must have an existing JDK installed. Make sure to put the JDK bin
directory into the path variable.
To check the location of your JDK and the version, use the following syntax:
$which java /opt/local/bin/java java version "1.5.0_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_06-b05, mixed mode)
The Borland VisiBroker CD includes installation software for the Red Hat Linux operating systems. This section describes how to prepare to install VisiBroker on Red Hat Enterprise Linux 3.0 from CD.
# mount -t iso9660 -o ro /dev/cdrom /cdromwhere
/cdrom
represents the mount point of the CD-ROM.If you are using auto-mounting software, the CD-ROM is mounted automatically to the directory specified in your auto-mount configuration when you insert it into the CD-ROM drive. You can proceed with instructions given in Installing Borland VisiBroker .
To check if you have auto-mounting software, use the following command:
$ ps aux | grep automountIf you have auto-mounting software, the output should be similar to the following:
root 628 0.0 0.2 1148 588 ? S 17:32 0:00 /usr/sbin/automount
Go to root and enter the following command:
umount /cdrom
(if you have manually mounted the CD-ROM)
eject cdrom
(if you have used auto-mounting software to mount the CD-ROM)
You can install VisiBroker from the CD or download the software from the Borland web site: http://www.borland.com/products/downloads/download_visibroker.html
Before you install VisiBroker, select the installation method:
install_linux
The installation wizard launches a separate window.
Previous
button to return to earlier screens and change any information that is incorrect.If installing from a downloaded file:
java -cp <installer file>-<release number>-CROSS-linux-montavista-x64.jar install
For console mode installation, use -i console option.
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.
Next
.This creates a new installation of VisiBroker, or adds components to an existing installation.
To create a new installation, either accept the default location or choose another location.Important: You cannot install this version of VisiBroker on top of previous releases.
Depending on the Borland Deployment Platform product you are installing, select from the following product components for each feature set:
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.
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
osagent
. This port is used by the ORB to communicate with the
server. You can choose any value between 5000 and 65535. The default is 14000
.
choose
button.Previous
button to revisit and
change any selections you made except your choice for which product to
install. To approve your choices and start installing, click the Install
button.
Done
.The installer generates an install log that is written to the root of the installation directory if you installed VisiBroker from CD, or to the folder where the installer file resides if you used a downloaded file to install VisiBroker.
The VisiBroker install log file is:
<install_dir>/Borland_VisiBroker_InstallLog.xml
The file is an XML formatted log with installation-specific information, such as errors.
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:
java -cp <install_file>.jar install -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.
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:
<install_dir>/bin
.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
.profile
, .cshrc
, or .login
file.After creating the text properties file, save it as <propertiesfile>.txt
, where <propertiesfile>
is the filename prefix for your properties file. Now you can invoke the silent installation process using the values specified in the properties file(s).
Note: All properties and values are case-sensitive. When specifying directory and file paths, always use a forward slash.
The properties file is a plain text file, with each property listed on its own line, terminated by a carriage return, with no blank spaces at the end of each line and no blank lines at the end of the file. The properties can appear in any order in the file.
Properties File Contents for Silent Installation
Variable | Value |
---|---|
INSTALLER_UI | silent (required). The mode of installation. |
USER_INSTALL_DIR | <install_dir> (required). The full path name for the VisiBroker.
The default installation directory is /opt/Borland/VisiBroker. |
OSAGENT_PORT | (optional). Default is 14000 . |
USER_SHORTCUTS | The required value is /dev/null . |
INSTALL_DOCS | Installs the suite of online documentation. Default is YES . |
INSTALL_EXAMPLES | Installs the example applications for VisiBroker. Default is YES . |
INSTALL_TYPE | (Required) VisiBroker Installs VisiBroker |
JVM_JDK_HOME | (optional). Sets the JDK path for VisiBroker components that host user application code. The default is set to the location where the JDK included with VisiBroker is installed. |
INSTALL_VBCONSOLE | Installs the GUI and tools for managing VisiBroker ORB and services. Default is YES . |
INSTALL_VISICORE | Installs the VisiBroker for Java and C++ development tools and server components. Default is YES . |
VISI_SERVICES | When INSTALL_TYPE is VisiBroker , installs any optional VisiBroker Extended Services you purchased. The value is a comma-delimited list that contains one or more of the following entries:
For example, if you purchased VisiBroker Edition with VisiNotify and VisiTransact, include the following line in your silent installation For a description of each optional Extended Service, see the Choose VisiBroker Extended Services section in VisiBroker Installation Guide. |
CONFIGURATION_SETUP | Installs the VisiBroker example configuration. Default is YES . |
VISICORE_FEATURES | {Java|.NET} This will determine whether you get Visi for Java/C++, Visi for .NET, or both Default is Visi for Java/C++. This is ignored if you specified INSTALL_VISICORE=NO |
This example installs VisiBroker on non-default agent port, and installs several VisiBroker Extended Services.
INSTALLER_UI=silent USER_INSTALL_DIR=/opt/Borland/VisiBroker USER_SHORTCUTS=/dev/null OSAGENT_PORT=14925 INSTALL_TYPE=VisiBroker VISI_SERVICES=VisiNotify,VisiSecure,VisiTime,VisiTransact,VisiTelcoLog
To invoke the silent installation process using the values specified in the properties file:
tar
file you downloaded.chmod
all, where 777
indicates all, to run the installer.<propertiesfile>
file:
java -cp <installer file>.jar install -f <path to properties file>or where
<path to properties file>
is the full path of the propertiesfile
file.
To uninstall VisiBroker:
osagent
) running during the uninstall.<install_root>/UninstallerData
directory.java -cp uninstaller.jar uninstall
uninstall
command:
uninstall
Note: This does not remove files and folders that were created after the installation.
uninstall
command, check the installation directory and
remove any unnecessary files and subdirectories.