Product Documentation
Abstract
This document contains system requirements for WebSphere Application Server V6.1 on z/OS.
Content
|
| Back to all V6.1 detailed system requirements |
This document describes the minimum product levels that need to be installed before opening a problem report with the WebSphere Application Server Support team. Because other products frequently ship fixes, updates, and new releases, testing every configuration is not possible. In general, you can install and run with updates to supported products if those updates are forward compatible.
The following list identifies the products that are supported when WebSphere Application Server runs on the z/OS operating system. It is not necessary to run these products on the same machine or operating system as WebSphere Application Server.
(+) Product is included with this WebSphere edition
| Operating Systems supported with 31-bit WebSphere Application Server |
| |
| Operating Systems supported with 64-bit WebSphere Application Server |
| |
| Hardware Requirements |
(See the program directory for disk space requirements) | |
| Java™ The WebSphere-supplied Java 2 SDK is required for both the run time and any remote Java clients |
| |
| Databases and Transaction Managers See the JDBC Drivers section |
| |
| Java Database Connectivity (JDBC) Drivers For the mapping of the JDBC Driver to supported databases refer to the information center article, Vendor-specific data sources minimum required settings. |
| |
| LDAP Servers using Stand Alone LDAP User Registry Configuration | Any LDAP directory server that supports the LDAP V3 specification rfc 2251 is supported unless specific LDAP is noted on unsupported page. The following products were investigated and meet the specification if you are at the level indicated or higher:
For the LDAP servers not listed above that support the LDAP V3 specification, you will need to configure the LDAP server using a custom LDAP feature with an appropriate filter and you will need to obtain the appropriate filter information from your LDAP vendor. | |
| LDAP Servers using Federated Repository Configuration | Any LDAP directory server that supports the LDAP V3 specification rfc 2251 is supported unless specific LDAP is noted on unsupported page. The following products were investigated and meet the specification if you are at the level indicated or higher:
For the LDAP servers not listed above that support the LDAP V3 specification, you will need to configure the LDAP server using a custom LDAP feature with appropriate objectclass and attribute mappings that you need to obtain from your LDAP vendor. | |
| Web Servers Refer to the information center article, Installing Web server plug-ins. |
| |
| Web browsers |
(See Required Detail 6) | |
| JMS Provider |
| |
| Security |
| |
| Third Party ORBs |
|
For information regarding the supported WebSphere Application Server programming model, see the specifications and API documentation topic in the Version 6.1 Information Center.
Required details:
1 IBM provides the plug-in binaries for the selected Web server on the z/OS operating system.
2 WebSphere Application Server Version 6.1 supports IBM Cloudscape V10.1, which provides the Derby V10.1 runtime, National Language Service (NLS) enablement, and IBM problem support. However, Application Server does not currently support Cloudscape V10.1 for production. The Application Server tools, the administrative console, and the runtime all reference Derby class files and object names.
3 6.1.0.15 (or higher) is required to work with Microsoft SQL Server JDBC Driver, version 1.2.
4 Ships with the z/OS operating system.
5 IBM WebSphere MQ and IBM WebSphere MQ for z/OS can be used with, and as an alternative to, the default messaging provider that is included with WebSphere Application Server. Client mode connections are supported for IBM WebSphere MQ Version 5.3 CSD 12, IBM WebSphere MQ V5.3.1 for z/OS plus PK10303, IBM WebSphere MQ V6.0.1.1 and IBM WebSphere MQ V6.0 for z/OS plus PK22728. To establish client mode connections you can use the intrinsic capability of WebSphere Application Server to communicate with IBM WebSphere MQ or IBM WebSphere MQ for z/OS on any platform. IBM WebSphere MQ V5.3.1 for z/OS plus PK31290 and IBM WebSphere MQ V6.0 for z/OS plus PK22728 are also supported for bindings mode connections from 31-bit WebSphere Application Server for z/OS. IBM WebSphere MQ V6.0 for z/OS plus PK31289 is also supported for bindings mode connections from 31-bit and 64-bit WebSphere Application Server for z/OS. To establish bindings mode connections, you must run the application server and queue manager on the same machine, on the same operating system, and on an architecture that is supported by the relevant version of IBM WebSphere MQ for z/OS.
6 Browsers enable viewing of the administrative console, Samples Gallery, and launchpad. Local and remote administration is supported. The Samples Gallery also supports local or remote use. The launchpad is limited to local use. Not all browsers are supported on all systems. There is neither restriction nor certification of Web browsers on clients that connect to the server to display content.
7 The selected Web server does not run on the z/OS operating system. However, IBM provides the plug-in binaries for the operating system on which the Web server can run.
8 The Oracle 9i JDBC driver is supported with Oracle 9i database server. The Oracle 10g JDBC driver is supported with both Oracle 9i and 10g database servers. The Oracle 11g JDBC driver is supported with Oracle 9i, 10g, and 11g database servers.
9 CORBA Interoperability testing was performed with WebSphere Application Server running on z/OS. VisiBroker 6.5 and Orbix 6.3 were run on AIX, Solaris, and Windows. Sun J2SE was run on Solaris and Windows. All testing was done with 32-bit kernel support only.
10 6.1.0.11 (or higher) is required for plug-in to work with Apache 2.2
11 Information about using WebSphere MQ as the JMS Provider for WebSphere Application Server Version 6.1
12Microsoft SQL Server JDBC Driver version 3.0 was tested with Microsoft SQL Server 2008 R2 database
Back to top
Change history
Last Updated: 27 August 2011
- 27 August 2011: added z/OS v1.13 information
- 3 August 2011: Added DB2 Connect 8.2 FP8, 9.1 FP3 or 9.5 FP1 to JDBC drivers section.
- 22 July 2011: Added hotfix for Microsoft SQL Server JDBC Driver, version 3.0 and version 1.2
- 24 September 2010: Added V1.12 to 31 and 64 bit operating systems
- 9 September 2010: Added Microsoft SQL Server Enterprise 2008 R2 Driver and footnotes.
- 31 July 2010: Added Oracle Database 11.2.0.1
- 8 July 2010: Added Oracle Driver 11g release 2 to JDBC
- 6 July 2010: Added Informix JDBC Driver 3.50 JC1
- 25 November 2009: Added Microsoft SQL Server 2008
- 25 September 2009: Added z/OS 1.11
- 17 August 2009: Added z/OS 1.10
- 4 August 2009: Added (type 2/4) for Oracle JDBC driver
- 6 June 2009: Added Tivoli Directory Server 6.2 support
- 26 May 2009: Added Informix 11.50xC1 support
[{"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"General","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"6.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
09 December 2019
UID
swg27007678