HP BridgeWorks Version 3.0A Release Notes for OpenVMS

This document outlines the Release Notes for HP BridgeWorks Version 3.0A for OpenVMS, published in September 2004. It details new and innovative features designed to support enterprise-level distributed applications, includes several important bug fixes, and provides essential information for installation, usage, and upgrading.

Key New Features (across Versions 3.0A and 3.0):

• Multi-developer Support (3.0A): The BridgeWorks UI now facilitates team collaboration by registering developers modifying shared connection definitions, allowing others to access them in read-only mode.
• Installation Enhancements (3.0A): New, more robust installation procedures using PCSI for OpenVMS and the latest Install Shield for Windows, with improved uninstall options.
• Character Set Support (3.0A): Enhanced support for passing strings based on various and mixed Java character sets.
• ODS-5 Disk Support (3.0A): Improved compatibility with ODS-5 file systems, resolving issues with mixed-case directory and file names.
• Corrected Problems (3.0A): Fixes for ACCVIO crashes in BridgeWorks Manager and various FTP/browsing errors during the ANA import process.
• Cross-Platform Transactions (3.0): Introduction of two-phase commit transactions originating from Java clients and coordinated by J2EE transaction managers (e.g., BEA WebLogic Server), integrating DECdtm-based 3GL/ACMS and transactional databases like Rdb and Oracle9i.
• New Transport Options (3.0): An enhanced transport layer offering ICC (Intra-cluster Communications) for fastest OpenVMS cluster performance, RPC (now without requiring a developer license), and no-transport options.
• More-Efficient Runtime Code (3.0): Improved component architecture with optimized runtime libraries, reducing user-specific generated code, simplifying deployment, and improving maintainability.
• Server Management Services (3.0): The BridgeWorks Manager now provides new directory services and server management capabilities, including load-balancing and server pooling to speed response times.
• SYSUAF-Based Security (3.0): Support for OpenVMS SYSUAF-based client authentication, allowing clients to log in and out of different OpenVMS accounts.
• Enhanced Structures & Exceptions (3.0): New Java-based get/set access methods for individual fields, an abstract BwxStructure class, and a new BwxDecimal class for OpenVMS decimal strings (leveraging Java's BigDecimal). Exception handling is enhanced with a root BwxException and derived classes for better error differentiation.

Upgrade Considerations for BridgeWorks 2.1/2.1A Users:

• Version 3.0A coexists with older versions but is not backward-compatible for newly generated code.
• Existing Java clients will require import statement changes (from com.compaq.bwx to com.hp.bwx), adjustments for the new BwxStructure and BwxDecimal classes, and updated error handling for structure constructors.
• Extended Method Code (customized middle component code) is no longer supported.
• The installation process provides a one-time opportunity to import existing connection databases.

Configuration Requirements:

• ICC transport requires the ICC$STARTUP file to be enabled.
• The BridgeWorks Manager and server processes require LOG_IO privilege for mailbox operations.

Known Limitations and Issues:

• Transaction support with WebLogic versions 7.0 and higher has known issues, with workarounds provided (e.g., specifying unique EJB domain names).
• Transactions may fail if WebLogic's JTA Health Monitor times out (workaround: override timeout in config.xml).
• Server processes supporting EJBs in an OpenVMS cluster may crash during cluster transitions (client recovery is advised).
• Some COM-related issues are under investigation, with a recommendation to run COM middle components on Windows systems for this release.
• Nonthreadsafe applications should not be run with the no-transport option.

The document also provides contact and support information, including email addresses for feedback and the HP BridgeWorks home page.