HP BridgeWorks Version 3.0A

This document is the Readme for HP BridgeWorks Version 3.0A for Windows, released in September 2004.

Overall Purpose: HP BridgeWorks 3.0A introduces new features and bug fixes to support enterprise-level distributed applications. This Readme provides essential information for installing and using this release.

Key Highlights:

1. Cross-Platform Tool: BridgeWorks is a cross-platform tool consisting of an OpenVMS Alpha kit (for running wrapped servers) and a Windows kit (for development tools and runtime libraries).
2. Supported Platforms:
   • Server Component (OpenVMS Alpha): Versions 7.3, 7.3-1, 7.3-2. (Note: Itanium 8.2 and Alpha 8.2 are not supported. VAX applications are not supported in 3.0A but remain supported in 2.1A).
   • Middle Component (Windows): Windows XP SP1 or Windows 2000 SP2+.
3. Generated Components: Can expose applications as JavaBeans, Enterprise JavaBeans (EJB), or COM objects. Limitations apply, such as transactions only for EJB and COM not supporting ACMS tasks or structures/arrays in 3GL. Cross-platform COM is not recommended due to security issues; Windows client to Windows COM, or Alpha client to Alpha COM are recommended.
4. Installation & Upgrade:
   • Mandatory Uninstall: Users of Version 3.0 must uninstall it before installing 3.0A.
   • Connection Database Import: The installation process offers a one-time opportunity to import existing 2.1/2.1A connection definitions into the new 3.0A database. Backing up BWXData_2_03.mdb is recommended.
   • System Requirements: Detailed requirements for OpenVMS (C Compiler, TCP/IP, Java SDK/RTE, DCE RPC, DECdtm/XA for transactions, ACMS for ACMS apps) and Windows (disk space, RAM, IE, Java SDK/RTE, MS Visual C++ 6.0 SP5 for COM).
   • Post-Installation: Restart J2EE environments (e.g., WebLogic Server) after installation.
5. New Features (Version 3.0A & 3.0):
   • Multi-developer Support: Facilitates team collaboration on shared connection databases, notifying users of concurrent edits.
   • Improved Installation: Uses PCSI for OpenVMS and Install Shield for Windows, offering more robust procedures.
   • Enhanced Character Set Support: Better handling of multi and mixed character sets in Java strings and improved ODS-5 disk support.
   • Fixed Issues: Corrected ACCVIO in BridgeWorks Manager and various FTP/import problems.
   • Cross-Platform Transactions: Supports two-phase commit transactions originating from Java clients, coordinated by J2EE transaction managers.
   • New Transport Options: Enhanced architecture with ICC (Intra-cluster Communications) and RPC (RPC no longer requires a developer license).
   • More Efficient Runtime Code: Optimized libraries reduce generated code, build times, and simplify deployment.
   • New Server Management Services: Includes load-balancing and server pooling.
   • SYSUAF-Based Security: Supports OpenVMS SYSUAF-based client authentication.
   • Enhanced Structures and Exceptions: BwxStructure is now an abstract class with improved get/set methods, and a new BwxDecimal class handles OpenVMS decimal strings. Enhanced exception hierarchy (BwxException, BwxServerException, BwxConnectException).
6. Upgrading Considerations (from 2.1/2.1A):
   • Not Backward-Compatible: The new component architecture is not backward-compatible.
   • Manager Coexistence: The new OpenVMS Manager (BWX$MANAGER) replaces the old one, but the old one (BWX$MGR_V21) can still run for 2.1/2.1A connections.
   • Client Code Changes (Java): Existing Java clients will require changes to import statements (com.compaq.bwx to com.hp.bwx), BwxStructure usage (now requires try/catch), and replacing BwxString with BwxDecimal for decimal string types. Extended method code is no longer supported.
7. Known Limitations and Issues:
   • WebLogic Transaction Support: Issues with BEA WebLogic Server 7.0 and higher when two EJBs are called in the same domain; workaround involves using WL 6.1 or unique domain names.
   • WebLogic JTA Health Monitor: Transactions may fail if the JTA health monitor times out; workaround to override MaxXACallMillis.
   • COM-Related: Ongoing issues, recommended to run COM middle components on Windows.
   • No-Transport Option: Not suitable for non-threadsafe (e.g., COBOL) applications when the JVM is part of a larger environment.
   • Documentation: The Environment Evaluation Wizard (EEW) and some help topics are not fully updated for 3.0A.
8. Performance Disclaimer: HP makes no performance claims due to the complexity of distributed computing and underlying technologies. Consulting a qualified services consultant for critical projects is recommended.