|
|
United States-English | |
|
|
 |
|
 HP OpenVMS Systems |
|
Readme for WindowsSeptember 2004
HP BridgeWorks Version 3.0A introduces new and innovative features that
enable and support enterprise-level distributed applications, and includes
several important bug fixes. This file contains information that will help you install and use this
release of HP BridgeWorks. Software Version Hewlett-Packard Company
© 2004 Hewlett-Packard Development Company, L.P. Intel,
Intel Inside, and Itanium are trademarks of Intel Corporation in the Microsoft,
Windows, Windows XP, Visual Basic, Visual C++, and Win32 are trademarks of
Microsoft Corporation in the Java and
all Java-based marks are trademarks or registered trademarks of Sun
Microsystems, Inc. in the BEA WebLogic Server is a trademark of BEA Systems Inc. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided “as is” without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
|
|
Component |
Existing Application |
Transactions |
Structures |
|
EJB |
3GL, ACMS, DCL, Files |
Yes |
Yes |
|
JavaBeans |
3GL, ACMS, DCL, Files |
Not Applicable |
Yes |
|
COM |
3GL, DCL, Files |
No |
No |
Not supported in this release:
Tru64
UNIX is not available as a target platform for middle components in this
release.
Cross-platform
limitations apply to COM:
Cross-platform COM connections - where a Windows client communicates with
an Alpha-based middle component - have produced inconclusive results related to
account and security issues. The following configurations are recommended
instead:
1. Windows client to Windows COM middle component.
2. OpenVMS Alpha client to Alpha COM middle component.
Note: Your choice of component architecture should be guided by an understanding of the relative merits and limitations of each component type for your particular distributed application needs. It should take into account any preexisting middle-tier application server and client codebase.
These
are the minimum system requirements needed to install BridgeWorks and to build
and run the generated components. “Optional” requirements represent requirements
that are not needed for every type of connection. However, several such
requirements will apply to your particular platform/component selection.
Make sure you
have the latest MUPs, ECOs, and patches for your configuration. Search for
these on the Patch Download page.
http://www2.itrc.hp.com/service/patch/mainPage.do
Always
Check Cross-Product Requirements!
Always check for cross-product software requirements, which can change with new
releases. These product requirements may be greater than for BridgeWorks
itself.
For example, to run a BridgeWorks-generated EJB component requires OpenVMS Alpha Version 7.3 or higher and a Java 2 Runtime Environment 1.3.1 or higher. Each Java SDK and RTE has specific ECO requirements. In addition, WebLogic Server 7.0 (a J2EE 1.2-compliant application server) requires OpenVMS Alpha Version 7.3 or 7.3-1, the Java 2 SDK 1.3.1-5 or higher, and additional ECOs as specified. (See Section 2.3: Additional OpenVMS Requirements)
2.1 OpenVMS
Server Component - Installation Requirements
OpenVMS Alpha Version 7.3, 7.3-1, and 7.3-2
4,500 blocks during installation, 3,500 blocks after installation
System requirements vary enormously depending on the way you deploy your BridgeWorks components.
Server Component - Development Requirements
The C Compiler is required to build all server components:
HP C Version 6.5 for OpenVMS Alpha or higher
Server Component - Optional Development Requirements
For automatic import and build features, you must enable REXEC and FTP services.
TCP/IP Services for OpenVMS Version 4.2 or higher
TCP/IP for OpenVMS Home Page
http://h71000.www7.hp.com/network/tcpip.html
Server Component - Optional Runtime Requirements
You can choose between non-transport and transport-based options:
Non-Transport-Based Connections
None for Alpha-only, nontransactional connections.
Transport-Based Connections
You can use choose
either ICC (Intra-cluster Communications) or RPC, or both. (If you
choose both, the BridgeWorks Manager automatically use ICC in a cluster configuration
and RPC in a noncluster configuration.)
ICC for OpenVMS Alpha Version 7.3 or higher
(Bundled with operating system)
or
DCE RPC Runtime Services Kit Version 1.5 or higher
DCE for OpenVMS Home Page
http://h71000.www7.hp.com/commercial/dce/dce_index.html
For DCE RPC
OpenVMS Alpha DCE Denial of Service
Security Patch Kit
Alpha Security ECO Kit For SSRT3608
http://www2.itrc.hp.com/service/cki/patchDocDisplay.do?patchId=ALP_DCE_030_SSRT3608
Middle Component - Optional Development and Runtime Requirements
For middle components, similar requirements apply during development
and at runtime.
For JavaBeans and EJB components
Java 2 SDK (“JDK”) Standard Edition 1.3.1-7 or higher
Runtime only
Java 2 RTE (JRE) Standard Edition 1.3.1-7 or higher
Java Software Patches (ECOs): See Section 2.3: Additional OpenVMS Requirements
Java Technology for Alpha Download Page
http://h18010.www1.hp.com/java/download/
For COM components only
COM for OpenVMS Version 1.3
Compaq C++ 6.5 for OpenVMS Alpha
COM Denial of Service ECO kit for SSRT3608
COM for OpenVMS Home Page
http://h71000.www7.hp.com/openvms/products/dcom/
C++ for OpenVMS Home Page
http://h71000.www7.hp.com/commercial/cplus/cplus_index.html
ECO kit for SSRT3608
http://www2.itrc.hp.com/service/cki/patchDocDisplay.do?patchId=DCOM_013_SSRT3608-V0
For EJB components only
A J2EE 1.2-compliant environment
Free 30-day evaluation license available for WebLogic Server.
Download Version 7.0 or 8.1 SP1 for HP OpenVMS.
See Section 2.3: Additional OpenVMS Requirements
BEA WebLogic Server Downloads Page
http://commerce.bea.com/showallversions.jsp?family=WLS
For Transactions (EJB components only)
DECdtm/XA SDK 2.1
This new release of DECdtm/XA ships on OpenVMS Version 7.3-2. It must
be installed as a layered product on OpenVMS Alpha Version 7.3 and 7.3-1.
Note: Version 2.1 is available as a layered product from the BridgeWorks Download page.
BridgeWorks Home Page
http://www.hp.com/go/bridgeworks
Alpha System Recommendations for Java applications
|
|
Best |
Average |
Low |
|
System speed |
Above 500MHz |
500MHz |
Below 500MHz |
|
System memory |
1GB or higher |
512MB |
Minimum 256MB |
“Average” represents the recommended minimums for deploying Enterprise JavaBeans using BEA WebLogic Server.
For ACMS applications
A properly configured ACMS 4.3-or-later system.
Middle Component - Installation Requirements
Windows XP SP1 or Windows 2000 SP2 or higher
Note: 2000 Server or XP Professional recommended in a production
environment.
2003 Server has not been tested.
40MB minimum free disk space
128MB minimum RAM
TCP/IP configured
Internet Explorer 5.5 or higher
Optional Development and Runtime Requirements
For middle components, similar requirements apply during development
and at runtime.
For JavaBeans and EJB components
Java 2 SDK (SDK) Standard Edition 1.3.1 or higher
Runtime only
Java 2 RTE (“JRE”) Standard Edition 1.3.1 or higher
For COM components only
Microsoft Visual C++ 6.0 SP5
Note: Visual C++ .NET is not supported and is not a substitute.
For EJB components only
A J2EE 1.2-compliant environment
ECO Downloads for Java 2 SDKs for OpenVMS
ECO Page for 1.4.2
http://h18010.www1.hp.com/java/download/ovms/1.4.2/sdk1.4.2_patches.html
ECO Page for 1.4.1
http://h18010.www1.hp.com/java/download/ovms/1.4.1/sdk1.4.1_patches.html
ECO Page for 1.4.0
http://h18010.www1.hp.com/java/download/ovms/1.4.0/sdk1.4.0_patches.html
ECO Page for 1.3.1
http://h18010.www1.hp.com/java/download/ovms/1.3.1/sdk1.3.1_patches.html
For BEA WebLogic 7.0 or 8.1 SP1 for OpenVMS
BEA WebLogic 8.1 SP1 for OpenVMS Requirements Page
http://edocs.bea.com/platform/suppconfigs/configs81/hpovms73_alpha/81sp1.html
Installation
involves setting up HP BridgeWorks on (at least) two systems:
§
Installing the BridgeWorks Manager, development
tool utilities, runtime library and support files on OpenVMS.
(For
OpenVMS installation instructions, see the BWX030A_INSTALLATION_GUIDE.TXT |HTM|PDF|PS,
available from the web download page.)
§
Installing the BridgeWorks development tool,
runtime library and support files on Windows.
Note: The BridgeWorks Version 3.0A Windows kit can only be used in conjunction with the corresponding Version 3.0A OpenVMS kit. Subsequent field test and production releases will require both installations to be repeated with the up-to-date kits.
You
should uninstall Version 3.0 before installing Version 3.0A of BridgeWorks.
This is a required step to ensure all files are properly replaced.
Before you begin
Back up your connection database to preserve your BridgeWorks connection
database.
§
Copy the file BWXData_2_03.mdb to a secure
location before uninstalling BridgeWorks.
Instructions:
HP BridgeWorks should be uninstalled by first using the Windows Control Panel utility and then removing remaining files and directories as necessary.
Follow the standard Windows uninstall procedure. (The following steps
are for Windows XP; some details may differ for Windows 2000):
1.
Click the Windows Start button and click Control
Panel.
2.
Open Add
or Remove Programs, select HP BridgeWorks, and click the Change/Remove button.
3.
Follow any on-screen instructions.
4.
When the uninstall is complete, go to the location
where BridgeWorks was installed (usually, C:\Program Files\HP BridgeWorks) and
delete all remaining files and subdirectories EXCEPT for the BWXData_2_03.mdb
file.
IMPORTANT UPGRADE INFORMATION: If your current version of BridgeWorks is 2.1 or 2.1A, the BridgeWorks installation process will automatically prompt you to import your existing connection definitions into the new Version 3.0 and higher database. Your 2.1/2.1A connection database will not be affected by this procedure.
This is your ONLY opportunity to import your
existing connections unless you rerun the installation.
Before you begin:
§
Your Windows user profile should include
Administrator privileges to install BridgeWorks.
Using BridgeWorks with a
nonprivileged account
After installing, you can use a nonprivileged user account on Windows XP or
2000 to run BridgeWorks. However, if you are installing to an NTFS partition on
Windows 2000, you must choose a directory with read and write privileges to do
so. (The default installation location, under \Program Files\ is protected,
meaning that only users with Administrator accounts are able to run BridgeWorks
on Windows 2000.)
§
As with any Windows installation, you are recommended
to:
-Do a system backup before proceeding.
-Exit all other Windows applications before installing.
§
The BridgeWorks setup includes Microsoft’s ODBC
3.0 files. The installation updates files only if they need to be updated and
creates a new ODBC data source called “BWXData_2_03”. If you have a newer
version of ODBC than 3.0, setup will leave this as is.
Instructions for web download installation
1.
Save the BridgeWorks self-extracting archive (BWX030A_Setup.exe)
to a temporary location on your disk by choosing the option to save the program
to your disk.
2.
In My Computer or Windows Explorer, double-click
the downloaded file and wait for the Setup Wizard to begin.
3.
Follow the on-screen instructions in the Setup
Wizard to complete the installation. You will be prompted for any required information,
including install location on your Windows machine.
Note: Choose the Typical or Custom Install to get all the supplied
files for tutorials and examples.
After Installation:
ALWAYS restart J2EE environments, such as BEA WebLogic Server, or other bean servers, such as Tomcat, after a BridgeWorks installation. Such environments do not automatically refresh shareable images and libraries without being restarted.
Environment Evaluation Wizard
The Environment Evaluation Wizard (EEW) is a utility included in the Windows kit for post-installation diagnostics. For more information, see the EEW.chm Help file that is distributed with the utility in the \HP BridgeWorks\Utilities\EEW directory.
Important: The EEW in this release has not been updated to reflect the current Version 3.0A requirements.
3.3 Running
BridgeWorks on Windows
To start the BridgeWorks development tool:
1.
Click the Windows Start button and click Programs.
2.
Click the BridgeWorks icon in the HP BridgeWorks
program folder.
Using
Help
Context-sensitive and reference-based online Help is available from:
§
The HP BridgeWorks Program Folder:
Click the
BridgeWorks Help icon.
§
The BridgeWorks Development Tool
To get the
Help Contents in the main BridgeWorks window, choose Help Topics from the Help
menu. Press F1 for window-level Help.
To search Help
Click the Search tab, type one or more words, and click List Topics.
To get What’s
This Help in the BridgeWorks Wizard or a dialog box
Click the ? button once and click a control, or select a control and press F1.
To get Topic
Help inside the BridgeWorks Wizard or a dialog box
Click the Help button.
Using the
Tutorials and Examples:
In
Help, open the Quick-Start Tutorials book in the Contents tree.
You’ll find complete instructions for building your first JavaBeans, EJB, or COM connection, including simple clients. Supporting sample files, which are referenced in the tutorial, are included in the BridgeWorks installation kit.
Important:
Disregard references to
VAX as a platform for wrapping applications using BridgeWorks Version 3.0A.
Caution: In Version 3.0A,
some published help topics are not fully updated or applicable to Version 3.0A.
Please Refer to “Key Usage Topics” (linked from the Help Welcome page) for the
most important topics.
Note: Accuracy of web links cannot be guaranteed.
To check for
updated documentation
From
Help, click About Help and click the “Check for Updated Documentation” link.
(This opens a BridgeWorks web page from which you can download newer
documentation than in the installation kit if it is available.)
-
Preparation of 3GL Routines and ACMS Tasks
-
Transport Options
-
Scalability and Your Application
-
Session Options and Your Application
-
Making Configuration Changes
-
Working with Rdb and Oracle9i Databases
-
Debugging Your Server Routines
- Using the Bwx Classes
- Compiling and Running Java Clients
Performance Disclaimer – Please Read
HP
makes no performance claims for BridgeWorks-generated applications. Performance
metrics for HP BridgeWorks are largely dependent on the underlying
cross-platform technologies used by BridgeWorks - including RPC and ICC
transports; COM, Java, and EJB components; J2EE application servers; and DECdtm
and XA protocols for transactions. Given the complexities of distributed
computing and the huge diversity of potential production environments,
including such factors as data throughput and network speed, it is not possible
to make any baseline assertions about the performance you should expect.
For these reasons, it is strongly recommended that you obtain the
advice of a qualified services consultant before embarking on any major or
mission-critical project.
Multi-developer
Support
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
read-only mode.
