Supported Configurations for WebLogic Server 6.1
 |
 |
 |
|
 |
Get Adobe Reader |
Note: WebLogic Server 6.1 was retired November 14, 2006. See Supported Configurations.
The following sections provide an overview of supported WebLogic Server 6.1 configurations.
The table that follows lists the releases of WebLogic Server for each platform BEA supports.
Click a platform name to view all support information for that platform.
BEA provides full support for these platforms only. We are continuously working to provide support for more platforms. Please contact your sales representative for information about platforms not listed in this table.
The table that follows lists the platforms that are supported by WebLogic Server release.
Click a platform name to view all support information for that platform.
For product End-of-Life (EOL) information, see WebLogic Server and WebLogic jDriver End-of-Life Information.
For BEA's product lifecycle policy, see BEA Product Lifecycle Policy.
For information on changes in the release lifecycle for BEA products and related product components, as well as information about BEA support for third-party products reaching end-of-life, see BEA Product End-of-Life Announcements.
Sun Microsystems has announced the Sun End of Life (EOL) for J2SE 1.3.1. After March 30, 2006, this SDK will no longer be supported by Sun. Other SDK providers are likely to end support of 1.3.1 in a similar timeframe.
WebLogic Server configurations that run on J2SE 1.3.1 after the EOL will no longer be running on fully supported configurations. BEA will continue to provide support on these environments on a best-effort basis. However, lack of support by the SDK vendor may limit BEA's ability to resolve certain SDK related issues. For more information, see BEA Product End-of-Life Announcements.
The following sections provide information on:
For information on how WebLogic Server is distrubuted, see WebLogic Server Distribution Methods.
For general information on WebLogic Server installation, see the WebLogic Server 6.1 Installation Guide.
Because setup, download, and installation of WebLogic Server are more specialized on some platforms, this documentation provides additional information on these topics when required.
BEA supports WebLogic Server on multiple platforms, JVMs, and operating system configurations. BEA validates the operation of supported software on various sub-platforms with rigorous internal testing. In some cases, there are problems with certain JDKs, operating systems, and hardware platforms that prevent BEA from supporting WebLogic Server. BEA updates this site frequently to provide you with the latest information on supported sub-platforms and recommends that you confirm support for your configuration with other vendors you use.
We test our software in a variety of Java environments. Our multi-platform testing program contributes to the high quality of our software by uncovering bugs that only appear in some Java environments. We fix the bugs we find in WebLogic Server, but sometimes we uncover bugs in a particular Java environment or in the underlying operating system. When we uncover bugs such as these, we report the bug to the vendor and work towards a solution. We may also attempt to work around the bug in our software. For some sub-platforms, we specify a particular version of the Java Virtual Machine (JVM) or operating system patches needed to run WebLogic Server.
BEA attempts to support binary and source-level compatibility between WebLogic Server 6.1SP1 and WebLogic Server 6.0SP2 in the areas of persistent data, generated classes, API and Protocol compatibility. For more detailed information, see Compatibility Statement for BEA WebLogic Server 6.1.
WebLogic Server supports Development Platforms for the design, development, and verification of applications. Development Platforms are not supported for production server deployments. We indicate that a platform is supported as a Development Platform by specifically marking a platform as Development Platform Only.
A Java Virtual Machine (JVM) is required for WebLogic Server to run. For your convenience, in most cases the WebLogic installation program includes a JVM for creation of WebLogic domain configurations and use of WebLogic software. For details, see "Installing BEA WebLogic Server".
BEA cannot directly resolve potential issues traced to the third-party JVM. Support for a third-party JVM must be provided by the JVM vendor.
The version of any third-party JVM bundled by BEA is recommended by the JVM vendor at the time BEA releases its product. Because the versions of JVMs supported by vendors change over time, please consult with your JVM vendor and confirm the latest configurations in this document to understand the latest JVM support information before using a third-party JVM.
Platform support for the WebLogic jDrivers is described by individual platform. If you use a driver in conjunction with WebLogic Server, see the List of Supported Platforms for information on supported JVMs.
Note: The Type 4 drivers for Microsoft SQL Server and Informix Dynamic Server are pure Java drivers, are not tied to a particular OS and do not require any native libraries or DLLs.
Also note that other third-party JDBC Drivers may be used in conjunction with WebLogic Server. WebLogic is a completely java-based server and is committed to the J2EE standards. As such, WebLogic supports the use of any third-party JDBC driver to any DBMS while using WebLogic Server.
However, there are some limitations. The driver must be threadsafe. WebLogic is a highly multithreaded application and there are drivers (the JDBC-ODBC bridge from Sun, for example) which cannot be used with WebLogic. Also, when used in transactionally aware environments, such as for EJBs etc., the driver must implement the standard JDBC transactional calls, such as setAutoCommit(), setTransactionIsolation() etc. Third-party JDBC drivers that do not implement Serializable or Remote interfaces cannot pass objects to a T3 client application.
The following sections provide information on WebLogic Server platform support for the following Oracle versions :
WebLogic Server no longer supports Oracle 8.1.6 and earlier versions; Oracle has dropped support for these versions and is no longer fixing bugs in these products. The.dll files for their use are still available in earlier version of WebLogic, however future releases will no longer include them. If you are doing development work, it is highly recommended to move to 8.1.7 or higher.
WebLogic Server applications that use distributed transactions with Oracle Server 9.2.0.x are experiencing problems with the Oracle thin driver 9.2.0.x. For such applications, BEA recommends against using Oracle thin driver 9.2.0.x at this time. Instead, use a 9.0.1.X driver, where X is 3 or higher.
In addition to the aforementioned workaround, the following tuning technique may help alleviate the problem:
For more information, please see:WebLogic 6.1 jDrivers .
This section lists Web servers supplied by third-party vendors that are supported by WebLogic Server 6.1. Web Server plug-ins, delivered with WebLogic Server, enableWebLogic Server to communicate with applications which have been deployed on a different Web Server. For details about the Web Server Plug-ins, see the WebLogic Server Administration Guide at the following URLs:
|
Note: SWS is an Apache Web Server modified, released, and supported by HP. |
||
The Apache plug-in versions listed as supported on a particular platform are available from the Apache Server Foundation. Other products derived from the open source version of Apache, such as Covalent's Enterprise Ready Server, may also work with the Apache plug-in provided with WebLogic Server but have not been tested by BEA. All support testing for products based on open source Apache will be performed by the vendor offering such products.
Jolt is a Java-based client API that manages requests to BEA Tuxedo services via a Jolt Service Listener (JSL) running on the Tuxedo server. For more information on Tuxedo and Jolt, see BEA Tuxedo Documentation.
The next sections summarize Jolt support.
The following table provides support information for Jolt releases used with a WebLogic Server 6.1 client.
WebLogic Enterprise Connectivity (WLEC) is deprecated in WebLogic Server 7.0. Tuxedo Corba applications using WLEC should migrate to WebLogic Tuxedo Connector. For more information, see WebLogic Tuxedo Connector.
WebLogic Enterprise Connectivity (WLEC) is an optional component of WebLogic Server (WLS) version 5.1 and later. Using WLEC, you can execute objects and EJBs in WebLogic EnterpriseTM (WLE) 5.1, Tuxedo 8.0, or Tuxedo 8.1 domains from WLS applications. You enable WLEC by creating an Internet Inter-ORB Protocol (IIOP) connection pool and then writing server-side Java code to use the connection pool.
WLEC is supported on the following Tuxedo releases:
WebLogic Tuxedo Connector is supported on the following Tuxedo releases:
Note: If you use a browser version that is not listed as a supported browser in the following sections, you may experience functional or formatting problems.
Browser support for WebLogic Server is dependent on the browser version, the client operating system for console, and the Java plug-in for applet support. The following sections summarize browser support for WebLogic Server:
The following table summarizes browser support for the WebLogic Server console.
|
Intel Pentium-compatible with Windows 2000 Server or Windows 2000 Advanced Server Intel Pentium-compatible with Windows 2000 Professional |
|
The following table summarizes browser support for applets with WebLogic Server.
|
|
|