The Borland Enterprise Server is available in the following four "Editions":
The most basic is the Web Edition; the most versatile is the AppServer Edition. If desired, you can upgrade from one Edition to another. This release note is applicable to all of these Editions.
Note: For additional information specific to the VisiBroker Edition and VisiBroker standalone, see the release notes appropriate to your platfor in http://techpubs.borland.com/am/bes/v5x/
This section contains important information concerning the following areas:
Important: When selecting or creating an installation directory path for Borland Enterprise Server, please ensure that this path uses only ASCII characters. Due to a limitation in the SonicMQ installer, when multi-byte characters are used in the installation directory path, installation may fail.
For information on how to install Borland Enterprise Server, please refer to the Installation Guide. If you are upgrading, see Upgrading from previous versions.
The following table describes the two "install types":
| Install Type | Description |
|---|---|
| Borland Enterprise Server Complete | Installs a BES server and all components required to run any Edition. |
| Borland VisiBroker Standalone | Installs a self-contained VisiBroker installation - just the VisiBroker ORB or VisiBroker Management Console without any J2EE components. |
Note: The Borland VisiBroker Standalone installation is not to be confused with BES VisiBroker Edition. The former is an install type, the latter licensing purchased for BES. Both install types are available with all BES Editions.
Important: If you have a previous installation of Borland AppServer or Borland Enterprise Server installed, do not install on top it. Remove the previous version or install Borland Enterprise Server in a separate directory.
Before installing, ensure that you have read and complied with the all platform requirements, including J2SE. See the Platform information section for detailed requirements.
Borland Enterprise Server licensing technology governs the level of features available. You can upgrade your license at any time. For example, you can upgrade from one Edition to another, from an evaluation to development license, or to a runtime license. You can manage your server's license using the BES Management Console.
A fully licensed installation on UNIX may emit the following licensing error message when using tools like idl2cpp or VBJ.
There is no valid license to run this product or component. Please make sure that a license enabling this product or component is installed correctly and it has not yet expired.
These tools require access to appropriate environment variables. Prior to running
these tools, use the vbroker.csh (for C-Shell) or vbroker.sh
(for Bourne and KornShell), bash scripts in the installation's /bin
directory to set up the appropriate environment variables. Building the
examples requires invoking a number of these tools; if you wish to
compile the examples on UNIX or Linux, you must invoke the setup
scripts first. This behavior is as designed.
When an appropriate license is presented to the Borland Enterprise Server, client license Serial Numbers and Activation Keys are generated automatically. You can find the Serial Number and Activation Key in the file:
<install_dir>/var/servers/<server_name>/adm/client.license
To run the Borland Enterprise Server, navigate to its /bin subdirectory
and type ias. In Windows, choose Start|Programs|Borland Enterprise
Server. Refer to the Borland Enterprise Server User's Guide in the online Help Topics for more detailed information.
To use the Java-based Management Console, navigate to your installation's /bin directory and type Console.
The Management Console allows you to browse, control, and configure the
server, as well as deploy applications to it. In Windows, choose Start|Programs|Borland Enterprise Server|Management Console. Refer to the Borland Enterprise Server User's Guide in the online Help Topics for more detailed information.
When the Management Console starts, a Login dialog appears. All servers are installed
with a default user named admin. The password for this user is admin as well.
By default, security is disabled for the user domain on Partitions in the Borland Enterprise Server. To enable security on a Partition:
Note: BES 5.2.1 is a maintenance release. For information describing features that were new to BES 5.2, please see: BES 5.2 Release Notes.
This feature now also supports EARs.
CMP_Update and CMP_Query only measured the CMP 1.x engine.ejb.cmp.checkExistenceBeforeCreate
to the CMP 2.x engine. The default is different from CMP 1.x; by
default the CMP 2.x PM does not defensively check for existence of the
primary key before the insert is tried. Refer to the BES Developer's Guide in the online Help Topics for details.The Apache web server component has been upgraded to version 2.0.45 on all platforms, except for HP-UX. This version remains at 2.0.43. This platform has been patched to address all known security issues fixed in Apache 2.0.45, particularly CAN-2003-0132.
OpenSSL has been upgraded to 9.6i. All known security issues, including the Klima-Pokorny-Rosa attack vulnerability and the blinding attack vulnerability are fixed.
The following fixes were made in 5.2.1 in response to reported problems in previous releases. Each fix is preceded by its bug number.
33714: homogeneous naming service clustering fails with java.lang.ArrayIndexOutOfBoundsException
35072: Thread connection issue in IIOP-connector
36619: Hosting an exploded EAR, the EJB JARs, client JARs, RARs, and DARs will
be deleted when the Partition is stopped.
37093: Memory leak in iis_redirector
37107: ArrayIndexOutOfBoundsException in CMP 2.0 persistence manager
37141: EJB CMP 2.0 Relationship with more than 100 rows cause a NullPointerException
37165: Same Tx Branch Qualifier used in Xid for xa_start()s in different connections
37194: EJB CMP and BMP cannot be colocated in the same jar file
37227: When user logs off of the console the SonicMQ Broker shuts down
37279: Parsing error for EJB-QL statement with subquery
37291: WinInet errors (12029) is IIS redirector
37301: EJB CMP bad cascade delete false behavior
37410: ssl.conf ships with directives not supported by the Apache server
37495: Class cast exception getting connection from deployed RAR
37556: Servlet cannot access a request's Socket object in a custom valve
37750: Deploy/redeploy of large EAR modules causes OutOfMemory error
37760: EJB 1.1 apps with old stubs will not deploy, because the old stubs were
not fully stripped when using Deployment Wizard.
37868: Cannot deploy RAR which does not conform to Connectors 1.0 conventions.
37973: Optimistic Concurrency Control generates incorrect SQL
38129: null values return from fields of finder method beans
The following are additional issues you may encounter when migrating earlier versions of BES to BES 5.2.1.
Note: BES 5.2.1 is a maintenance release. For information describing issues you may encounter when migrating from earlier versions of BES to BES 5.2, please see: BES 5.2 Release Notes.
20 (from 100). This is motivated by benchmark studies of EJB applications.Depending on system resource usage, the NFILE parameter may be too small to support the number of open files the installation requires. We recommend a value of at least 3000. Please see the HP-UX system documentation for information about configuring and rebuilding the HP-UX kernel.
Although AIX is not certified to run applications on JDK 1.4, JDK 1.4 is still required to support a full BES installation, as it is used for internal tooling.
In the case of a VisiBroker standalone installation, no tooling is installed that requires JDK 1.4, but the installer still requires the user to enter a path to JDK 1.4. As a workaround for the VisiBroker standalone install on AIX only, it is permissible to enter the path to JDK 1.3.1 in place of JDK 1.4.
There is a known issue in SonicMQ where the Sonic installer does not support installation to a directory path using multi-byte characters in its name. To ensure a successful installation, the directory path used for installation must use only ASCII characters.
There is a known issue in the Linux C libraries affecting Java applications which call System.exit(x). This is the recommended practice for GUI applications. iastool and Console both use this method to exit the VM. This problem is resolved in a later version of the C libraries. Please see http://java.sun.com/j2se/1.4.1/relnotes.html for more information. The suggested workaround is to edit the makefile
to ignore the failing command. Since the necessary work has been
accomplished by the time the tool exits, this is not a serious problem.
When running the Management Console, DDEditor, or other GUIs under JDK 1.4 (the default JDK for all tools in BES 5.2) on Windows systems using ATI Radeon video drivers, exiting the GUI can sometimes result in the "blue screen of death". On these systems, please add the following parameters:
vmparam -Dsun.java2d.ddoffscreen=false vmparam -Dsun.java2d.noddraw vmparam -Dsun.java2d.d3d=false vmparam -Dsun.java2d.ddoffscreen=false
to the following files, all in <install_dir>/bin :
jdk.config ddeditor.config vbconsole.config beshelp.config jdsserver.config jdsexplorer.config sonicmqexplorer.config
When running the BES Server on Linux, the Management Console and
iastool are sometimes unable to discover that server when run from a
different system. This is because the default Linux hosts file has only the loopback entry (127.0.0.1). In order to correct this, you must add an entry for the local host. For example, on a machine named mylinux that is called mylinux.work.mydomain.com at 172.1.1.1, the following must be added to the hosts file and must be the first entry in that file:
172.1.1.1 mylinux.work.mydomain.com mylinux
mod_iiop cannot run seteuid/setegid on HP-UX
The HP-UX dynamic loader dld.sl does not respect the LD_PRELOAD
environment variable for seteuid/setegid
programs. This is a documented behavior. This affects the Borland
Enterprise Server's ability to start and/or control an instance of the
Apache web server running on a privileged port and using mod_iiop. Please see the UNIX FAQ for detailed information about configuring the Apache web server to listen on privileged ports on HP-UX.
To compile and run the Web Services examples on HP-UX, use the supported HP-UX 1.4 JDK, rather than the HP-UX 1.3 JDK.
Starting BES and then logging off the system causes Apache to hang
on Windows 2000. This appears to be a problem only when using mod_iiop.
Stateful Session EJB passivation sometimes causes reactivated beans to use a different ClassLoader than expected. The workaround is to disable SFSB passivation.
AIX may fail with OutOfMemoryError
ias may run out of memory when cloning a partition on AIX. The workaround is to increase the default max heap size from 32 megs to 64 megs (or an appropriate upper value) in <install_dir>/var/servers/<server_name>/adm/properties/server.config:
vmparam -Xmx64m
In order to use BES 5.2.1 as the application server in a JBuilder8 project, a patch must be applied to JBuilder8. The patch (jb8_bes_001.jar) can be found:
<cd_root>/JBuilder<install_dir>/etc.In both folders, the JAR is accompanied by a readme.html file that explains how to install the patch.
The patch causes JBuilder8 to use required libraries from the BES installation (<besinstall_dir>/lib)
rather then from the JBuilder8 installation
(<jb8install_dir>/lib/bes) for deployment and stub generation
functions. It does not cause JBuilder8 to use the
DDEditor from the BES installation. With or without the patch, the
DDEditor function that appears in JBuilder8 is the 5.1.1 DDEditor.
Note: With the patch installed, JB8 will support BES 5.1, 5.1.1, 5.2 and 5.2.1. If you need to use JB8 with BES 5.0.2, do not apply the patch.
When deploying/debugging a project using JBuilder and BES, JBuilder will create its own Partition (named "JBuilder") in the BES server. This Partition is configured using a default configuration that is identical to that used in the Standard Partition. If these Partitions are running at the same time, port conflicts will occur.
Before using JBuilder, do the following:
Such port conflicts can also occur with other Partitions that have been created with the default parameters.
When using the Start using Server or Debug using Server commands, JBuilder8 will:
This can be quite slow. In the majority of cases, you can avoid this behavior by using the Deploy options for <archivename>
command (right-click archive in JBuilder), and selecting the Redeploy
command. This will cause a hot deploy to occur, which will not stop the
Partition. It does launch another tracker window at the bottom of
JBuilder. Once the redeploy is complete, you can close this window.
When opening any ejb example in JB9 (any example in <bes install dir>/examples/ejb/<example name>/jb/<example>.jpx, if obsolete libraries are not removed, opening the EJB Designer will result in a warning message. Projects otherwise build and run ok.
To remove the obsolete library:
The README.HTML files in the ejb and PetStore examples were not updated for BES 5.2.1/JBuilder 9. The following corrections should have been made:
onMessage() method can cause infinite redeliveries of the same JMS message
Currently there is no way to limit the number of retries.
There is a known issue with the use of the resource vault file in VisiConnect. If an attempt to use run-as roles with a RAR in VisiConnect is made without providing a resource vault, VisiConnect will need to be cycled before being able to read in a subsequently provided resource vault using the same Security Context (username/password or credential). It is highly recommended you deploy the required resource vault file(s) for VisiConnect prior to executing deployed Resource Adapters with dependencies on that file(s).
The BES Management Console provides a configuration dialog for the
SonicMQ service. In this dialog, you may configure the Admin Broker
port (on the Settings tab). This setting changes only the port that the
BES service manager will use to communicate to SonicMQ. After changing
this, you must also configure the SonicMQ server's port either by
editing the <install_dir>/SonicMQ/broker.ini file, or by using the SonicMQ explorer available in the BES Management Console | Tools menu.
openssl cannot generate certificates and keys on some platforms
The openssl utility cannot generate certificates and
keys on some platforms including AIX and Solaris 8. The workaround is
to use an earlier version of openssl or to simply use your current certificates and keys.
When running the standalone online Help Topics Browser in a Japanese locale environment, the topics and content display only in English, and not Japanese. This is due to a limitation in the beshelp environment. When the online Help Topics Browser is launched from the Management Console in a Japanese locale environment, the topics and content are displayed in Japanese. As a workaround, launch the Help Topics from the Management Console Help pulldown menu.
The PetStore Tutorial, VisiBroker VisiTransact Guide, and How To Use Help books are available only in English. They are not available in Japanese for 5.2.1.
To upgrade from Borland Enterprise Server 5.x, 5.0.x, or 5.1.x do not install on top of the previous installation. Install in a separate directory or uninstall your previous version first. You may then redeploy your applications to Borland Enterprise Server 5.2.1.
Important: Borland Enterprise Server 5.2.1 is not interoperable with version 5.0 due to fixes for bugs relating to compliance to specifications. Therefore, all installations of version 5.0 that interact with later versions must be upgraded.
To upgrade from Borland AppServer 4.5.x, do not install on top of the previous installation. Install in a separate directory or uninstall your previous version first. You may then migrate your applications from BAS 4.5.x to Borland Enterprise Server 5.2.1.
Important: For information on minimum hardware requirements, certified operating systems, JDKs, and compilers, please refer to the Product Platforms Page.
For AppServer edition: http://techpubs.borland.com/am/bes/platforms/52xplatformase.htm
For VisiBroker edition: http://techpubs.borland.com/am/bes/platforms/52xplatformvbe.htm
For Web edition: http://techpubs.borland.com/am/bes/platforms/52xplatformweb.htm
For Team edition: http://techpubs.borland.com/am/bes/platforms/52xplatformtme.htm
The following sections detail the J2SE requirements for Borland Enterprise Server. The J2SE versions referenced below are the only versions certified for use with Borland Enterprise Server.
It is vitally important that you read the Release Notes and/or Readme that accompany the version of Java you use with Borland Enterprise Server. In particular, pay special attention to the sections that detail Operating System patches that must be applied. Failure to do this WILL lead to unpredictable Java VM crashes.
On Windows and Linux, J2SE 1.3.1_06 and 1.4.1_01 are installed as part of the Borland Enterprise Server. You can read the Release Notes on Sun's web site.
On Solaris, J2SE 1.3.1_06 and 1.4.1_01 are installed as part of the Borland Enterprise Server. You can read the Release Notes on Sun's web site.
The Borland Enterprise Server is not certified to run with any IBM 1.4 JDK for AIX.
Please refer to http://www.hp.com/products1/unix/java/java2/sdkrte1_3/infolibrary/sdk_rnotes_1-3-1-07.html#socket. The patches listed on this page are required for this version of BES, although they are listed by HP as merely recommended. Please ensure that your system conforms to this patch level.
HP-UX kernels are typically underconfigured for real-world
applications, and must be re-tuned. HP-UX 11.0 is configured by default
to allocate only 64 threads to any particular process. The typical
symptom of this configuration problem is that ias and
other processes emit errors regarding memory problems or errors
regarding an inability to allocate additional threads. This can be
corrected by reconfiguring the kernel using the SAM utility. We recommend a minimum configuration of 512 threads per process.
You should test your application under load to the verify this meets your requirements.
HP provides the HPJconfig tool to help configure your kernel for a variety of Java applications. The tool can be downloaded from HP's web site.
Most scripts in this release use the KornShell, which must be installed on your
system. The pdksh package, which is distributed with Red Hat Linux, is known to
work but is not installed by default. To install this file, use this command:
rpm -i package-file