This topic applies only on the z/OS operating system.

Target system requirements

Prerequisites for configuring and running WebSphere Application Server for z/OS application serving environments are listed below.

Hardware requirements

The hardware requirements for this product are any hardware that supports z/OS Version 1 Release 4 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 might need to increase the real storage size depending on the size and number of application servers you deploy. In addition, you might want to increase your JES spool space if you use WebSphere Application Server for z/OS tracing options to the SYSPRINT DD data set.

In addition to the DASD volumes used to hold the product code and file system, you will need additional DASD storage to hold configuration data for application serving environments. The amount of storage depends on the number of environments and the size and complexity of the applications being deployed.

WebSphere Application Server for z/OS is a heavy user of auxiliary storage. You might want to add additional paging volumes before configuring application serving environments.

Software requirements

You need to enable, and configure the following z/OS elements, features, and components on each z/OS target system. Consult the WebSphere Application Server for z/OS Program Directory and PSP bucket for any additional required corrective service not listed here. In some cases, this corrective service must be installed on each target system for WebSphere Application Server to start.

All of the z/OS sources referenced are available at this Web site: http://www.ibm.com/servers/eserver/zseries/zos/bkserv/
  • z/OS (or z/OS.e) Version 1 Release 4 or later, configured as a sysplex (in the case of a single z/OS system, as a monoplex). For details, see z/OS MVS Setting Up a Sysplex.
  • z/OS UNIX System Services (z/OS UNIX) with an HFS or zFS file system. For details, see z/OS UNIX System Services Planning.
  • eNetwork Communications Server (TCP/IP) or equivalent. In this manual, we refer to eNetwork Communications Server; but you can substitute an equivalent product. For details, see z/OS Communications Server: IP Migration.
  • Workload management (WLM) set up in goal mode. For details, see z/OS MVS Planning: Workload Management.
  • Resource recovery services (RRS). For details, see z/OS MVS Programming: Resource Recovery.
  • System logger. For details, see z/OS MVS Setting up a Sysplex.
  • A security product such as z/OS Security Server (RACF). In this manual, we refer to Security Server in examples; but you can substitute an equivalent security product. For details, see z/OS Security Server RACF Migration.
Additional software might be required to support particular product functions.
Table 1. Software requirements for optional functions
If you plan to use . . . Then you need . . . Notes . . .
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 might 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 might still require it. For example, session persistence requires an existing database. Check your individual configuration.
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:
  • CICS Transaction Gateway Version 5.0.1
  • CICS Transaction Server Version 1.3
  • WebSphere Studio Application Developer IE Version 5.0
For the IMS Connector for Java:
  • IMS Connect for z/OS Version 2.1
  • IMS Version 8
  • WebSphere Studio Application Developer IE Version 5.0.1
For the IMS JDBC Connector:
  • IMS Version 8
 



Related tasks
Planning for installation
Reference topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 10:43:27 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v602web&product=was-nd-mp&topic=rins_reqstarget
File name: rins_reqstarget.html