This document describes procedures for installing either BES or Borland Deployment Op-Center (BDOC) on SuSE Linux x86 (32 bit) operating systems.
Important: For documentation updates, go to http://www.borland.com/techpubs.
Notes:
Before installing on SuSE Linux you should:
Before installing BES/BDOC on SuSE Linux check the platform, system, and JDK requirements. For the latest platform information and system requirements see the BES Installation Guide or BDOC Installation Guide or go to
BES:
http://www.borland.com/techpubs/bes/platforms.BDOC:
http://www.borland.com/techpubs/opcenter/platforms.The installation package includes a bundled version of the Java Development Kit (JDK).
Important: Make sure to put the JRE 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/BDOC from the CD or download the software from the Borland web site:
BES:
http://www.borland.com/products/downloads/download_bes.htmlBDOC:
http://www.borland.com/products/downloads/download_opcenter.html.Before you install BES/BDOC, select the installation method:
To install BES/BDOC from a CD:
$ /cdrom/install_linuxwhere
/cdrom is the directory where CD-ROM is mounted.
Important: Make sure the Mozilla /usr/bin is in your path in order to use the default browser.
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.
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.
If installing from the web:
.tar file from the Borland website and untar it.
BES:
BES_65_SUSE_32_Web.tar
BDOC:
OPCENTER_65_SUSE_32_Web.tar
.bin file:
chmod 777 <file_name>.bin
BES:
BES_65_SUSE_32.bin
BDOC:
OPCENTER_65_SUSE_32.bin
For most options, defaults offered by the installation wizard are acceptable. You can use the Previous button to return to earlier screens and change any information that is incorrect.
Important: Once you select which product you are installing and click Next, to select a different product, you must cancel the current installation and restart the installation process.
BES AppServer Edition with Tibco. Installs the entire Borland Enterprise Server, which includes VisiBroker core functionality, plus support for integrated management of Java Messaging Services (JMS) through Tibco.
BES AppServer Edition with SonicMQ. Installs the entire Borland Enterprise Server, which includes VisiBroker core functionality, plus support for integrated management of JMS through SonicMQ.
BES AppServer Edition with OpenJMS. Installs the entire Borland Enterprise Server, which includes VisiBroker core functionality, plus support for integrated management of JMS through OpenJMS.
BES VisiBroker Edition. Installs the VisiBroker Java and C++ Core, development and management tools, and optional VisiBroker Extended Services.
BES:
This creates a new installation of BES, or adds components to an existing 6.5 installation.
BDOC:
This creates a new installation of BDOC or upgrades an existing BES installation. To create a new installation, either accept the default (/opt/Borland/BDP) or choose another location.
Important: You cannot install this version of BES/BDOC 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:
Borland Enterprise Server AppServer Edition
Management Console. GUI and tools for managing services and Partitions. For information about installing only the Management Console, go to Installing a standalone Borland Management Console.
Server. All server components, such as the Partition, Apache Web server, JDataStore, and VisiBroker.
Client. Components for client applications (EJB client and CORBA client).
Documentation. Suite of online documentation.
Examples. Example applications for Borland Enterprise Server.
Borland Enterprise Server VisiBroker Edition
VisiBroker Console. GUI and tools for managing VisiBroker ORB and services.
VisiBroker Core. VisiBroker for Java and C++ development tools and server components.
Documentation. Suite of online documentation.
Examples. Example applications for Borland Enterprise Server.
VisiBroker Extended Services. Optional components you purchase for extended VisiBroker functionality.
VisiBroker Op-Center Management Pack. Adds features for managing VisiBroker through Borland Deployment Op-Center.
VisiBroker Web Services Pack (VisiExchange). Web services support, Apache web server, Borland web container, IIOP connector, redirector, JDataStore, and support for JDBC datasources.
BDOC
Select from the following product components:
Management Console. GUI and tools for managing BDOC Configurations. For information about installing only the Management Console, go to Installing a standalone Borland Management Console.
Documentation. Suite of online documentation.
Op-Center Server Components. All required BDOC server-side components including the Management Hub and Management Agent.
VisiNotify. An industrial strength, ORB-level implementation of the OMG Event/Notification Service.
VisiSecure. A framework for establishing secure connections between clients and servers.
VisiTime. A complete implementation of the OMG Time Service Specification, Version 1.1.
VisiTransact. A complete implementation of the OMG transaction management solution for transactions with CORBA applications over the Internet or intranets.
VisiTelcoLog. An OMG compliant implementation of the OMG Telecom Log Service specification version 1.1.2
In addition, the typical installation includes the following defaults:
osagent. This port is used by the ORB to communicate with the server. You can use the Management Console to
change the Smart Agent port after installation is completed. The default is 14000.
42424.
osagent) port
should have a unique name. The default is the host name.
Note: The value(s) you enter for the port(s) must be valid for the installation to proceed.
BES_LIC_DIR to <install_dir>/var and BES_LIC_DEFAULT_DIR to <install_dir>/license.
Important: There should only be one Hub per Management Domain (port). For specific information on installing more than one Borland Enterprise Server on the same machine go to the Installing more than one BES instance section in the BES Installation Guide.
<install_dir>/license directory. If you did not receive a license activation key file, or if you are reinstalling the software, go to http://www.borland.com/products/downloads and download a new license key.
Important: You must register and activate your
license in order to use the product. If you have a valid, node-locked license for
BES/BDOC 6.0 on the same machine where you installed BES/BDOC 6.5, use the lmadm command-line tool to migrate your 6.0 license for use with the newly-installed BES/BDOC 6.5 software (see Migrating an existing 6.0 license).
Note: If you want to register and activate your license
later, either by running the lmadm executable found in the
<install_dir>/bin directory or by launching the wizard from the
Tools menu in the Management Console (see the Management Console User's Guide), choose
"No" and click Next.
The installer generates an install log that is written to the root of the installation directory if you installed BES/BDOC from CD, or to the folder where the installer file resides if you used a downloaded file to install BES/BDOC.
The BES AppServer install log file is:
<install_dir>/BES_AppServer_Edition_InstallLog.xml
The BES VisiBroker install log file is:
<install_dir>/BES_VisiBroker_Edition_InstallLog.xml
The BDOC install log file is:
<install_dir>/Borland_Deployment_Op-Center_InstallLog.xml
The file is an XML formatted log with installation-specific information, such as errors.
BES/BDOC includes a graphical user interface, called the Management Console, which acts as the focal point for managing Agents and applications on your network.
The server typically runs on a large shared UNIX or Windows machine, while the Management Console runs on any machine from which users want to view or modify the distributed system. Once the Management Console is installed, you can deploy to any server on your network.
To install a standalone Management Console:
If you install more than one instance of BES on the same machine:
Note: We recommend you use the Management Console to change port ID numbers.
To change Management port numbers:
To change Web container port IDs:
For information about updating the Borland web container server.xml, go
to the BES Developer's Guide.
The installer is capable of running in a text only mode 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.setuser tool to manage ownership
Note: The setuser tool replaces the functionality
provided by the iaschangeowner script included in previous releases.
The setuser tool manages ownership of BES/BDOC components installed on UNIX hosts.
The tool manages all aspects of ownership for these components, which includes:
For example, if you install the software as usernameA but usernameB is the intended user, you can use setuser with the +o option to change ownership of the appropriate components so usernameB can start the SCU process (Agent) as intended.
For example, if you have Payroll, Legal, and Human Resources departmental applications
configured as separate MOs under the same Agent, you can use setuser with the
+m option to grant execution permissions for each application to mutually exclusive owners without exposing other BES/BDOC privileges to either owner. While BES/BDOC is running in MUM, each user has access to only the MOs they have permission to use.
The setuser tool implements defense mechanisms to secure these components by
configuring the file system with appropriately restrictive ownership and access permissions.
Important: This tool must be run by a superuser, and all BES/BDOC processes must be stopped before running the tool. The superuser's current GID should be configured to be the same as the GID that was initially used to configure the MUM. The SCU process will fail to start if you invoke it as root but with a GID that is different than the one used to configure the MUM.
The setuser tool is in your BES/BDOC installation's /etc/utils/ directory. Its usage is as follows:
setuser [-r <install-dir>] [-u <new-user>] [-g <new-group>] [+o|+m] [-h]
where
<install-dir> is the root directory of the installation where the ownership changes are made. If not specified, the setuser tool's own installation location is used.
<new-user> is the new username for the installation (and, if enabling MUM, the default username that MOs started by the Agent run under).
<new-group> is the new groupname for the installation (and, if enabling MUM, the default group name that MOs started by the Agent run under).
+o changes the owner ID of the Agent and other BES/BDOC components to
<new-user> and <new-group>.
+m changes the owner ID of the Agent and other BES/BDOC components to <new-user> and <new-group> while simultaneously
enabling the application to run in MUM, allowing each MO started by the Agent to retain its configured ownership.
-h displays usage information for the setuser tool.
The +o and +m options are mutually exclusive: either use +o to configure the installation to simply execute BES/BDOC components under a different owner, or use +m to enable MUM.
The -u and -g options are optional.
/Borland/BDP to usernameB:
setuser -r /Borland/BDP -u usernameB -g admins +o
setuser +m
setuser +o
Note: Subsequently running setuser with the +o option to change ownership after using the +m option disables MUM. To enable MUM and change ownership of the installation at the same time, use the +m option only (see Enabling multi-user mode).
When you need to change the ID an installation's Agent runs under, use the setuser tool with the +o option. The tool changes the owner ID and reconfigures the necessary file ownerships (log files, property files, configuration files, and so forth). For example:
setuser -r /borland/myBES/ -u usernameC -g admins +oor
setuser -r /borland/myBDOC/ -u usernameC -g admins +o
changes the user and group under which the BES/BDOC installation found in /borland/myBDOC or /borland/myBES executes to usernameC and admins, respectively. The +o option tells the tool that the new user and group name will be used as the new owner ID of BES/BDOC.
To change ownership of the installation and its supporting files:
setuser tool with the +o option, specifying the username and groupname of a new owner. For example:
setuser -r /borland/myBES/ -u usernameC -g admins +oor
setuser -r /borland/myBDOC/ -u usernameC -g admins +o
Important: If you are configuring a remote script or application to run under MUM, the MO user you specify in the Configuration must have appropriate permissions on the remote filesystem to load and execute the script or application. For security, other users should not have access to the remote script or application's filesystem.
Note: If you add or modify configurations under an Agent that
is already running in MUM, you need to rerun setuser with the +m
option to enable the new or modified Configurations to run in MUM.
Multi-user mode configures BES/BDOC to securely support running MOs under multiple, differing user IDs. Enabling MUM is in many ways a special case of changing the user ID under which the Agent executes.
When MUM is enabled for an Agent, the SCU process for the Agent must be started by root. After the SCU process starts, the running process is owned by the specified Agent owner, while the processes for each MO are owned by the configured user for the MOs or applications. If a Configuration does not specify values for Start As User or Start As Group, the MO's processes are owned by the Agent's owner.
To enable MUM:
setuser with the +m option, specifying the new owner ID (or omit the -u and -g flags to keep the existing owner ID). For example:
setuser -r /borland/myBES/ -u usernameC -g admins +mor
setuser -r /borland/myBDOC/ -u usernameC -g admins +m
agent.config (see Enabling Managed Objects to start as root).agent.config (see Enabling JavaScript support when starting Managed Objects as root).The SCU process starts under root ownership but after starting, the process is owned by the existing owner of the BES/BDOC installation, or by the new owner ID specified by the -u and -g options. Each MO's processes are owned by the owners specified in their Configurations. If a Configuration does not specify values for Start As User or Start As Group, the MO's processes are owned by the Agent's owner.
Important: Enabling an MO to start as root might expose elevated privileges to unintended users, and should only be implemented for MOs that must be started as root to provide required functionality (for example, enabling Apache to allow privileged port access). To prevent accidental or malicious deployment of a root-started MO that might compromise system security, before enabling an MO to start as root, perform a security audit on the MO's executables and secure access to the system where the MO resides.
Tip:
To isolate potential security exposures and simplify administration efforts,
put all root-started MOs under one Agent and update its agent.config file to allow
the MOs to start as root. Place all other MOs under a different Agent and leave its agent.config file unchanged to retain the default BES/BDOC behavior to disallow starting MOs as root.
Typically, to protect against unauthorized access to MOs, the Agent is prevented from starting
an MO as root user. In rare cases, an MO might need to be started by root to function as intended.
To override builtin protection against root-started MOs after enabling BES/BDOC to run in MUM, you need to modify agent.config to allow MOs to be started by root.
After the MO starts under root ownership, its process ownership is defined and configured by the MO or application (for example, the Apache owner specified in the httpd.conf file), not by BES/BDOC.
To enable MOs to be started by a root user:
agent.mum.enable.root.mo property in agent.config (found in <install_dir>/var/domains/base/adm/properties) as follows:
agent.mum.enable.root.mo=true
Important: Enabling JavaScript execution for an MO started by an Agent configured for MUM might expose your system to malicious code that can run with elevated privileges. When enabling JavaScript execution for such an MO, ensure that the JavaScript has been security audited and is protected from unauthorized user access.
JavaScript execution is typically not allowed when an MO is started by an Agent configured for MUM. If any of the MOs that will run in MUM contain JavaScripts, you need to modify agent.config to allow those JavaScripts to run.
To enable JavaScript execution when MUM is enabled:
agent.mum.enable.jscript property in agent.config (found in <install_dir>/var/domains/base/adm/properties) as follows:
agent.mum.enable.jscript=true
To disable MUM:
setuser with the +o option. For example:
setuser -r /borland/myBES/ +oor
setuser -r /borland/myBDOC/ +o
agent.mum.enable.root.mo property in agent.config to false (see Setting Managed Objects to start as root).agent.mum.enable.jscript property in agent.config to false (see Enabling JavaScript support when starting Managed Objects while in MUM).
The SCU process will start and run as the existing BES/BDOC owner ID (or the new owner ID specified by the -u and -g options). Any unique user ID information configured for individual MOs will be ignored, and the MOs are run under the Agent's owner ID.
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/BDOC product directory of your choice. For SuSE Linux, the default installation directory is /opt/Borland/BDP. |
| OSAGENT_PORT | (optional). Default is 14000. |
| SERVER_NAME | <server_name> (optional). A server name of your choice. Default is host name. |
| MANAGEMENT_PORT | (optional). Sets the Management Port. Default is 42424. |
| USER_SHORTCUTS | The required value is /dev/null. |
| INSTALL_DOCS | (optional). Installs the suite of online documentation. Default is YES. |
| INSTALL_EXAMPLES | (optional). Installs the example applications for Borland Enterprise Server. Default is YES. |
| INSTALL_TYPE | BES: Choose only one of the following(required):
BDOC:
|
| JMS_TYPE | BES only. Choose only one of the following (required only if INSTALL_TYPE=AppServer):
|
| JVM_JDK_HOME | (optional). Sets the JDK path for BES components that host user application code. The default is set to the location where the JDK included with BES is installed. |
| INSTALL_CONSOLE | (optional, applies to AppServer Edition only). Installs the Management Console. Default is YES. |
| INSTALL_SERVER | (optional, applies to AppServer Edition only). Installs all the server components, such as the Partition, Apache Web server, JDataStore, and VisiBroker. Default is YES.
|
| INSTALL_CLIENT | (optional, applies to AppServer Edition only). Installs all the components for client applications (EJB client and CORBA client). Default is YES. |
| INSTALL_VBCONSOLE | (optional, applies to VisiBroker Edition only). Installs the GUI and tools for managing VisiBroker ORB and services. Default is YES. |
| INSTALL_VISICORE | (optional, applies to VisiBroker Edition only). Installs the VisiBroker for Java and C++ development tools and server components. Default is YES. |
| INSTALL_VISIMGT | (optional, applies to VisiBroker Edition only). Adds features for managing VisiBroker through Borland Deployment Op-Center. Default is YES. |
| INSTALL_VISIWEB | (optional, applies to VisiBroker Edition only). Installs web services support, Apache web server, Borland web container, IIOP connector, redirector, JDataStore, and support for JDBC datasources. Default is YES. |
| VISI_SERVICES | (optional, applies to VisiBroker Edition only). When INSTALL_TYPE is VisiBroker, installs any optional VisiBroker Extended Services you purchased. The value is a comma-delimited list that contains one or more of the following entries:
For example, if you purchased BES VisiBroker Edition with VisiNotify and VisiTransact, include the following line in your silent installation For a description of each optional Extended Service, see the Choose VisiBroker Extended Services section in BES Installation Guide. |
| CONFIGURATION_SETUP | (optional). Installs the BES example configuration. Default is YES. |
| BDOC_TYPE | BDOC only. Choose only one of the following (required):
|
| INSTALL_BDOC | BDOC only. (optional). All required Op-Center server-side components including the Management Hub and Management Agent. The default is YES. |
This example installs BES VisiBroker Edition on non-default management and agent ports, and installs several VisiBroker Extended Services.
INSTALLER_UI=silent USER_INSTALL_DIR=/opt/Borland/BDP USER_SHORTCUTS=/dev/null OSAGENT_PORT=14925 INSTALL_TYPE=VisiBroker VISI_SERVICES=VisiNotify,VisiSecure,VisiTime,VisiTransact,VisiTelcoLog MANAGEMENT_PORT=42925
This example installs a BDOC master Hub on a non-default management port and does not install the sample Configuration.
INSTALLER_UI=silent USER_INSTALL_DIR=/opt/Borland/BDOC INSTALL_TYPE=Op-Center BDOC_TYPE=master-hub USER_SHORTCUTS=/dev/null MANAGEMENT_PORT=42925 CONFIGURATION_SETUP=NO
To invoke the silent installation process using the values specified in the properties file:
chmod all, where 777 indicates all, to run the installer.<propertiesfile> file:
BES:
BES_65_SUSE_32.bin install -f <path to properties file>
BDOC:
OPCENTER_65_SUSE_32.bin install -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 or by launching the wizard from the Tools menu in the Management Console (see the Management Console User's Guide).
Before using BES/BDOC, you need to register and activate the license you received for your product. The license may be in the form of an email from Borland listing one or more serial numbers and license keys, or it may be a license key file sent to you in an email from Borland.
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/BDOC 6.0 installed on the same machine
as the newly-installed BES/BDOC 6.5, use the lmadm command-line tool to migrate your 6.0 license for use with the newly-installed BES/BDOC 6.5 software (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/BDOC product using one of the following registration methods:
Depending on which method you choose, you may be asked to indicate whether you have a Borland Developer Network (BDN) account. If you do not have an account, you will be prompted to create one in the product registration wizard.
If you do not choose the Direct registration method, you will receive an activation file.
Simply copy this file into the <install_dir>/license directory and it
will be applied automatically when you start your product.
To migrate an existing 6.0 node-locked license after installing 6.5:
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/BDOC:
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.