WebLogic Server 8.1 Certification

WebLogic Server 8.1 Certification for BEA WebLogic Java Adapter for Mainframe 5.1
Date: April 2004

This appendix was added to the BEA WebLogic Java Adapter for Mainframe (JAM) 5.1 Release Notes in January 2004 and updated in April 2004. It describes the additional WebLogic version and platforms on which the Java Adapter for Mainframe 5.1 is certified.

 

---

New in This Certification

The JAM 5.1 product is now certified for the WebLogic Server 8.1 on the platforms indicated in Supported Platforms for WebLogic JAM Components.

For information about additional fixes in this release, see Problems Fixed in This Release.

 

---

Not Supported in This Certification

The following items describe what is not supported in this certification:

• JAM 5.1 does not support the WebLogic Integration product on WebLogic Server 8.1.

• No new functionality has been added to the JAM 5.1 product.

 

---

Prerequisites

The following WebLogic Patch must be applied to your WebLogic Server 8.1 environment before running the Java Adapter for Mainframe 5.1 product: CR129439_810.

Please consult the BEA WebLogic Java Adapter for Mainframe 5.1 Release Notes for additional prerequisites.

 

---

Supported Platforms for WebLogic JAM Components

The following sections list the supported platforms for each of the WebLogic JAM components

WebLogic Server 8.1 Certification—Supported Platforms for the WebLogic JAM Gateway

The following table lists the platforms and associated version of the Java Development Kit (JDK) on which this version of WebLogic JAM Gateway is certified.

Table A-1 Supported Platforms for the WebLogic JAM Gateway

Platform	JDK Version
HP-UX 11.0	SunSoft 1.4.1_02
Microsoft Windows 2000 Server	SunSoft 1.4.1_02
Microsoft Windows 2000 Server	Jrockit 8.1
Microsoft Windows 2000 Advanced Server	SunSoft 1.4.1_02
Microsoft Windows 2000 Advanced Server	Jrockit 8.1
Solaris 8	SunSoft 1.4.1_02
Solaris 9	SunSoft 1.4.1_02

 

WebLogic Server 8.1 Certification—Supported Platforms and Required Stacks for the WebLogic JAM CRM

The following table lists the supported platforms and required stacks for the WebLogic JAM CRM.

Table A-2 Required Stacks for WebLogic JAM CRM

Platform	Stack
OS/390 Unix V2R8	OS/390 V2R8 SecureWay Communications Server
OS/390 Unix V2R9	OS/390 V2R9 SecureWay Communications Server
OS/390 Unix V2R10 (31-bit)	OS/390 V2R10 Communications Server
OS/390 MVS V2R8	OS/390 V2R8 SecureWay Communications Server
OS/390 MVS V2R9	OS/390 V2R9 SecureWay Communications Server
OS/390 MVS V2R10 (31-bit)	OS/390 V2R10 Communications Server
z/OS MVS V1R1.0 (31-bit)	z/OS V1R1.0 Communications Server
z/OS Unix V1R1.0 (31-bit)	z/OS V1R1.0 Communications Server
z/OS MVS V1R2.0 (31-bit)	z/OS V1R2.0 Communications Server
z/OS Unix V1R2.0 (31-bit)	z/OS V1R2.0 Communications Server
z/OS MVS V1R3.0 (31-bit)	z/OS V1R3.0 Communications Server
z/OS Unix V1R3.0 (31-bit)	z/OS V1R3.0 Communications Server
z/OS MVS V1R4.0 (31-bit)	z/OS V1R4.0 Communications Server
z/OS Unix V1R4.0 (31-bit)	z/OS V1R4.0 Communications Server
Solaris 8	DCL 7.0.2.2
Solaris 9	DCL 7.0.2.4

 

 

---

Miscellaneous Issues

This section provides information about known limitations and fixed problems in the current release of WebLogic JAM.

Solaris 9 DCL 7.0.2.4 SNA Primary Group Requirement

Solaris 9 DCL 7.0.2.4 includes an authorization test that requires each application to start under a user ID having SNA as its primary group. The WebLogic JAM CRM must comply with this requirement.

Problems Fixed in This Release

This section describes known problems from the prior release of WebLogic JAM that have been fixed with the current release of the software. The following table lists a BEA Case or Change Request (CR) number for each problem.

Table A-3 Problems Fixed in This Release

Change Request Number	Description
CR103763	Problem: Default codepage is used even when a different codepage is designated on the output dataview. The egen code generator was changed to correctly use the user specified codepage to translate the output from EBCDIC to UNICODE.
CR108888	Problem: The XML generated by the JAM egen tool does not work in XMLUnloader with the XML Spy product. The JAM egen product was updated to generate the DTDs required for the XML Spy product.
CR120587	Problem: JAM JCA threw an error when using an input XML Record. The JCA was changed to fully support the XML Record type.
CR121012	Problem: CRM transactional tasks are queued up but not processed in certain load conditions. The CRM now successfully processes the queued items.