HP BridgeWorks Version 3.0A includes the following new features, as well
as several important bug fixes.
The BridgeWorks UI now helps coordinate team members using a shared
BridgeWorks connection database. As developers work with a connection
definition within BridgeWorks, they are registered within the database
itself. If other team members attempt to work with the same
connection definition (in that shared database), they are notified
that it is being modified, as well as who is modifying it. BridgeWorks
then allows the developer to open the connection definition in
Multi- and Mixed-Character Set Support
Java supports many different characters sets. BridgeWorks now supports
the passing of strings based on these many character sets. This
support also includes the mixing of character sets within a single
Enhanced Support for ODS-5 Disks
BridgeWorks has improved its support for the ODS-5 file system.
Previously, BridgeWorks had problems seeing some directories and files
with mixed case characters in its name.
New Installation Procedures
The OpenVMS kit has been changed to use PCSI, while the Windows kit
has been changed to use the latest Install Shield. The new
installation procedures provide the user with a more robust set of
options, including an enhanced uninstall procedure.
HP BridgeWorks Version 3.0 introduced a host of new and
innovative features that enable and support enterprise-level
Foremost among these features are:
Support for Cross-Platform Transactions
BridgeWorks now enables two-phase commit transactions that originate from a
Java client and are coordinated by a J2EE transaction manager, such as BEA WebLogic
Server. BridgeWorks supplies all the infrastructure components for OpenVMS integration
of DECdtm-based 3GL or ACMS transactional applications and other resource managers
- including transaction-aware databases, such as Rdb and Oracle9i.
New Transport Options
An enhanced transport-layer architecture optimizes transport by providing ICC
(Intra-cluster Communications), DCE/RPC, or no-transport options. ICC provides
clustered OpenVMS systems with the fastest transport available. DCE/RPC no longer
requires the DCE RPC developer license.
Faster Build Times, More-Efficient Runtime Code
BridgeWorks now uses an improved component architecture that uses optimized
runtime libraries and reduces the amount of user-specific generated code.
New Server Management Services
The BridgeWorks Manager provides new directory services and server management
for the middle component. This includes load-balancing capabilities, such as
keeping track of available servers and maintaining pools of free servers (determined
by configurable parameters for minimum, maximum, and idle servers) to speed
response times. These extra capabilities allow some connections to avoid the
high cost of process creation at server startup.
BridgeWorks now supports OpenVMS SYSUAF-based client authentication. This means
that server processes will start up in the BridgeWorks default (SYSTEM or another
specified) account, and clients will be able to use a log-in and log-out method
to access other OpenVMS accounts required to use the wrapped application.
An enhanced structures scheme gives you the option of using Java-based get and
set access methods for individual fields. This implementation is consistent
with the getter/setter bean that is recognized by Java IDEs, such as NetBeans.
By using enhanced structures, you can simplify client coding and optimize call-time
performance by doing most data marshaling at the time the values are being read
from and written to the client.
» Return to the HP BridgeWorks home page