The following sections describe system requirements for WebSphere Application Server for z/OS.
Hardware requirements
The
hardware requirements for this product are any hardware that supports OS/390
Version 2 Release 10 or any version of z/OS Version 1.1 or later. However,
there are significant performance advantages for those applications doing
floating point arithmetic if the machine has binary floating point hardware,
such as S/390 Parallel Enterprise Server-Generation 5 and later systems.
The LPAR in which the WebSphere Application Server for z/OS runtime and initial Application Servers run requires a minimum of 512 MB of real storage. You may need to increase the real storage size depending on the size and number of Application Servers you deploy. In addition, you may want to increase your JES spool space if you use WebSphere Application Server for z/OS tracing options to the SYSPRINT DD dataset.
You should plan on an extra 3390-3 volume for the distribution and configuration HFS data sets, two additional 3390-3 volumes for the WebSphere product code, and two further 3390-3 volumes if you will use the Integrated JMS Provider.
Recommendation: Increase your paging subsystem by one 3390-3 volume if your storage is constrained.
Software requirements
You must install, enable, and configure the following z/OS or OS/390 elements, features, and components. Consult the Program Directory and PSP bucket for the required corrective service.
All of the z/OS sources referenced are available at this Web site: http://www.ibm.com/servers/eserver/zseries/zos/bkserv/
If you want to utilize the dynamic application environment functionality of WebSphere Application Server for z/OS Version 5.0.x, you must run at least z/OS Version 1.2.
Note:
MAXTHREADS:10000 MAXTHREADTASKS:5000 MAXFILEPROC:10000 MAXSOCKETS in the AF_INET domain:12000
Determine the size of the file system by entering the ISHELL command at the root "/" level in ISPF and using the line command U on the line for /tmp. This will display a box with information on the file system. Multiply the "Block Size" field by the "Total Blocks" field to see the total space in the file system in bytes. Multiply the "Block Size" field by the "Available Blocks" field to see the available space in bytes.
Note: The administrative console application .ear file is over 10 megabytes, so if there is not at least that much available space, action must be taken to increase the amount of space.
To increase the size of your /tmp directory file system, perform one of the following, depending on your file system type:
MOUNT FILESYSTEM('/TMP') TYPE(TFS) MOUNTPOINT('/tmp') PARM('-s 20')where 20 represents the desired amount of space in megabytes. If you do not specify a space value, the undesirable small default value of 1 megabyte will be assumed.
If you are not running z/OS Version 1.2 or above with the WLM-DAE support PTF (APAR OW54622), you must complete some additional steps for WLM.
Later releases of the IBM Developer Kit for OS/390 Java 2 Technology Edition are not supported.
Regarding optional functions, consult the following table:
If you plan to use . . . | Then you need . . . | Notes . . . |
---|---|---|
Kerberos security | OS/390 SecureWay Security Server Network Authentication and Privacy Service for OS/390 | For OS/390 and z/OS, this support is part of SecureWay Security Server. |
Cryptography | Cryptographic Services System SSL, a component of Cryptographic Services Base, an element of z/OS. | For details, see z/OS System Secure Sockets Layer Programming. |
EJB roles to secure Web components or enterprise beans | z/OS Version 1.2 Security Server (RACF) or equivalent | For releases of z/OS earlier than z/OS Version 1.2, install the appropriate APAR for this support. |
Java Message Service (JMS) |
|
MQSI, a pub sub product that supports z/OS, does not support new function like MDBs. |
WebSphere Application Server for z/OS IMS Connect Version 8 support | IMS/TM 6.1.0 | |
WebSphere Application Server for z/OS CICS Transaction Gateway 5.0.1 support | CICS/TS 1.3 | |
DB2 | DB2 Version 7.1 | DB2 is no longer a prerequisite for WebSphere Application Server for z/OS, though some functions may still require it. For example, session persistence requires an existing database. Check your individual configuration. |
DB2 SQLJ in J2EE application components | DB2 Version 7.1 PTF UQ59527 | DB2 is no longer a prerequisite for WebSphere Application Server for z/OS, though some functions may still require it. For example, session persistence requires an existing database. Check your individual configuration. |
Logging | z/OS system logger | For details, see z/OS MVS Setting Up a Sysplex. |
Connectors | WebSphere Application Server for z/OS supports any resource adapter that is designed to use the 1.0 level of the J2EE Connector Architecture (JCA). Install the listed IBM connectors if you want to access your IMS or CICS legacy data. For details on how to define and install a specific connector, see the documentation for that particular connector product. | |
For the CICS Transaction Gateway ECI connector:
|
||
For the IMS Connector for Java:
|
||
For the IMS JDBC Connector:
|