HP OpenVMS

Note: WebLogic Server 6.1 was retired November 14, 2006. See Supported Configurations.

General Information

For 1.3.1 SDK End-of-Life information, see BEA Product End-of-Life Announcements.
To download supported releases for this platform, see Distribution and Installation Information.
For Information on Web servers supplied by third-party vendors that are supported by WebLogic Server 6.1, see Platform Support for Web Servers.
For general information about Java technology for HP (formerly Compaq) Alpha Systems, see the hp OpenVMS^TM systems website.

This section lists the releases supported for this platform:

For detailed information on this Platform, JVM requirements, and installation instructions, see How to Install BEA WebLogic Server 6.1 on OpenVMS^TM Alpha^TM.

Operating System	OpenVMS 7.3 or later OpenVMS 7.3 Update kit: VMS73_UPDATE-V0100 Available via the standard OpenVMS ECO release process at: http://ftp1.support.compaq.com/public/vms/axp/v7.3. OpenVMS 7.3 Compaq C Runtime ECO kit: VMS730_ACRTL-V0200 Available via the standard OpenVMS ECO release process at: http://ftp1.support.compaq.com/public/vms/axp/v7.3. OpenVMS 7.3 LIBRTL ECO kit: VMS73_LIBRTL-V0200 Available via the standard OpenVMS ECO release process at: http://ftp1.support.compaq.com/public/vms/axp/v7.3.
Required OS Patches	None
CPU	A HP Alpha processor with a non-system disk that can be converted or initialized to ODS-5. Note: The disk must not have page or swap files on it. 433 MHz Alpha
RAM	Tested with 2GB
Disk Space	67 MB
Supported Client JVM	JDK 1.3.1 JavaTM 2 Runtime Environment, Standard Edition Fast VM (build 1.3.1-3, build J2SDK.v.1.3.1:03/22/2002-15:43, native threads, jit_131)
Supported Server JVM	JDK 1.3.1 JavaTM 2 Runtime Environment, Standard Edition Fast VM (build 1.3.1-3, build J2SDK.v.1.3.1:03/22/2002-15:43, native threads, jit_131)
Performance Pack	None
Node Manager	None
Oracle jDriver	Oracle 8.1.7 Thin Driver for Oracle 8.1.7

NodeManager functionality is not supported in this release. The workaround is to start the managed nodes manually.

NodeManager functionality is not supported in this release. The workaround is to start the managed nodes manually.