This document describes procedures for installing either BES VisiBroker on IBM zSeries (s390 31 bit system and zSeries 64 bit system) SuSE Linux operating systems.
Important: For documentation updates, go to http://www.borland.com/techpubs.
Notes:
Before installing on IBM zSeries you should:
Before installing BES VisiBroker on IBM zSeries check the platform, system, and JDK requirements. For the latest platform information and system requirements see the BES Installation Guide or go to http://www.borland.com/techpubs/bes/platforms.
The installation package for IBM zSeries does not ship any version of the Java Development Kit (JDK). For information on Java products for IBM zSeries go to http://www.ibm.com/developerworks/java/jdk.
Important: Before installing on IBM zSeries, you must have an existing JDK (1.4.2 is supported) 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 java version "1.4.2"
You can install BES VisiBroker 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 VisiBroker, select the installation method:
To install BES VisiBroker from a CD:
If installing from a downloaded file:
.bin file by untarring the appropriate .tar file:
VBE_65_SUSE_S390_Web.tarVBE_65_SUSE_ZSERIES_Web.tarVBE_65_SUSE_S390.binVBE_65_SUSE_ZSERIES.binThis creates a new installation of BES, or adds components to an existing 6.5 installation.
Important: You cannot install this version of BES VisiBroker on top of previous releases.
Select from the following product components for each feature set:
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
In addition, the typical installation includes the following defaults:
osagent. This port is used by the ORB to communicate with the server. You can use the Management Console to change the Smart Agent port after installation is completed. The default is 14000.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.
BES_LIC_DIR to <install_dir>/var and BES_LIC_DEFAULT_DIR to <install_dir>/license.bin directory in PATH. The default is "No". To add the directory to your PATH, choose "Yes".
BES_LIC_DIR to
<install_dir>/var and BES_LIC_DEFAULT_DIR to
<install_dir>/license.
<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 VisiBroker 6.0 on the same machine where you installed BES VisiBroker 6.5, use the lmadm command-line tool to migrate your 6.0 license for use with the newly-installed BES VisiBroker 6.5 software (see Migrating an existing 6.0 license).
Note: If you want to register and activate your license
later, either by running the lmadm executable found in the
<install_dir>/bin directory.
The installer generates an install log that is written to the root of the installation directory if you installed BES VisiBroker from CD, or to the folder where the installer file resides if you used a downloaded file to install BES VisiBroker.
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.
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:
<install_file>.bin -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.Before invoking the silent installation process, you must first create a text file that contains the properties for configuration settings, such as install directory, server name and JDK home. Each property must be listed on its own line, terminated by a carriage return, with no blank spaces at the end of each line and no blank lines at the end of the file. See the Properties file for silent installation section for more information.
After creating the text properties file, save it as <propertiesfile>.txt, where <propertiesfile> is the filename prefix for your properties file. Now you can invoke the silent installation process using the values specified in the properties file(s).
Note: All properties and values are case-sensitive. When specifying directory and file paths, always use a forward slash.
The properties 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 BES VisiBroker product directory of your choice. For IBM zSeries, the default installation directory is /opt/Borland/BDP. |
| OSAGENT_PORT | (optional). Default is 14000. |
| USER_SHORTCUTS | The required value is /dev/null. |
| INSTALL_DOCS | (optional). Installs the suite of online documentation. Default is YES. |
| INSTALL_EXAMPLES | (optional). Installs the example applications for Borland Enterprise Server. Default is YES. |
| INSTALL_TYPE |
Choose the following(required):
VisiBroker — Installs Borland Enterprise Server, VisiBroker Edition. |
| JVM_JDK_HOME | (optional). Sets the JDK path for BES components that host user application code. The default is the location of the JDK which is in the PATH at the time the installer is run. |
| INSTALL_VISICORE | (optional). Installs the VisiBroker for Java and C++ development tools and server components. Default is YES. |
| INSTALL_VISIMGT | (required) Adds features for managing VisiBroker
through Borland Deployment Op-Center. Make sure to set it to NO.
Default is YES. |
| INSTALL_VISIWEB | (required) Installs web services support, Apache
web server, Borland web container, IIOP connector, redirector, JDataStore,
and support for JDBC datasources. Make sure to set it to NO.
Default is YES. |
| VISI_SERVICES | (optional). When INSTALL_TYPE is VisiBroker, installs any optional VisiBroker Extended Services you purchased. The value is a comma-delimited list that contains one or more of the following entries:
For example, if you purchased BES VisiBroker Edition with VisiNotify and VisiTransact, include the following line in your silent installation For a description of each optional Extended Service, see the Choose VisiBroker Extended Services section in BES Installation Guide. |
This example installs BES VisiBroker Edition on non-default agent ports, and installs several VisiBroker Extended Services.
INSTALLER_UI=silent USER_INSTALL_DIR=/opt/Borland/BDP USER_SHORTCUTS=/dev/null OSAGENT_PORT=14925 INSTALL_TYPE=VisiBroker VISI_SERVICES=VisiNotify,VisiSecure,VisiTime,VisiTransact,VisiTelcoLog INSTALL_VISIMGT=NO INSTALL_VISIWEB=NO
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:
VBE_65_SUSE_S390.bin -f <path to properties file>or
VBE_65_SUSE_ZSERIES.bin -f <path to properties file>where
<path to properties file> is the full path of the propertiesfile file.
Note: After silent installation is completed, you need to register and activate the license you received for your product. 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. If you want to register and activate your license by running the lmadmw executable found in the <install_dir>/bin directory.
Before using BES VisiBroker, 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.
Important: For information on how to license your product, go to http://info.borland.com/devsupport/bdpcommon/faq/6.5/licensing/index.html.
If you have a valid, node-locked license for BES VisiBroker 6.0 installed on the same machine
as the newly-installed BES VisiBroker 6.5, use the lmadm command-line tool to migrate your 6.0 license for use with the newly-installed BES VisiBroker 6.5 software (see Migrating an existing 6.0 license).
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 VisiBroker product using one of the following registration methods:
Depending on which method you choose, you may be asked to indicate whether you have a Borland Developer Network (BDN) account. If you do not have an account, you will be prompted to create one in the product registration wizard.
If you do not choose the Direct registration method, you will receive an activation file.
Simply copy this file into the <install_dir>/license directory and it
will be applied automatically when you start your product.
To migrate an existing 6.0 node-locked license after installing 6.5:
For information on how to migrate your existing 6.0 license after installing 6.5, go to the Borland website, http://info.borland.com/devsupport/bdpcommon/faq/6.5/licensing/index.html.To use the Borland product registration wizard for Direct registration:
To use the Borland product registration wizard for Email registration:
<install_dir>/license directory,
and it will be applied automatically when you start your product.To use the Borland product registration wizard for Web page registration:
<install_dir>/license directory,
and it will be applied automatically when you start your product.To use the Borland product registration wizard for Telephone registration:
<install_dir>/license directory, and it will be applied
automatically when you start your product.To uninstall BES VisiBroker:
osagent) running during the uninstall.<install_root>/UninstallerData directory.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.